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 of a four-quadrant grid with tasks sorted by importance and urgency and translated into actions.
Decision Making
Eisenhower Matrix
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for Pareto Analysis
Decision Making
Pareto Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped.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.In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.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
LowHighLowHigh
Timedifferent
15-30 minPreparation, scenario analysis, and findings review; effort depends on scope30-60 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-6Architecture experts and stakeholders for scenarios and weighting1-6Evaluation team, architects, and relevant stakeholders
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Eisenhower Matrix, Action List, Delegation NotesDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesPareto Chart, Top Causes, Focus ListPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
PrioritizationFocusTasks
ArchitectureChangeAnalysisComparisonQuality
PrioritizationQualityFocusRoot cause
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods