View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Specification by ExampleArchitecture Communication CanvasLinked Open TermsCompetency Questions
| Criterion |  Agile Specification by Example |  Architecture Architecture Communication Canvas |  Knowledge Modeling Linked Open Terms |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 60-90 min pro Feature | 60-120 min | Wochen bis Monate | 2-4 h |
Participantsdifferent | 3-6 | 2-8 | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureCommunicationStakeholdersCanvas | OntologyMethodologyAgileSemantic | OntologyKnowledge graphScopeRequirementsSemantic |