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 | ![]() Architecture Software Architecture Canvas | ![]() Knowledge Modeling Shape-First Modeling |
|---|---|---|---|
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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 2-4 h | 1-2 h | Halber Tag pro Domain Slice |
Participantsdifferent | 2-8 | 3-10 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Architecture Canvas, Goals, Constraints, Quality Attributes | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | CanvasArchitectureAlignmentWorkshop | Knowledge graphValidationSemantic |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






