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 | ![]() Delivery RAID Log | ![]() Knowledge Modeling Ontology Design Patterns | ![]() Knowledge Modeling NeOn Methodology |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. | 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 | 15-45 min | 30 min Setup, dann laufend | 1-3 h pro Pattern | Mehrere Wochen bis Monate |
Participantsdifferent | 1-3 | 1-3 maintaining, briefing for everyone | 1-6 | 2-10 |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | OntologyPatternsReuseSemanticModeling | OntologyMethodologyReuseSemanticEngineering |



