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 | ![]() Delivery RAID Log |
|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | Halber Tag pro Domain Slice | 15-45 min | 30 min Setup, dann laufend |
Participantsdifferent | 1-4 | 1-3 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Async | Async |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | ADR File, Decision Log, Rationale | RAID Log, Status Report Source |
Tagsno overlap | Knowledge graphValidationSemantic | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






