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 AnalysisARID (Active Reviews for Intermediate Designs)Pre-MortemATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Engineering Failure Scenario Analysis |  Architecture ARID (Active Reviews for Intermediate Designs) |  Decision Making Pre-Mortem |  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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | 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 | Medium | Low | High |
Timedifferent | 1-3 h | 2–4 h review as a planning range; preparation and evaluation additional | 20–45 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-8 | Designers, developers as users, and facilitation | Small cross-functional group | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Risk list, Mitigation plan, Assumption log | 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 | ArchitectureEngineeringFeedbackValidationTasks | RiskDecisionFailurePlanning | ArchitectureQualityRiskTradeoffsStakeholders |