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 | ![]() Agile Three Amigos | ![]() Knowledge Modeling NeOn Methodology | ![]() Knowledge Modeling Ontology Design Patterns |
|---|---|---|---|---|
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. | When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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. |
Complexitydifferent | Low | Low | High | Medium |
Timedifferent | 30-60 min | 15-30 min | Mehrere Wochen bis Monate | 1-3 h pro Pattern |
Participantsdifferent | 3-7 | 3 | 2-10 | 1-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Clarified Story, Test Examples, Open Questions | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Selected Patterns, Adapted Schema Fragments, Pattern Documentation |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CollaborationBehavior-Driven DevelopmentQualityRefinement | OntologyMethodologyReuseSemanticEngineering | OntologyPatternsReuseSemanticModeling |



