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 | ![]() Knowledge Modeling Ontology Design Patterns | ![]() Architecture arc42 |
|---|---|---|---|---|
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. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 15-45 min | Halber Tag pro Domain Slice | 1-3 h pro Pattern | 1-2 Tage |
Participantsdifferent | 1-3 | 1-4 | 1-6 | 1-4 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Knowledge graphValidationSemantic | OntologyPatternsReuseSemanticModeling | ArchitectureDocumentationCommunication |



