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
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
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 for Option Framing.
Decision Making
Option Framing
Paper illustration for TOWS Matrix.
Business Strategy
TOWS Matrix
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.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.The TOWS Matrix connects internal strengths and weaknesses with external opportunities and threats into action-oriented strategies. It goes a step further than a pure stocktaking.
Complexitydifferent
HighMediumMediumMedium
Timedifferent
Preparation, scenario analysis, and findings review; effort depends on scope3–4 h for initial assessment; preparation and deeper analysis additional45-120 min1-2 h
Participantsdifferent
Architecture experts and stakeholders for scenarios and weighting1 or a small team; particularly suitable for 3–4 people3-83-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
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 alternativesLean 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 checksOption Frames, Assumption Notes, Comparable Shortlist, Decision InputsTOWS Matrix, Strategic Options, Priority Actions
Tagsno overlap
ArchitectureChangeAnalysisComparisonQuality
ArchitectureQualityRiskAssessmentLean
OptionsDecision framingStrategyComparison
StrategyAnalysisOptions
Add more methods