View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Example Mapping |  Knowledge Modeling NeOn Methodology |  Knowledge Modeling Ontology Design Patterns |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. | 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. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 30-60 min | Mehrere Wochen bis Monate | 1-3 h pro Pattern | 60-90 min pro Feature |
Participantsdifferent | 3-7 | 2-10 | 1-6 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Example Table, Acceptance Tests |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | OntologyMethodologyReuseSemanticEngineering | OntologyPatternsReuseSemanticModeling | AgileRequirementsExamplesBehavior-Driven Development |