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 |  Agile Acceptance Criteria Workshop |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
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. | 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. | 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 | High | Low | Medium |
Timedifferent | 30-60 min | Mehrere Wochen bis Monate | 20-40 min pro Story | 2-4 h |
Participantsdifferent | 3-7 | 2-10 | 3-6 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Acceptance Criteria, Story Update | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | OntologyMethodologyReuseSemanticEngineering | AgileRequirementsRefinementBehavior-Driven Development | OntologyKnowledge graphScopeRequirementsSemantic |