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 Domain Context Map |  Knowledge Modeling Linked Open Terms |  Domain Modeling Bounded Context Canvas |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. | 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 | 2-4 h |
Participantsdifferent | 3-10 | 2-8 | 3-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Context Canvas, Glossary, Integration Notes | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | Domain-Driven DesignContextBoundaries | OntologyMethodologyAgileSemantic | Domain-Driven DesignBoundariesModeling | OntologyKnowledge graphScopeRequirementsSemantic |