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 C4 Model |  Architecture arc42 |  Decision Making DACI |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 1-4 h | 1-2 Tage | 30-60 min | 15-45 min |
Participantsdifferent | 1-5 | 1-4 | 2-10 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Architecture Document, Context View, Runtime View, Deployment View | DACI Matrix, Decision Owner, Decision Log | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureCommunicationVisualization | ArchitectureDocumentationCommunication | DecisionRolesGovernanceAlignment | ArchitectureRationaleDocumentationGovernance |