View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Shape-First ModelingC4 ModelCompetency QuestionsARID (Active Reviews for Intermediate Designs)
| Criterion | ![]() Knowledge Modeling Shape-First Modeling | ![]() Architecture C4 Model | ![]() Knowledge Modeling Competency Questions | ![]() Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
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. | 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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | Halber Tag pro Domain Slice | 1-4 h | 2-4 h | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 1-4 | 1-5 | 2-8 | Designers, developers as users, and facilitation |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Context Diagram, Container Diagram, Component Diagram | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | Knowledge graphValidationSemantic | ArchitectureCommunicationVisualization | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureEngineeringFeedbackValidationTasks |



