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 arc42 |  Domain Modeling Context Map |  Architecture Architecture Decision Record |  Domain Modeling Bounded Context Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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. | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 1-2 Tage | 1-3 h | 15-45 min | 1-3 h |
Participantsdifferent | 1-4 | 2-8 | 1-3 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Context Map, Integration Patterns, Boundary Notes | ADR File, Decision Log, Rationale | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | ArchitectureDocumentationCommunication | Domain-Driven DesignBoundariesStrategy | ArchitectureRationaleDocumentationGovernance | Domain-Driven DesignBoundariesModeling |