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 Bounded Context Canvas |  Systems Thinking Wardley Mapping |  Systems Thinking System Dynamics Simulation |  Domain Modeling Context Map |
|---|---|---|---|---|
Purposedifferent | 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. | Wardley Mapping makes visible where an offering stands today and where it can evolve. The method connects user need, value chain, and evolution stages into a strategic basis for platform, build, or buy decisions. | 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 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. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 1-3 h | 1-3 h | Mehrere Tage bis Wochen | 1-3 h |
Participantsdifferent | 3-8 | 2-10 | 1-5 Modellierende, Stakeholder asynchron | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Context Canvas, Glossary, Integration Notes | Wardley Map, Strategic Options, Evolution Notes | Simulation Model, Scenario Reports | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | Domain-Driven DesignBoundariesModeling | StrategySystems thinkingDynamics | Systems thinkingDynamicsSimulationAnalysis | Domain-Driven DesignBoundariesStrategy |