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 ARID (Active Reviews for Intermediate Designs) |  Knowledge Modeling Shape-First Modeling |  Agile Example Mapping |
|---|---|---|---|
Purposedifferent | 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. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | Halber Tag pro Domain Slice | 30-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | 1-4 | 3-7 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | 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 | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | Knowledge graphValidationSemantic | Behavior-Driven DevelopmentRequirementsExamplesRefinement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
