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 for Risk Storming.
Architecture
Risk Storming
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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
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.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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
LowHighMediumHigh
Timedifferent
60-90 min1-4 WochenWochen bis MonateMehrere Wochen bis Monate
Participantsdifferent
4-121-62-82-10
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogExperiment results, Decision log, Learning summaryOntology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance PlanOntology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report
Tagsno overlap
RiskArchitectureWorkshopValidation
ExperimentsGrowthAnalyticsValidation
OntologyMethodologyAgileSemantic
OntologyMethodologyReuseSemanticEngineering
Add more methods