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 Shape-First Modeling | ![]() Systems Thinking Evaporating Cloud | ![]() 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. | Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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 | Medium | High |
Timedifferent | 2-4 h | Halber Tag pro Domain Slice | 60-120 min | Mehrere Wochen bis Monate |
Participantsdifferent | 2-8 | 1-4 | 2-8 | 2-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | Knowledge graphValidationSemantic | Theory of ConstraintsAssumptionsSystems thinking | OntologyMethodologyReuseSemanticEngineering |



