View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:SAAM (Software Architecture Analysis Method)Impact MappingATAM (Architecture Tradeoff Analysis Method)LASR (Lightweight Approach for Software Reviews)
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Product Strategy Impact Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
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 a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | 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. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. |
Complexitydifferent | High | Medium | High | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-8 | Evaluation team, architects, and relevant stakeholders | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + 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 alternatives | Impact Map, Outcome Hypotheses, Delivery Options | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | OutcomesStrategyBehaviorPlanning | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureQualityRiskAssessmentLean |