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 of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration of NeOn Methodology with its method-specific working model.
Knowledge Modeling
NeOn Methodology
Paper illustration of Linked Open Terms with its method-specific working model.
Knowledge Modeling
Linked Open Terms
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.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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.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
MediumMediumHighMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional45-60 minMehrere Wochen bis MonateWochen bis Monate
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people2-82-102-8
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 checksAssumption map, Test backlog, Risk rankingOntology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation ReportOntology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
AssumptionsRiskExperimentsValidation
OntologyMethodologyReuseSemanticEngineering
OntologyMethodologyAgileSemantic
Add more methods