View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Kano Model |  Agile Specification by Example |  Knowledge Modeling NeOn Methodology |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | 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. | 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 | Medium | Medium | High | Medium |
Timedifferent | 1-2 Tage | 60-90 min pro Feature | Mehrere Wochen bis Monate | 2-4 h |
Participantsdifferent | 10-50 | 3-6 | 2-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Example Table, Acceptance Tests | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | SatisfactionPrioritizationCustomer | AgileRequirementsExamplesBehavior-Driven Development | OntologyMethodologyReuseSemanticEngineering | OntologyKnowledge graphScopeRequirementsSemantic |