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 Competency Questions | ![]() Agile Three Amigos | ![]() Knowledge Modeling NeOn Methodology | ![]() Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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. | 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. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 2-4 h | 15-30 min | Mehrere Wochen bis Monate | 30-60 min |
Participantsdifferent | 2-8 | 3 | 2-10 | 3-7 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Clarified Story, Test Examples, Open Questions | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | CollaborationBehavior-Driven DevelopmentQualityRefinement | OntologyMethodologyReuseSemanticEngineering | Behavior-Driven DevelopmentRequirementsExamplesRefinement |



