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 Specification by Example |  Agile Acceptance Criteria Workshop |
|---|---|---|---|
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 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 story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-3 h | 60-90 min pro Feature | 20-40 min pro Story |
Participantsdifferent | 2-8 | 3-6 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Example Table, Acceptance Tests | Acceptance Criteria, Story Update |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | AgileRequirementsExamplesBehavior-Driven Development | AgileRequirementsRefinementBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
