View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Request for Comments |  Architecture Risk Storming |  Decision Making Decision Rights Mapping |  Architecture Software Architecture Canvas |
|---|---|---|---|---|
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. | 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. | 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 60-90 min | 90-180 min | 1-2 h |
Participantsdifferent | 3-20 Reviewer | 4-12 | 4-12 | 3-10 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Annotated Diagram, Prioritized Risk List, Action Backlog | Decision Rights Matrix, Agreement | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | RiskArchitectureWorkshopValidation | DecisionGovernanceAlignmentResponsibility | CanvasArchitectureAlignmentWorkshop |