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 |  Knowledge Modeling Linked Open Terms |  Architecture arc42 |  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. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | Low | Medium |
Timedifferent | Halber Tag pro Domain Slice | Wochen bis Monate | 1-2 Tage | 2-4 h |
Participantsdifferent | 1-4 | 2-8 | 1-4 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Architecture Document, Context View, Runtime View, Deployment View | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | Knowledge graphValidationSemantic | OntologyMethodologyAgileSemantic | ArchitectureDocumentationCommunication | OntologyKnowledge graphScopeRequirementsSemantic |