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 Architecture Decision Record |  Architecture arc42 |  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. | 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. | 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. | 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 | Low | Low |
Timedifferent | Halber Tag pro Domain Slice | 15-45 min | 1-2 Tage | 1-4 h |
Participantsdifferent | 1-4 | 1-3 | 1-4 | 1-5 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | Knowledge graphValidationSemantic | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication | ArchitectureCommunicationVisualization |