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 Linked Open Terms with its method-specific working model.
Knowledge Modeling
Linked Open Terms
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 for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently.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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
Wochen bis Monate1-3 h pro Pattern3–4 h for initial assessment; preparation and deeper analysis additional2-6 h
Participantsdifferent
2-81-61 or a small team; particularly suitable for 3–4 people3-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance PlanSelected 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 checksFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
OntologyMethodologyAgileSemantic
OntologyPatternsReuseSemanticModeling
ArchitectureQualityRiskAssessmentLean
RiskQualityOperationsRoot cause
Add more methods