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 arc42 |  Knowledge Modeling Competency Questions |  Architecture C4 Model |
|---|---|---|---|---|
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. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | Halber Tag pro Domain Slice | 1-2 Tage | 2-4 h | 1-4 h |
Participantsdifferent | 1-4 | 1-4 | 2-8 | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Architecture Document, Context View, Runtime View, Deployment View | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | Knowledge graphValidationSemantic | ArchitectureDocumentationCommunication | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureCommunicationVisualization |