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)
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Paper illustration of a SWOT matrix with four separated quadrants and marked strategic options.
Business Strategy
SWOT Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
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.GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.SWOT Analysis arranges strengths, weaknesses, opportunities, and threats into a compact picture of the situation. It keeps internal capabilities and external influences separate before strategic options emerge from them.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
HighMediumLowHigh
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope1-3 h30-60 minPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
Evaluation team, architects, and relevant stakeholders2-83-12Architecture experts and stakeholders for scenarios and weighting
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 investigationsGap Matrix, Action Plan, Risk NotesSWOT matrix, Strategic options, Action listDomain 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
ArchitectureQualityRiskTradeoffsStakeholders
StrategyAnalysisPlanning
StrategyAnalysisMarketPositioning
ArchitectureChangeAnalysisComparisonQuality
Add more methods