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 |  Architecture Risk Storming |  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 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. | 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 |
Timedifferent | Halber Tag pro Domain Slice | 60-90 min | 2-4 h |
Participantsdifferent | 1-4 | 4-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Annotated Diagram, Prioritized Risk List, Action Backlog | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | Knowledge graphValidationSemantic | RiskArchitectureWorkshopValidation | OntologyKnowledge graphScopeRequirementsSemantic |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
