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 |  Agile Example Mapping |  Agile Specification by Example |  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 story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 | Low | Medium | Medium |
Timedifferent | 1-3 h | 30-60 min | 60-90 min pro Feature | 1-3 h |
Participantsdifferent | 2-8 | 3-7 | 3-6 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development | Domain-Driven DesignContextBoundaries |