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 |  Systems Thinking Evaporating Cloud |  Systems Thinking Future Reality Tree |  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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. | 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 | Medium | High | Medium |
Timedifferent | Halber Tag pro Domain Slice | 60-120 min | 2-4 h | 2-4 h |
Participantsdifferent | 1-4 | 2-8 | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | Knowledge graphValidationSemantic | Theory of ConstraintsAssumptionsSystems thinking | Theory of ConstraintsSystems thinkingChange | OntologyKnowledge graphScopeRequirementsSemantic |