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 |  Domain Modeling Context Map |  Knowledge Modeling Ontology Design Patterns |  Domain Modeling Domain Context Map |
|---|---|---|---|---|
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. | 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. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 2-4 h | 1-3 h | 1-3 h pro Pattern | 1-3 h |
Participantsdifferent | 2-8 | 2-8 | 1-6 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Context Map, Integration Patterns, Boundary Notes | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | Domain-Driven DesignBoundariesStrategy | OntologyPatternsReuseSemanticModeling | Domain-Driven DesignContextBoundaries |