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 Property Graph Schema Design |  Knowledge Modeling Ontology Design Patterns |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
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. | 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. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 30-60 min | 4-8 h initial, dann iterativ | 1-3 h pro Pattern | 2-4 h |
Participantsdifferent | 3-7 | 1-6 | 1-6 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Knowledge graphModelingSemantic | OntologyPatternsReuseSemanticModeling | OntologyKnowledge graphScopeRequirementsSemantic |