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 |  Domain Modeling Context Map |  Delivery Communication Plan |
|---|---|---|---|
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. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 1-4 h | 1-3 h | 45-90 min |
Participantsdifferent | 1-5 | 2-8 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Context Map, Integration Patterns, Boundary Notes | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | ArchitectureCommunicationVisualization | Domain-Driven DesignBoundariesStrategy | CommunicationStakeholdersDeliveryPlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
