View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Three-Point EstimationLASR (Lightweight Approach for Software Reviews)Delphi MethodATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Decision Making Three-Point Estimation |  Architecture LASR (Lightweight Approach for Software Reviews) |  Decision Making Delphi Method |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes. | 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 knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. | 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 | High | High |
Timedifferent | 10-30 min je Item | 3–4 h for initial assessment; preparation and deeper analysis additional | 1-4 Wochen | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-8 | 1 or a small team; particularly suitable for 3–4 people | 6-30 Experten | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Three-Point Estimate, Risk Range, Assumption Notes | 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 | Expert Forecast, Consensus Range, Assumption Notes | 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 | EstimationUncertaintyForecasting | ArchitectureQualityRiskAssessmentLean | ForecastingExpertsDecisionStrategy | ArchitectureQualityRiskTradeoffsStakeholders |