View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:NeOn MethodologyLASR (Lightweight Approach for Software Reviews)Risk StormingLinked Open Terms
| Criterion |  Knowledge Modeling NeOn Methodology |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture Risk Storming |  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. | 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. | 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. | 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 | High | Medium | Low | Medium |
Timedifferent | Mehrere Wochen bis Monate | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-90 min | Wochen bis Monate |
Participantsdifferent | 2-10 | 1 or a small team; particularly suitable for 3–4 people | 4-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | 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 checks | Annotated Diagram, Prioritized Risk List, Action Backlog | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan |
Tagsno overlap | OntologyMethodologyReuseSemanticEngineering | ArchitectureQualityRiskAssessmentLean | RiskArchitectureWorkshopValidation | OntologyMethodologyAgileSemantic |