View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Delphi MethodSAAM (Software Architecture Analysis Method)Business Model Stress TestLASR (Lightweight Approach for Software Reviews)
| Criterion |  Decision Making Delphi Method |  Architecture SAAM (Software Architecture Analysis Method) |  Business Strategy Business Model Stress Test |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. | 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 | High | High | Medium |
Timedifferent | 1-4 Wochen | Preparation, scenario analysis, and findings review; effort depends on scope | Half day | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 6-30 Experten | Architecture experts and stakeholders for scenarios and weighting | 3-8 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Expert Forecast, Consensus Range, Assumption Notes | 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 | Stress Test Report, Action Plan per Scenario | 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 | ForecastingExpertsDecisionStrategy | ArchitectureChangeAnalysisComparisonQuality | StrategyBusiness modelRiskDiagnosis | ArchitectureQualityRiskAssessmentLean |