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 FramingForce Field AnalysisLASR (Lightweight Approach for Software Reviews)SAAM (Software Architecture Analysis Method)
| Criterion |  Decision Making Option Framing |  Decision Making Force Field Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 45-120 min | 45-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 3-8 | 3-12 | 1 or a small team; particularly suitable for 3–4 people | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Option Frames, Assumption Notes, Comparable Shortlist, Decision Inputs | Force Field Map, Change Levers, Risk Notes | 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 |
Tagsno overlap | OptionsDecision framingStrategyComparison | ChangeDecisionStrategy | ArchitectureQualityRiskAssessmentLean | ArchitectureChangeAnalysisComparisonQuality |