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 |  Systems Thinking System Dynamics Simulation |  Domain Modeling Bounded Context Canvas |  Systems Thinking Causal Loop Diagram |
|---|---|---|---|---|
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. | System Dynamics Simulation makes assumptions about time, delay, and feedback testable through experiments. It draws relationships, patterns, and feedback loops. The result is captured as a simulation model and scenario reports. | 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. | A Causal Loop Diagram makes feedback, reinforcement, and balance in a system legible. It uncovers side effects and self-reinforcement that stay hidden in linear explanations. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-3 h | Mehrere Tage bis Wochen | 1-3 h | 1-3 h |
Participantsdifferent | 2-8 | 1-5 Modellierende, Stakeholder asynchron | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Simulation Model, Scenario Reports | Context Canvas, Glossary, Integration Notes | Causal Loop Diagram, Feedback Notes, Leverage Points |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Systems thinkingDynamicsSimulationAnalysis | Domain-Driven DesignBoundariesModeling | FeedbackSystems thinkingCausalityDynamics |