methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Fault Isolation.
Engineering
Fault Isolation
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Complexitydifferent
MediumLowLowLow
Timedifferent
30-180 min1-2 h15-45 min1-2 h
Participantsdifferent
1-63-101-33-8
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop
Outputdifferent
Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault AreaArchitecture Canvas, Goals, Constraints, Quality AttributesADR File, Decision Log, RationaleInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
TroubleshootingDiagnosisEngineering
CanvasArchitectureAlignmentWorkshop
ArchitectureRationaleDocumentationGovernance
AlignmentArchitectureCanvas
Add more methods