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 Property Graph Schema Design |  Domain Modeling Bounded Context Canvas |
|---|---|---|---|---|
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. | Property Graph Schema Design turns business and technical requirements into a robust graph schema. It fits when query patterns, constraints, and migrations need to be thought about together. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 2-4 h | 1-3 h | 4-8 h initial, dann iterativ | 1-3 h |
Participantsdifferent | 2-8 | 2-8 | 1-6 | 3-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Context Map, Integration Patterns, Boundary Notes | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | Domain-Driven DesignBoundariesStrategy | Knowledge graphModelingSemantic | Domain-Driven DesignBoundariesModeling |