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 EstimationATAM (Architecture Tradeoff Analysis Method)Delphi MethodLASR (Lightweight Approach for Software Reviews)
| Criterion |  Decision Making Three-Point Estimation |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Decision Making Delphi Method |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
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. | 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 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. | 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 | Medium | High | High | Medium |
Timedifferent | 10-30 min je Item | Several meetings plus preparation and analysis; total effort depends on scope | 1-4 Wochen | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 1-8 | Evaluation team, architects, and relevant stakeholders | 6-30 Experten | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Three-Point Estimate, Risk 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 | Expert Forecast, Consensus 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 |
Tagsno overlap | EstimationUncertaintyForecasting | ArchitectureQualityRiskTradeoffsStakeholders | ForecastingExpertsDecisionStrategy | ArchitectureQualityRiskAssessmentLean |