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 C4 Model | ![]() Knowledge Modeling Shape-First Modeling | ![]() Architecture Architecture Decision Record | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 1-4 h | Halber Tag pro Domain Slice | 15-45 min | 60-120 min |
Participantsdifferent | 1-5 | 1-4 | 1-3 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | ADR File, Decision Log, Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ArchitectureCommunicationVisualization | Knowledge graphValidationSemantic | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationStakeholdersCanvas |



