View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  Knowledge Modeling Property Graph Schema Design |  Knowledge Modeling Shape-First Modeling |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 60-90 min | 4-8 h initial, dann iterativ | Halber Tag pro Domain Slice | 2-4 h |
Participantsdifferent | 4-12 | 1-6 | 1-4 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | 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 | RiskArchitectureWorkshopValidation | Knowledge graphModelingSemantic | Knowledge graphValidationSemantic | OntologyKnowledge graphScopeRequirementsSemantic |