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 Specification by Example |  Agile Example Mapping |  Knowledge Modeling Competency Questions |  Knowledge Modeling Linked Open Terms |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Medium | Low | Medium | Medium |
Timedifferent | 60-90 min pro Feature | 30-60 min | 2-4 h | Wochen bis Monate |
Participantsdifferent | 3-6 | 3-7 | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | OntologyKnowledge graphScopeRequirementsSemantic | OntologyMethodologyAgileSemantic |