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
Paper illustration of Ontology Design Patterns with its method-specific working model.
Knowledge Modeling
Ontology Design Patterns
Paper illustration of NeOn Methodology with its method-specific working model.
Knowledge Modeling
NeOn Methodology
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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.Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles.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.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.
Complexitydifferent
LowMediumHighHigh
Timedifferent
60-90 min1-3 h pro PatternMehrere Wochen bis MonateSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
4-121-62-10Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogSelected Patterns, Adapted Schema Fragments, Pattern DocumentationOntology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation ReportPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
RiskArchitectureWorkshopValidation
OntologyPatternsReuseSemanticModeling
OntologyMethodologyReuseSemanticEngineering
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods