View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Knowledge Modeling Shape-First Modeling |  Architecture C4 Model |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 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. | 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 | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | Halber Tag pro Domain Slice | 1-4 h | 2-4 h |
Participantsdifferent | 1-3 | 1-4 | 1-5 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Context Diagram, Container Diagram, Component Diagram | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Knowledge graphValidationSemantic | ArchitectureCommunicationVisualization | OntologyKnowledge graphScopeRequirementsSemantic |