View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Knowledge Modeling NeOn Methodology | ![]() Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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. |
Complexitydifferent | Low | High | Medium |
Timedifferent | 30 min Setup, dann laufend | Mehrere Wochen bis Monate | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-10 | Designers, developers as users, and facilitation |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | RiskTrackingStakeholdersGovernance | OntologyMethodologyReuseSemanticEngineering | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






