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 |  Knowledge Modeling Ontology Design Patterns |  Delivery MoSCoW |  Knowledge Modeling NeOn Methodology |
|---|---|---|---|---|
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. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. | When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved. | 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. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 2-4 h | 1-3 h pro Pattern | 30-90 min | Mehrere Wochen bis Monate |
Participantsdifferent | 2-8 | 1-6 | 3-12 | 2-10 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Prioritized Backlog, Release Scope, Tradeoff Notes | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | OntologyPatternsReuseSemanticModeling | PrioritizationScopeDecision | OntologyMethodologyReuseSemanticEngineering |