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 ATAM (Architecture Tradeoff Analysis Method) |  Engineering Failure Scenario Analysis |  Operations 5 Whys |
|---|---|---|---|
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. | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | 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 | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 h | 15-30 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Root cause notes, Countermeasures |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | FailureResilienceRisk | Root causeIncidentLeanProblem solving |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
