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 Example Mapping |  Knowledge Modeling Event Modeling |  Domain Modeling Domain Context Map |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | 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 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 30-60 min | 2-6 h | 1-3 h | 60-90 min pro Feature |
Participantsdifferent | 3-7 | 2-8 | 3-10 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Event Model, UI Flow, Commands, Read Models | Domain Context Map, Boundary Notes, Ownership Map | Example Table, Acceptance Tests |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | EventsBlueprintDomain-Driven DesignBehavior | Domain-Driven DesignContextBoundaries | AgileRequirementsExamplesBehavior-Driven Development |