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 Product Vision Board with its method-specific working model.
Product Strategy
Product Vision Board
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture 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.When a product needs a shared direction, it connects target audience, benefit, and business picture in a clear vision. It makes the envisioned future legible for the team.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 Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.
Complexitydifferent
MediumLowHighLow
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional1-2 hPreparation, scenario analysis, and findings review; effort depends on scope1-2 h
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people2-8Architecture experts and stakeholders for scenarios and weighting3-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
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 checksProduct Vision Board, Vision Statement, Assumptions and Validation QuestionsDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
VisionCanvasStrategyAlignment
ArchitectureChangeAnalysisComparisonQuality
CanvasArchitectureAlignmentWorkshop
Add more methods