View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Delivery Communication Plan |  Architecture Views and Beyond |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 45-90 min | 1-3 Tage | 15-45 min |
Participantsdifferent | 2-8 | 2-6 | 1-4 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Communication Plan, Channel Matrix, Message Cadence | Architecture Views, Cross-view Notes, Rationale | ADR File, Decision Log, Rationale |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | CommunicationStakeholdersDeliveryPlanning | DocumentationStakeholdersArchitecture | ArchitectureRationaleDocumentationGovernance |