View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling NeOn Methodology |  Agile Specification by Example |  Agile Acceptance Criteria Workshop |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | High | Medium | Low |
Timedifferent | Mehrere Wochen bis Monate | 60-90 min pro Feature | 20-40 min pro Story |
Participantsdifferent | 2-10 | 3-6 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Example Table, Acceptance Tests | Acceptance Criteria, Story Update |
Tagsno overlap | OntologyMethodologyReuseSemanticEngineering | AgileRequirementsExamplesBehavior-Driven Development | AgileRequirementsRefinementBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
