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 SAAM (Software Architecture Analysis Method) |  Operations Scatter Diagram |  Operations Root Cause Analysis |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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 | High | Low | Medium | Low |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 30-90 min | 1-4 h | 15-30 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 1-4 | 3-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | 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 | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Root cause notes, Countermeasures |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | Root causeQualityVisualization | Root causeProblem solvingQualityIncident | Root causeIncidentLeanProblem solving |