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 a four-quadrant grid with tasks sorted by importance and urgency and translated into actions.
Decision Making
Eisenhower Matrix
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Pareto Analysis
Decision Making
Pareto 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.It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.
Complexitydifferent
MediumLowHighLow
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional15-30 minSeveral meetings plus preparation and analysis; total effort depends on scope30-60 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people1-6Evaluation team, architects, and relevant stakeholders1-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 checksEisenhower Matrix, Action List, Delegation NotesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsPareto Chart, Top Causes, Focus List
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
PrioritizationFocusTasks
ArchitectureQualityRiskTradeoffsStakeholders
PrioritizationQualityFocusRoot cause
Add more methods