View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)Root Cause AnalysisHypothesis-Driven Troubleshooting
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Root Cause Analysis |  Engineering Hypothesis-Driven Troubleshooting |
|---|---|---|---|
Purposedifferent | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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 | Several meetings plus preparation and analysis; total effort depends on scope | 1-4 h | 30-240 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-8 | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | Root causeProblem solvingQualityIncident | TroubleshootingProblem solvingDiagnosis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
