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 AnalysisATAM (Architecture Tradeoff Analysis Method)ARID (Active Reviews for Intermediate Designs)Architecture Communication Canvas
| Criterion |  Engineering Failure Scenario Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 2–4 h review as a planning range; preparation and evaluation additional | 60-120 min |
Participantsdifferent | 3-8 | Evaluation team, architects, and relevant stakeholders | Designers, developers as users, and facilitation | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | FailureResilienceRisk | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureCommunicationStakeholdersCanvas |