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 Event Modeling |  Knowledge Modeling NeOn Methodology |  Knowledge Modeling Ontology Design Patterns |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | 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. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. | 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 | High | Medium | Medium |
Timedifferent | 2-6 h | Mehrere Wochen bis Monate | 1-3 h pro Pattern | 2-4 h |
Participantsdifferent | 2-8 | 2-10 | 1-6 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | OntologyMethodologyReuseSemanticEngineering | OntologyPatternsReuseSemanticModeling | OntologyKnowledge graphScopeRequirementsSemantic |