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 |  Delivery RAID Log |  Architecture Architecture Decision Record |  Architecture Views and Beyond |
|---|---|---|---|---|
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 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 30 min Setup, dann laufend | 15-45 min | 1-3 Tage |
Participantsdifferent | 3-20 Reviewer | 1-3 maintaining, briefing for everyone | 1-3 | 1-4 |
Formatdifferent | Async | Async | Async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | RAID Log, Status Report Source | ADR File, Decision Log, Rationale | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | RiskTrackingStakeholdersGovernance | ArchitectureRationaleDocumentationGovernance | DocumentationStakeholdersArchitecture |