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 Competency Questions | ![]() Knowledge Modeling NeOn Methodology |
|---|---|---|---|
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. | 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. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 2-6 h | 2-4 h | Mehrere Wochen bis Monate |
Participantsdifferent | 2-8 | 2-8 | 2-10 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | OntologyKnowledge graphScopeRequirementsSemantic | OntologyMethodologyReuseSemanticEngineering |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






