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 Competency Questions |  Knowledge Modeling Shape-First Modeling |  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. | 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. | 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 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 | Medium | Medium |
Timedifferent | 1-4 h | 2-4 h | Halber Tag pro Domain Slice | 60-120 min |
Participantsdifferent | 1-5 | 2-8 | 1-4 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ArchitectureCommunicationVisualization | OntologyKnowledge graphScopeRequirementsSemantic | Knowledge graphValidationSemantic | ArchitectureCommunicationStakeholdersCanvas |