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 AnalysisScatter DiagramFault Tree AnalysisATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Engineering Failure Scenario Analysis |  Operations Scatter Diagram |  Operations Fault Tree Analysis |  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. | 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. | 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. | 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 | Low | High | High |
Timedifferent | 1-3 h | 30-90 min | 2-6 h | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-8 | 1-4 | 3-8 | 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 | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | 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 | Root causeQualityVisualization | RiskRoot causeSafety | ArchitectureQualityRiskTradeoffsStakeholders |