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 RecordOntology Design PatternsSpecification by ExampleLinked Open Terms
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Knowledge Modeling Ontology Design Patterns | ![]() Agile Specification by Example | ![]() Knowledge Modeling Linked Open Terms |
|---|---|---|---|---|
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. | 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. | 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 | Low | Medium | Medium | Medium |
Timedifferent | 15-45 min | 1-3 h pro Pattern | 60-90 min pro Feature | Wochen bis Monate |
Participantsdifferent | 1-3 | 1-6 | 3-6 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Example Table, Acceptance Tests | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | OntologyPatternsReuseSemanticModeling | AgileRequirementsExamplesBehavior-Driven Development | OntologyMethodologyAgileSemantic |



