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 Example Mapping |  Knowledge Modeling Linked Open Terms |
|---|---|---|---|---|
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 carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | Mehrere Wochen bis Monate | 60-90 min pro Feature | 30-60 min | Wochen bis Monate |
Participantsdifferent | 2-10 | 3-6 | 3-7 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan |
Tagsno overlap | OntologyMethodologyReuseSemanticEngineering | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | OntologyMethodologyAgileSemantic |