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 Ontology Design Patterns |  Knowledge Modeling Competency Questions |  Agile Specification by Example |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h pro Pattern | 2-4 h | 60-90 min pro Feature | 30-60 min |
Participantsdifferent | 1-6 | 2-8 | 3-6 | 3-7 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | OntologyPatternsReuseSemanticModeling | OntologyKnowledge graphScopeRequirementsSemantic | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement |