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 for Intervention Mapping.
Systems Thinking
Intervention Mapping
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for Change Analysis.
Operations
Change 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.Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain.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.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.
Complexitydifferent
MediumHighHighMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional1-5 TagePreparation, scenario analysis, and findings review; effort depends on scope45-120 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people4-12Architecture experts and stakeholders for scenarios and weighting2-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + 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 checksLogic Model, Change Objectives, Intervention Components, Evaluation PlanDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesChange Matrix, Cause Hypotheses, Validation Questions, Action List
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
ChangeSystems thinkingCapability
ArchitectureChangeAnalysisComparisonQuality
ChangeRoot causeTroubleshootingComparison
Add more methods