View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Domain Modeling Context Map | ![]() Knowledge Modeling Linked Open Terms | ![]() Knowledge Modeling Ontology Design Patterns | ![]() Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | Wochen bis Monate | 1-3 h pro Pattern | 2-4 h |
Participantsdifferent | 2-8 | 2-8 | 1-6 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | OntologyMethodologyAgileSemantic | OntologyPatternsReuseSemanticModeling | OntologyKnowledge graphScopeRequirementsSemantic |



