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 MORT Analysis with its method-specific working model.
Operations
MORT Analysis
Paper illustration of NeOn Methodology with its method-specific working model.
Knowledge Modeling
NeOn Methodology
Paper illustration of Ontology Design Patterns with its method-specific working model.
Knowledge Modeling
Ontology Design Patterns
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Purposedifferent
For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps.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.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 risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.
Complexitydifferent
HighHighMediumMedium
Timedifferent
Mehrere Tage bis WochenMehrere Wochen bis Monate1-3 h pro Pattern2-4 h
Participantsdifferent
2-62-101-62-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
MORT Worksheets, Findings per Branch, Corrective Actions, Systemic RecommendationsOntology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation ReportSelected Patterns, Adapted Schema Fragments, Pattern DocumentationBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
Root causeSafetySystemicIncident
OntologyMethodologyReuseSemanticEngineering
OntologyPatternsReuseSemanticModeling
Root causeSafetyIncident
Add more methods