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
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for ALPEN Method
Operations
ALPEN Method
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.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
MediumHighLowHigh
Timedifferent
45-90 minPreparation, scenario analysis, and findings review; effort depends on scope10-20 min dailySeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
2-5Architecture experts and stakeholders for scenarios and weighting1Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
A3 Report, Action Plan, Root Cause AnalysisDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesDaily Plan, Time Estimates, Review NotesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
LeanProblem solvingCoachingOperations
ArchitectureChangeAnalysisComparisonQuality
PlanningTime managementProductivityOperations
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods