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
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 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration of Linked Open Terms with its method-specific working model.
Knowledge Modeling
Linked Open Terms
Paper illustration of NeOn Methodology with its method-specific working model.
Knowledge Modeling
NeOn Methodology
Purposedifferent
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 an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently.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
MediumHighMediumHigh
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional1-6 WochenWochen bis MonateMehrere Wochen bis Monate
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people4-102-82-10
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Lean 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 checks8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanOntology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance PlanOntology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
QualityProblem solvingRoot cause
OntologyMethodologyAgileSemantic
OntologyMethodologyReuseSemanticEngineering
Add more methods