View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Engineering Fault Isolation | ![]() Architecture Views and Beyond | ![]() Architecture Software Architecture Canvas | ![]() Facilitation Alignment Mapping |
|---|---|---|---|---|
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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 30-180 min | 1-3 Tage | 1-2 h | 1-2 h |
Participantsdifferent | 1-6 | 1-4 | 3-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Architecture Views, Cross-view Notes, Rationale | Architecture Canvas, Goals, Constraints, Quality Attributes | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | TroubleshootingDiagnosisEngineering | DocumentationStakeholdersArchitecture | CanvasArchitectureAlignmentWorkshop | AlignmentStakeholdersStrategyFacilitation |



