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
Anonymous individual judgments pass through feedback loops to form a distribution.
Decision Making
Delphi Method
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together.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.In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.
Complexitydifferent
HighHighMediumHigh
Timedifferent
1-4 WochenSeveral meetings plus preparation and analysis; total effort depends on scope15-60 min je ZyklusPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
6-30 ExpertenEvaluation team, architects, and relevant stakeholders1-8Architecture experts and stakeholders for scenarios and weighting
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Expert Forecast, Consensus Range, Assumption NotesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsSituation Assessment, Decision Loop, Action UpdatesDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives
Tagsno overlap
ForecastingExpertsDecisionStrategy
ArchitectureQualityRiskTradeoffsStakeholders
DecisionChangeLearningStrategy
ArchitectureChangeAnalysisComparisonQuality
Add more methods