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 Competency Questions |  Knowledge Modeling Property Graph Schema Design |  Domain Modeling Domain Context Map |
|---|---|---|---|---|
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. | 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. | 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 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 | 1-3 h | 2-4 h | 4-8 h initial, dann iterativ | 1-3 h |
Participantsdifferent | 2-8 | 2-8 | 1-6 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | OntologyKnowledge graphScopeRequirementsSemantic | Knowledge graphModelingSemantic | Domain-Driven DesignContextBoundaries |