View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Request for CommentsDecision Rights MappingRAID LogATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Architecture Request for Comments |  Decision Making Decision Rights Mapping |  Delivery RAID Log |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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. | 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 | Medium | Low | High |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min | 30 min Setup, dann laufend | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-20 Reviewer | 4-12 | 1-3 maintaining, briefing for everyone | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Async | Workshop | Async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Decision Rights Matrix, Agreement | RAID Log, Status Report Source | 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 | ArchitectureDecisionAsyncGovernance | DecisionGovernanceAlignmentResponsibility | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskTradeoffsStakeholders |