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 Domain Context Map |  Operations Theory of Constraints |  Operations Process Mapping |
|---|---|---|---|---|
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 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. | For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 1-3 h | 1-3 h | 2-4 h Analyse, laufend | 1-3 h |
Participantsdifferent | 2-8 | 3-10 | 3-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Domain Context Map, Boundary Notes, Ownership Map | Constraint Map, Improvement Plan, Flow Metrics | Process Map, Handoff List, Improvement Backlog |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignContextBoundaries | OperationsConstraintsFlowImprovement | ProcessOperationsImprovement |