View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:PESTLE AnalysisATAM (Architecture Tradeoff Analysis Method)LASR (Lightweight Approach for Software Reviews)SWOT Analysis
| Criterion |  Business Strategy PESTLE Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture LASR (Lightweight Approach for Software Reviews) |  Business Strategy SWOT Analysis |
|---|---|---|---|---|
Purposedifferent | PESTLE Analysis makes political, economic, social, technological, legal, and environmental influences visible. The environment of an initiative is thereby read systematically instead of through isolated trends. | 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. | 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. | SWOT Analysis arranges strengths, weaknesses, opportunities, and threats into a compact picture of the situation. It keeps internal capabilities and external influences separate before strategic options emerge from them. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 3–4 h for initial assessment; preparation and deeper analysis additional | 30-60 min |
Participantsdifferent | 2-10 | Evaluation team, architects, and relevant stakeholders | 1 or a small team; particularly suitable for 3–4 people | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | PESTLE Map, External Risks, Strategic Questions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | 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 | SWOT matrix, Strategic options, Action list |
Tagsno overlap | StrategyMarketAnalysis | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureQualityRiskAssessmentLean | StrategyAnalysisMarketPositioning |