View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Root Cause Tree Analysis |  Operations Scatter Diagram |  Architecture SAAM (Software Architecture Analysis Method) |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | 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 | Medium | Low | High | Low |
Timedifferent | 1-3 h | 30-90 min | Preparation, scenario analysis, and findings review; effort depends on scope | 15-30 min |
Participantsdifferent | 2-8 | 1-4 | Architecture experts and stakeholders for scenarios and weighting | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Cause Tree, Evidence Notes, Countermeasures | Scatter Plot, Korrelationsnotiz, Hypothesenliste | 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 | Root causeTreeIncidentQuality | Root causeQualityVisualization | ArchitectureChangeAnalysisComparisonQuality | Root causeIncidentLeanProblem solving |