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 of Value Chain Analysis with its method-specific working model.
Business Strategy
Value Chain Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration of a Business Model Canvas with nine connected compartments, a few notes and symbols for customers, delivery and economic relationships.
Business Strategy
Business Model Canvas
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.Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list.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 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.
Complexitydifferent
MediumHighHighMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additionalHalf dayPreparation, scenario analysis, and findings review; effort depends on scope1-2 h
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people3-8Architecture experts and stakeholders for scenarios and weighting2-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
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 checksValue Chain Map, Lever ListDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesBusiness Model Canvas, Assumption List, Business Hypotheses
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
StrategyBusiness modelDiagnosisAnalysis
ArchitectureChangeAnalysisComparisonQuality
Business modelStrategyValueInnovation
Add more methods