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 QuestionsARID (Active Reviews for Intermediate Designs)Acceptance Criteria WorkshopShape-First Modeling
| Criterion |  Knowledge Modeling Competency Questions |  Architecture ARID (Active Reviews for Intermediate Designs) |  Agile Acceptance Criteria Workshop |  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. | 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. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 2-4 h | 2–4 h review as a planning range; preparation and evaluation additional | 20-40 min pro Story | Halber Tag pro Domain Slice |
Participantsdifferent | 2-8 | Designers, developers as users, and facilitation | 3-6 | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | 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 | Acceptance Criteria, Story Update | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureEngineeringFeedbackValidationTasks | AgileRequirementsRefinementBehavior-Driven Development | Knowledge graphValidationSemantic |