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 NeOn Methodology |  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. | The NeOn Methodology structures ontology work as a controlled process with reuse, scenarios, and reviews. It is useful when ontologies should not emerge ad hoc but modularly and reusably. | 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 | High | Medium |
Timedifferent | 30-60 min | 4-8 h initial, dann iterativ | Mehrere Wochen bis Monate | 2-4 h |
Participantsdifferent | 3-7 | 1-6 | 2-10 | 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 | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Knowledge graphModelingSemantic | OntologyMethodologyReuseSemanticEngineering | OntologyKnowledge graphScopeRequirementsSemantic |