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 Specification by Example |  Knowledge Modeling Competency Questions |  Knowledge Modeling NeOn Methodology |  Knowledge Modeling Ontology Design Patterns |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 60-90 min pro Feature | 2-4 h | Mehrere Wochen bis Monate | 1-3 h pro Pattern |
Participantsdifferent | 3-6 | 2-8 | 2-10 | 1-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Selected Patterns, Adapted Schema Fragments, Pattern Documentation |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | OntologyKnowledge graphScopeRequirementsSemantic | OntologyMethodologyReuseSemanticEngineering | OntologyPatternsReuseSemanticModeling |