View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Knowledge Modeling Ontology Design Patterns | ![]() Architecture arc42 | ![]() Knowledge Modeling NeOn Methodology |
|---|---|---|---|---|
Purposedifferent | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | Medium | Low | High |
Timedifferent | 30 min Setup, dann laufend | 1-3 h pro Pattern | 1-2 Tage | Mehrere Wochen bis Monate |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-6 | 1-4 | 2-10 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Architecture Document, Context View, Runtime View, Deployment View | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | RiskTrackingStakeholdersGovernance | OntologyPatternsReuseSemanticModeling | ArchitectureDocumentationCommunication | OntologyMethodologyReuseSemanticEngineering |



