View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Architecture arc42 |  Architecture Request for Comments |  Architecture Views and Beyond |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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 | Low | Low | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | 1-2 Tage | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 Tage |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-4 | 3-20 Reviewer | 1-4 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Architecture Document, Context View, Runtime View, Deployment View | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureDocumentationCommunication | ArchitectureDecisionAsyncGovernance | DocumentationStakeholdersArchitecture |