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 Views and Beyond | ![]() Decision Making Decision Matrix | ![]() Architecture Request for Comments | ![]() Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 Tage | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 Tage |
Participantsdifferent | 1-4 | 2-8 | 3-20 Reviewer | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Architecture Views, Cross-view Notes, Rationale | Decision Matrix, Scoring Rationale, Selected Option | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | DocumentationStakeholdersArchitecture | DecisionCriteriaScoringTradeoffs | ArchitectureDecisionAsyncGovernance | ArchitectureDocumentationCommunication |



