View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Constraint Analysis |  Architecture SAAM (Software Architecture Analysis Method) |  Operations 5 Whys |  Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitydifferent | Low | High | Low | Medium |
Timedifferent | 30-90 min | Preparation, scenario analysis, and findings review; effort depends on scope | 15-30 min | 1-4 h |
Participantsdifferent | 2-8 | Architecture experts and stakeholders for scenarios and weighting | 2-6 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | 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 | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | ConstraintsDecisionPlanningOptions | ArchitectureChangeAnalysisComparisonQuality | Root causeIncidentLeanProblem solving | Root causeProblem solvingQualityIncident |