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 |  Delivery RAID Log |  Knowledge Modeling Competency Questions |  Knowledge Modeling Ontology Design Patterns |
|---|---|---|---|---|
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. | 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. | 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. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 4-8 h initial, dann iterativ | 30 min Setup, dann laufend | 2-4 h | 1-3 h pro Pattern |
Participantsdifferent | 1-6 | 1-3 maintaining, briefing for everyone | 2-8 | 1-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | RAID Log, Status Report Source | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Selected Patterns, Adapted Schema Fragments, Pattern Documentation |
Tagsno overlap | Knowledge graphModelingSemantic | RiskTrackingStakeholdersGovernance | OntologyKnowledge graphScopeRequirementsSemantic | OntologyPatternsReuseSemanticModeling |