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 Ontology Design Patterns with its method-specific working model.
Knowledge Modeling
Ontology Design Patterns
Paper illustration of Linked Open Terms with its method-specific working model.
Knowledge Modeling
Linked Open Terms
Paper illustration of Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
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.Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles.Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently.Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures.
Complexitydifferent
HighMediumMediumMedium
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope1-3 h pro PatternWochen bis Monate2-4 h
Participantsdifferent
Evaluation team, architects, and relevant stakeholders1-62-82-8
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 investigationsSelected Patterns, Adapted Schema Fragments, Pattern DocumentationOntology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance PlanCompetency Question Set, Required Concepts, Test Queries, Coverage Matrix
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
OntologyPatternsReuseSemanticModeling
OntologyMethodologyAgileSemantic
OntologyKnowledge graphScopeRequirementsSemantic
Add more methods