View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:SAAM (Software Architecture Analysis Method)Root Cause AnalysisHypothesis-Driven Troubleshooting
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Root Cause Analysis |  Engineering Hypothesis-Driven Troubleshooting |
|---|---|---|---|
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 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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. |
Complexitydifferent | High | Medium | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 1-4 h | 30-240 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-8 | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
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 | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | Root causeProblem solvingQualityIncident | TroubleshootingProblem solvingDiagnosis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
