View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Specification by Example |  Domain Modeling Context Map |  Domain Modeling Domain Context Map |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 60-90 min pro Feature | 1-3 h | 1-3 h | 30-60 min |
Participantsdifferent | 3-6 | 2-8 | 3-10 | 3-7 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Context Map, Integration Patterns, Boundary Notes | Domain Context Map, Boundary Notes, Ownership Map | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignContextBoundaries | Behavior-Driven DevelopmentRequirementsExamplesRefinement |