View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ARID (Active Reviews for Intermediate Designs)MoSCoWDecision MatrixATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Delivery MoSCoW |  Decision Making Decision Matrix |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved. | When several options collide with several criteria, comparison quickly becomes subjective. A Decision Matrix makes the trade-off visible and brings weighting, criteria, and options into a shared logic. | 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 | Low | Medium | High |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 30-90 min | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | Designers, developers as users, and facilitation | 3-12 | 2-8 | Evaluation team, architects, and relevant stakeholders |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Prioritized Backlog, Release Scope, Tradeoff Notes | Decision Matrix, Scoring Rationale, Selected Option | 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 | ArchitectureEngineeringFeedbackValidationTasks | PrioritizationScopeDecision | DecisionCriteriaScoringTradeoffs | ArchitectureQualityRiskTradeoffsStakeholders |