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 |  Domain Modeling Bounded Context Canvas |  Decision Making Force Field Analysis |  Domain Modeling Domain Context Map |
|---|---|---|---|---|
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. | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 1-3 h | 45-90 min | 1-3 h |
Participantsdifferent | 2-8 | 3-8 | 3-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Context Canvas, Glossary, Integration Notes | Force Field Map, Change Levers, Risk Notes | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignBoundariesModeling | ChangeDecisionStrategy | Domain-Driven DesignContextBoundaries |