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 with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration of ICE Scoring with its method-specific working model.
Product Strategy
ICE Scoring
Paper illustration of Cost of Delay with its method-specific working model.
Delivery
Cost of Delay
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
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.When ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list.Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence.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
HighLowHighHigh
Timedifferent
Preparation, scenario analysis, and findings review; effort depends on scope30-60 min90-180 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
Architecture experts and stakeholders for scenarios and weighting2-83-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesICE Table, Top Idea ListCoD Table, Prioritization SequencePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
ArchitectureChangeAnalysisComparisonQuality
PrioritizationScoringGrowthDecision
PrioritizationDeliveryEconomicsDecision
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods