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 NeOn Methodology | ![]() Architecture arc42 | ![]() Knowledge Modeling Ontology Design Patterns |
|---|---|---|---|---|
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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | High | Low | Medium |
Timedifferent | 2-4 h | Mehrere Wochen bis Monate | 1-2 Tage | 1-3 h pro Pattern |
Participantsdifferent | 2-8 | 2-10 | 1-4 | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Architecture Document, Context View, Runtime View, Deployment View | Selected Patterns, Adapted Schema Fragments, Pattern Documentation |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | OntologyMethodologyReuseSemanticEngineering | ArchitectureDocumentationCommunication | OntologyPatternsReuseSemanticModeling |



