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