View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture arc42 | ![]() Operations A3 Problem Solving | ![]() Architecture SAAM (Software Architecture Analysis Method) | ![]() Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 1-2 Tage | 45-90 min | Preparation, scenario analysis, and findings review; effort depends on scope | 15-30 min |
Participantsdifferent | 1-4 | 2-5 | Architecture experts and stakeholders for scenarios and weighting | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | A3 Report, Action Plan, Root Cause Analysis | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Root cause notes, Countermeasures |
Tagsno overlap | ArchitectureDocumentationCommunication | LeanProblem solvingCoachingOperations | ArchitectureChangeAnalysisComparisonQuality | Root causeIncidentLeanProblem solving |



