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 RecordAcceptance Criteria WorkshopNeOn MethodologyCompetency Questions
| Criterion |  Architecture Architecture Decision Record |  Agile Acceptance Criteria Workshop |  Knowledge Modeling NeOn Methodology |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
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. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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. | 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. |
Complexitydifferent | Low | Low | High | Medium |
Timedifferent | 15-45 min | 20-40 min pro Story | Mehrere Wochen bis Monate | 2-4 h |
Participantsdifferent | 1-3 | 3-6 | 2-10 | 2-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Acceptance Criteria, Story Update | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | AgileRequirementsRefinementBehavior-Driven Development | OntologyMethodologyReuseSemanticEngineering | OntologyKnowledge graphScopeRequirementsSemantic |