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
Paper illustration of a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
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.Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently.When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound.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
HighMediumLowMedium
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scopeWochen bis Monate30-60 min2-4 h
Participantsdifferent
Evaluation team, architects, and relevant stakeholders2-83-72-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + 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 PlanExample Map, Acceptance Criteria, Open QuestionsCompetency Question Set, Required Concepts, Test Queries, Coverage Matrix
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
OntologyMethodologyAgileSemantic
Behavior-Driven DevelopmentRequirementsExamplesRefinement
OntologyKnowledge graphScopeRequirementsSemantic
Add more methods