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) |  Agile Specification by Example |  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 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. | 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 | Medium | High |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 60-90 min pro Feature | Mehrere Wochen bis Monate |
Participantsdifferent | Designers, developers as users, and facilitation | 3-6 | 2-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Example Table, Acceptance Tests | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | AgileRequirementsExamplesBehavior-Driven Development | OntologyMethodologyReuseSemanticEngineering |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
