View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Competency QuestionsArchitecture Communication CanvasARID (Active Reviews for Intermediate Designs)Shape-First Modeling
| Criterion |  Knowledge Modeling Competency Questions |  Architecture Architecture Communication Canvas |  Architecture ARID (Active Reviews for Intermediate Designs) |  Knowledge Modeling Shape-First Modeling |
|---|---|---|---|---|
Purposedifferent | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 2-4 h | 60-120 min | 2–4 h review as a planning range; preparation and evaluation additional | Halber Tag pro Domain Slice |
Participantsdifferent | 2-8 | 2-8 | Designers, developers as users, and facilitation | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureCommunicationStakeholdersCanvas | ArchitectureEngineeringFeedbackValidationTasks | Knowledge graphValidationSemantic |