View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Domain Storytelling |  Architecture arc42 |  Domain Modeling Context Map |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected. | 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. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 1-2 h | 1-2 Tage | 1-3 h | 1-4 h |
Participantsdifferent | 2-8 | 1-4 | 2-8 | 1-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Architecture Document, Context View, Runtime View, Deployment View | Context Map, Integration Patterns, Boundary Notes | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | ArchitectureDocumentationCommunication | Domain-Driven DesignBoundariesStrategy | ArchitectureCommunicationVisualization |