View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordCompetency QuestionsARID (Active Reviews for Intermediate Designs)NeOn Methodology
| Criterion |  Architecture Architecture Decision Record |  Knowledge Modeling Competency Questions |  Architecture ARID (Active Reviews for Intermediate Designs) |  Knowledge Modeling NeOn Methodology |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | 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. | 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 | Low | Medium | Medium | High |
Timedifferent | 15-45 min | 2-4 h | 2–4 h review as a planning range; preparation and evaluation additional | Mehrere Wochen bis Monate |
Participantsdifferent | 1-3 | 2-8 | Designers, developers as users, and facilitation | 2-10 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureEngineeringFeedbackValidationTasks | OntologyMethodologyReuseSemanticEngineering |