View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:SAAM (Software Architecture Analysis Method)LASR (Lightweight Approach for Software Reviews)Business Model CanvasBlue Ocean Strategy Canvas
| Criterion | ![]() Architecture SAAM (Software Architecture Analysis Method) | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Business Strategy Business Model Canvas | ![]() Business Strategy Blue Ocean Strategy Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The Business Model Canvas condenses a business model to its key building blocks and assumptions. It makes variants quickly comparable and reveals gaps before validation or implementation begins. | The Blue Ocean Strategy Canvas shows how an offering is positioned relative to the market. Differentiation thereby becomes tangible in value factors instead of merely being claimed. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 3–4 h for initial assessment; preparation and deeper analysis additional | 1-2 h | 2-4 h |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 1 or a small team; particularly suitable for 3–4 people | 2-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | 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 | 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 | Business Model Canvas, Assumption List, Business Hypotheses | Strategy Canvas, Value Curve, ERRC Actions |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | ArchitectureQualityRiskAssessmentLean | Business modelStrategyValueInnovation | StrategyPositioningInnovationValue |



