View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)Constraint AnalysisLASR (Lightweight Approach for Software Reviews)Trade-off Analysis
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Decision Making Constraint Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |  Decision Making Trade-off Analysis |
|---|---|---|---|---|
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. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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. | With limited resources, quality, speed, cost, and risk almost always compete with each other. Trade-off Analysis makes these tensions explicit and prevents decisions from producing hidden side effects. |
Complexitydifferent | High | Low | Medium | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 45-120 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | 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 | Trade-off Matrix, Criteria List, Decision Rationale, Accepted Downsides |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | ConstraintsDecisionPlanningOptions | ArchitectureQualityRiskAssessmentLean | TradeoffsDecisionCriteriaOptions |