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 |  Domain Modeling Context Map |  Architecture Architecture Decision Record |  Architecture arc42 |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 1-2 h | 1-3 h | 15-45 min | 1-2 Tage |
Participantsdifferent | 2-8 | 2-8 | 1-3 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Context Map, Integration Patterns, Boundary Notes | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | Domain-Driven DesignBoundariesStrategy | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |