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 for TOWS Matrix.
Business Strategy
TOWS Matrix
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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
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.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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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.
Complexitydifferent
MediumMediumLowHigh
Timedifferent
1-2 h3–4 h for initial assessment; preparation and deeper analysis additional15-45 minPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
3-101 or a small team; particularly suitable for 3–4 people1-3Architecture experts and stakeholders for scenarios and weighting
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
TOWS Matrix, Strategic Options, Priority ActionsLean 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 checksADR File, Decision Log, RationaleDomain 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
Tagsno overlap
StrategyAnalysisOptions
ArchitectureQualityRiskAssessmentLean
ArchitectureRationaleDocumentationGovernance
ArchitectureChangeAnalysisComparisonQuality
Add more methods