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)Risk Stormingarc42ATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture Risk Storming |  Architecture arc42 |  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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | Low | High |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 60-90 min | 1-2 Tage | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | Designers, developers as users, and facilitation | 4-12 | 1-4 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Annotated Diagram, Prioritized Risk List, Action Backlog | Architecture Document, Context View, Runtime View, Deployment View | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tags1 shared | ArchitectureEngineeringFeedbackValidationTasks | RiskArchitectureWorkshopValidation | ArchitectureDocumentationCommunication | ArchitectureQualityRiskTradeoffsStakeholders |