View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Failure Scenario AnalysisFault Tree Analysisarc42ATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Engineering Failure Scenario Analysis |  Operations Fault Tree Analysis |  Architecture arc42 |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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 critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitydifferent | Medium | High | Low | High |
Timedifferent | 1-3 h | 2-6 h | 1-2 Tage | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-8 | 3-8 | 1-4 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Architecture Document, Context View, Runtime View, Deployment View | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | FailureResilienceRisk | RiskRoot causeSafety | ArchitectureDocumentationCommunication | ArchitectureQualityRiskTradeoffsStakeholders |