View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordCompetency QuestionsLinked Open TermsAcceptance Criteria Workshop
| Criterion |  Architecture Architecture Decision Record |  Knowledge Modeling Competency Questions |  Knowledge Modeling Linked Open Terms |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 15-45 min | 2-4 h | Wochen bis Monate | 20-40 min pro Story |
Participantsdifferent | 1-3 | 2-8 | 2-8 | 3-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Acceptance Criteria, Story Update |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | OntologyKnowledge graphScopeRequirementsSemantic | OntologyMethodologyAgileSemantic | AgileRequirementsRefinementBehavior-Driven Development |