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)Hypothesis-Driven TroubleshootingARID (Active Reviews for Intermediate Designs)Risk Storming
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Engineering Hypothesis-Driven Troubleshooting |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture Risk Storming |
|---|---|---|---|---|
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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30-240 min | 2–4 h review as a planning range; preparation and evaluation additional | 60-90 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1-6 | Designers, developers as users, and facilitation | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | TroubleshootingProblem solvingDiagnosis | ArchitectureEngineeringFeedbackValidationTasks | RiskArchitectureWorkshopValidation |