View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Property Graph Schema Design |  Agile Example Mapping |  Agile Specification by Example |
|---|---|---|---|
Purposedifferent | Property Graph Schema Design turns business and technical requirements into a robust graph schema. It fits when query patterns, constraints, and migrations need to be thought about together. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 4-8 h initial, dann iterativ | 30-60 min | 60-90 min pro Feature |
Participantsdifferent | 1-6 | 3-7 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests |
Tagsno overlap | Knowledge graphModelingSemantic | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
