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 Architecture Decision Record |  Architecture C4 Model |  Delivery RAID Log |  Architecture Views and Beyond |
|---|---|---|---|---|
Purposedifferent | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. | 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 | Low | Medium |
Timedifferent | 15-45 min | 1-4 h | 30 min Setup, dann laufend | 1-3 Tage |
Participantsdifferent | 1-3 | 1-5 | 1-3 maintaining, briefing for everyone | 1-4 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram | RAID Log, Status Report Source | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization | RiskTrackingStakeholdersGovernance | DocumentationStakeholdersArchitecture |