View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Trade-off AnalysisLASR (Lightweight Approach for Software Reviews)ICE ScoringATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Decision Making Trade-off Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |  Product Strategy ICE Scoring |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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 | Medium | Medium | Low | High |
Timedifferent | 45-120 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 2-8 | Evaluation team, architects, and relevant stakeholders |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Trade-off Matrix, Criteria List, Decision Rationale, Accepted Downsides | 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 | ICE Table, Top Idea List | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | TradeoffsDecisionCriteriaOptions | ArchitectureQualityRiskAssessmentLean | PrioritizationScoringGrowthDecision | ArchitectureQualityRiskTradeoffsStakeholders |