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)Failure Mode and Effects AnalysisScatter Diagram
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Failure Mode and Effects Analysis |  Operations Scatter Diagram |
|---|---|---|---|
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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | 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 | Several meetings plus preparation and analysis; total effort depends on scope | 2-6 h | 30-90 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-10 | 1-4 |
Formatdifferent | Workshop + async | Workshop | 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 | FMEA Table, Risk Priority, Mitigation Actions | Scatter Plot, Korrelationsnotiz, Hypothesenliste |
Tags1 shared | ArchitectureQualityRiskTradeoffsStakeholders | RiskQualityOperationsRoot cause | Root causeQualityVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
