View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Agile Specification by Example |  Knowledge Modeling Competency Questions |  Agile Example Mapping |
|---|---|---|---|---|
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. | 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. | 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 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 | Low | Medium | Medium | Low |
Timedifferent | 15-45 min | 60-90 min pro Feature | 2-4 h | 30-60 min |
Participantsdifferent | 1-3 | 3-6 | 2-8 | 3-7 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Example Table, Acceptance Tests | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | AgileRequirementsExamplesBehavior-Driven Development | OntologyKnowledge graphScopeRequirementsSemantic | Behavior-Driven DevelopmentRequirementsExamplesRefinement |