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)Example MappingShape-First ModelingNeOn Methodology
| Criterion | ![]() Architecture ARID (Active Reviews for Intermediate Designs) | ![]() Agile Example Mapping | ![]() Knowledge Modeling Shape-First Modeling | ![]() Knowledge Modeling NeOn Methodology |
|---|---|---|---|---|
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. | 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. | 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 NeOn Methodology structures ontology work as a controlled process with reuse, scenarios, and reviews. It is useful when ontologies should not emerge ad hoc but modularly and reusably. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 30-60 min | Halber Tag pro Domain Slice | Mehrere Wochen bis Monate |
Participantsdifferent | Designers, developers as users, and facilitation | 3-7 | 1-4 | 2-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Example Map, Acceptance Criteria, Open Questions | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Knowledge graphValidationSemantic | OntologyMethodologyReuseSemanticEngineering |



