View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Option FramingLASR (Lightweight Approach for Software Reviews)SAAM (Software Architecture Analysis Method)TOWS Matrix
| Criterion | ![]() Decision Making Option Framing | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Architecture SAAM (Software Architecture Analysis Method) | ![]() Business Strategy TOWS Matrix |
|---|---|---|---|---|
Purposedifferent | In early decisions, alternatives are often still vague, incomplete, or blended together. Option Framing brings every possibility into a comparable form and makes visible which variant actually fits the question. | 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. | 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. | The TOWS Matrix connects internal strengths and weaknesses with external opportunities and threats into action-oriented strategies. It goes a step further than a pure stocktaking. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 45-120 min | 3–4 h for initial assessment; preparation and deeper analysis additional | Preparation, scenario analysis, and findings review; effort depends on scope | 1-2 h |
Participantsdifferent | 3-8 | 1 or a small team; particularly suitable for 3–4 people | Architecture experts and stakeholders for scenarios and weighting | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Option Frames, Assumption Notes, Comparable Shortlist, Decision Inputs | 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 | 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 | TOWS Matrix, Strategic Options, Priority Actions |
Tagsno overlap | OptionsDecision framingStrategyComparison | ArchitectureQualityRiskAssessmentLean | ArchitectureChangeAnalysisComparisonQuality | StrategyAnalysisOptions |



