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 for Risk Storming.
Architecture
Risk Storming
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 NeOn Methodology with its method-specific working model.
Knowledge Modeling
NeOn Methodology
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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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.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
MediumLowMediumHigh
Timedifferent
Wochen bis Monate60-90 min3–4 h for initial assessment; preparation and deeper analysis additionalMehrere Wochen bis Monate
Participantsdifferent
2-84-121 or a small team; particularly suitable for 3–4 people2-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance PlanAnnotated Diagram, Prioritized Risk List, Action BacklogLean 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 Specification, Reuse Plan, Ontology Modules, Evaluation Report
Tagsno overlap
OntologyMethodologyAgileSemantic
RiskArchitectureWorkshopValidation
ArchitectureQualityRiskAssessmentLean
OntologyMethodologyReuseSemanticEngineering
Add more methods