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 IBIS | ![]() Knowledge Modeling Property Graph Schema Design | ![]() Knowledge Modeling Shape-First Modeling | ![]() Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | 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. | 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. | 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 | 1-3 h | 4-8 h initial, dann iterativ | Halber Tag pro Domain Slice | 2-4 h |
Participantsdifferent | 2-8 | 1-6 | 1-4 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Issue Map, Positions, Argument Notes | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | RationaleKnowledgeDecision | Knowledge graphModelingSemantic | Knowledge graphValidationSemantic | OntologyKnowledge graphScopeRequirementsSemantic |



