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 Family Tree Analysis with its method-specific working model.
Operations
Family Tree 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.For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring.
Complexitysame
MediumMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional2-4 h
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people2-6
Formatsame
Workshop + 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 checksFamily Tree Diagram, Pattern Notes, Systemic Measures
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
Root causePatternsIncidentSystemic
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration of MORT Analysis with its method-specific working model.
Operations
MORT Analysis