View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Porter Five ForcesLASR (Lightweight Approach for Software Reviews)PESTLE AnalysisSAAM (Software Architecture Analysis Method)
| Criterion |  Business Strategy Porter Five Forces |  Architecture LASR (Lightweight Approach for Software Reviews) |  Business Strategy PESTLE Analysis |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
Purposedifferent | Porter Five Forces analyzes the forces that shape competitive pressure and profitability in a market. The view of market structure goes beyond individual competitors and reveals systemic pressure points. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 3–4 h for initial assessment; preparation and deeper analysis additional | 1-3 h | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 2-10 | Architecture experts and stakeholders for scenarios and weighting |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Five Forces Analysis, Competitive Risks, Strategic Options | 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 | PESTLE Map, External Risks, Strategic Questions | 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 |
Tagsno overlap | StrategyCompetitionMarket | ArchitectureQualityRiskAssessmentLean | StrategyMarketAnalysis | ArchitectureChangeAnalysisComparisonQuality |