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 | ![]() Knowledge Modeling Linked Open Terms | ![]() Knowledge Modeling Competency Questions | ![]() Knowledge Modeling Ontology Design Patterns |
|---|---|---|---|---|
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. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | 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. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | Wochen bis Monate | 2-4 h | 1-3 h pro Pattern |
Participantsdifferent | 10-50 | 2-8 | 2-8 | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Selected Patterns, Adapted Schema Fragments, Pattern Documentation |
Tagsno overlap | SatisfactionPrioritizationCustomer | OntologyMethodologyAgileSemantic | OntologyKnowledge graphScopeRequirementsSemantic | OntologyPatternsReuseSemanticModeling |



