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)Request for CommentsATAM (Architecture Tradeoff Analysis Method)RAID Log
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture Request for Comments |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Delivery RAID Log |
|---|---|---|---|---|
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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 Wochen vom Draft bis zur Entscheidung | Several meetings plus preparation and analysis; total effort depends on scope | 30 min Setup, dann laufend |
Participantsdifferent | Designers, developers as users, and facilitation | 3-20 Reviewer | Evaluation team, architects, and relevant stakeholders | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureDecisionAsyncGovernance | ArchitectureQualityRiskTradeoffsStakeholders | RiskTrackingStakeholdersGovernance |