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 Property Graph Schema Design |  Knowledge Modeling Event Modeling |  Domain Modeling Context Map |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | 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. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 4-8 h initial, dann iterativ | 2-6 h | 1-3 h | 2-4 h |
Participantsdifferent | 1-6 | 2-8 | 2-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | Event Model, UI Flow, Commands, Read Models | Context Map, Integration Patterns, Boundary Notes | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | Knowledge graphModelingSemantic | EventsBlueprintDomain-Driven DesignBehavior | Domain-Driven DesignBoundariesStrategy | OntologyKnowledge graphScopeRequirementsSemantic |