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 Competency Questions | ![]() Knowledge Modeling Shape-First Modeling | ![]() Systems Thinking Future Reality Tree | ![]() Systems Thinking Evaporating Cloud |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 2-4 h | Halber Tag pro Domain Slice | 2-4 h | 60-120 min |
Participantsdifferent | 2-8 | 1-4 | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | Knowledge graphValidationSemantic | Theory of ConstraintsSystems thinkingChange | Theory of ConstraintsAssumptionsSystems thinking |



