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 NeOn Methodology | ![]() Knowledge Modeling Competency Questions | ![]() Decision Making Force Field Analysis | ![]() Knowledge Modeling Ontology Design Patterns |
|---|---|---|---|---|
Purposedifferent | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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 | High | Medium | Low | Medium |
Timedifferent | Mehrere Wochen bis Monate | 2-4 h | 45-90 min | 1-3 h pro Pattern |
Participantsdifferent | 2-10 | 2-8 | 3-12 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Force Field Map, Change Levers, Risk Notes | Selected Patterns, Adapted Schema Fragments, Pattern Documentation |
Tagsno overlap | OntologyMethodologyReuseSemanticEngineering | OntologyKnowledge graphScopeRequirementsSemantic | ChangeDecisionStrategy | OntologyPatternsReuseSemanticModeling |



