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 RecordExample MappingOntology Design PatternsSpecification by Example
| Criterion |  Architecture Architecture Decision Record |  Agile Example Mapping |  Knowledge Modeling Ontology Design Patterns |  Agile Specification by Example |
|---|---|---|---|---|
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 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. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 15-45 min | 30-60 min | 1-3 h pro Pattern | 60-90 min pro Feature |
Participantsdifferent | 1-3 | 3-7 | 1-6 | 3-6 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Example Map, Acceptance Criteria, Open Questions | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Example Table, Acceptance Tests |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Behavior-Driven DevelopmentRequirementsExamplesRefinement | OntologyPatternsReuseSemanticModeling | AgileRequirementsExamplesBehavior-Driven Development |