methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Ontology Design Patterns with its method-specific working model.
Knowledge Modeling
Ontology Design Patterns
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Paper illustration of NeOn Methodology with its method-specific working model.
Knowledge Modeling
NeOn Methodology
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitydifferent
MediumMediumHighLow
Timedifferent
1-3 h pro Pattern45-90 minMehrere Wochen bis Monate15-30 min
Participantsdifferent
1-62-52-102-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Selected Patterns, Adapted Schema Fragments, Pattern DocumentationA3 Report, Action Plan, Root Cause AnalysisOntology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation ReportRoot cause notes, Countermeasures
Tagsno overlap
OntologyPatternsReuseSemanticModeling
LeanProblem solvingCoachingOperations
OntologyMethodologyReuseSemanticEngineering
Root causeIncidentLeanProblem solving
Add more methods