methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration of a Strategy Canvas with several value curves
Business Strategy
Blue Ocean Strategy Canvas
Paper illustration of a SWOT matrix with four separated quadrants and marked strategic options.
Business Strategy
SWOT Analysis
Purposedifferent
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 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.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
MediumHighMediumLow
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additionalPreparation, scenario analysis, and findings review; effort depends on scope2-4 h30-60 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 peopleArchitecture experts and stakeholders for scenarios and weighting3-103-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
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 checksDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesStrategy Canvas, Value Curve, ERRC ActionsSWOT matrix, Strategic options, Action list
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
ArchitectureChangeAnalysisComparisonQuality
StrategyPositioningInnovationValue
StrategyAnalysisMarketPositioning
Add more methods