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 Shape-First Modeling |  Delivery RAID Log |  Knowledge Modeling Property Graph Schema Design |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | Halber Tag pro Domain Slice | 30 min Setup, dann laufend | 4-8 h initial, dann iterativ | 2-4 h |
Participantsdifferent | 1-4 | 1-3 maintaining, briefing for everyone | 1-6 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | RAID Log, Status Report Source | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | Knowledge graphValidationSemantic | RiskTrackingStakeholdersGovernance | Knowledge graphModelingSemantic | OntologyKnowledge graphScopeRequirementsSemantic |