View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile Example Mapping | ![]() Architecture Architecture Decision Record | ![]() Knowledge Modeling Linked Open Terms | ![]() Knowledge Modeling NeOn Methodology |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | The NeOn Methodology structures ontology work as a controlled process with reuse, scenarios, and reviews. It is useful when ontologies should not emerge ad hoc but modularly and reusably. |
Complexitydifferent | Low | Low | Medium | High |
Timedifferent | 30-60 min | 15-45 min | Wochen bis Monate | Mehrere Wochen bis Monate |
Participantsdifferent | 3-7 | 1-3 | 2-8 | 2-10 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | ADR File, Decision Log, Rationale | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureRationaleDocumentationGovernance | OntologyMethodologyAgileSemantic | OntologyMethodologyReuseSemanticEngineering |



