View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ARID (Active Reviews for Intermediate Designs)Shape-First ModelingSpecification by ExampleLinked Open Terms
| Criterion | ![]() Architecture ARID (Active Reviews for Intermediate Designs) | ![]() Knowledge Modeling Shape-First Modeling | ![]() Agile Specification by Example | ![]() Knowledge Modeling Linked Open Terms |
|---|---|---|---|---|
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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | Halber Tag pro Domain Slice | 60-90 min pro Feature | Wochen bis Monate |
Participantsdifferent | Designers, developers as users, and facilitation | 1-4 | 3-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
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 Table, Acceptance Tests | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | Knowledge graphValidationSemantic | AgileRequirementsExamplesBehavior-Driven Development | OntologyMethodologyAgileSemantic |



