View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Fault Tree Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Scatter Diagram |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | High | High | Low |
Timedifferent | 2-6 h | Several meetings plus preparation and analysis; total effort depends on scope | 30-90 min |
Participantsdifferent | 3-8 | Evaluation team, architects, and relevant stakeholders | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | 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 | Scatter Plot, Korrelationsnotiz, Hypothesenliste |
Tagsno overlap | RiskRoot causeSafety | ArchitectureQualityRiskTradeoffsStakeholders | Root causeQualityVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
