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 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
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration of Linked Open Terms with its method-specific working model.
Knowledge Modeling
Linked Open Terms
Purposedifferent
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.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently.
Complexitydifferent
HighMediumMediumMedium
Timedifferent
Mehrere Wochen bis Monate1-3 h pro Pattern3–4 h for initial assessment; preparation and deeper analysis additionalWochen bis Monate
Participantsdifferent
2-101-61 or a small team; particularly suitable for 3–4 people2-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation ReportSelected Patterns, Adapted Schema Fragments, Pattern DocumentationLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksOntology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan
Tagsno overlap
OntologyMethodologyReuseSemanticEngineering
OntologyPatternsReuseSemanticModeling
ArchitectureQualityRiskAssessmentLean
OntologyMethodologyAgileSemantic
Add more methods