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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Linked Open Terms with its method-specific working model.
Knowledge Modeling
Linked Open Terms
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration of NeOn Methodology with its method-specific working model.
Knowledge Modeling
NeOn Methodology
Purposedifferent
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.Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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
HighMediumMediumHigh
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scopeWochen bis Monate1-3 TageMehrere Wochen bis Monate
Participantsdifferent
Evaluation team, architects, and relevant stakeholders2-81-42-10
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsOntology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance PlanArchitecture Views, Cross-view Notes, RationaleOntology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
OntologyMethodologyAgileSemantic
DocumentationStakeholdersArchitecture
OntologyMethodologyReuseSemanticEngineering
Add more methods