View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:RadarATAM (Architecture Tradeoff Analysis Method)Value Chain AnalysisLASR (Lightweight Approach for Software Reviews)
| Criterion |  Decision Making Radar |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Business Strategy Value Chain Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | When capabilities, maturity levels, or market positions need to be compared across several dimensions, overview is easily lost. Radar brings different characteristics into a shared picture and shows patterns faster than tables do. | 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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | 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 | 1-2 h | Several meetings plus preparation and analysis; total effort depends on scope | Half day | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-10 | Evaluation team, architects, and relevant stakeholders | 3-8 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Radar Map, Capability Scores, Action Areas | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Value Chain Map, Lever List | 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 | AssessmentPortfolioCapability | ArchitectureQualityRiskTradeoffsStakeholders | StrategyBusiness modelDiagnosisAnalysis | ArchitectureQualityRiskAssessmentLean |