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 Decision Framing Workshop.
Decision Making
Decision Framing Workshop
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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Trade-off Analysis.
Decision Making
Trade-off Analysis
Purposedifferent
When a decision is poorly framed, even good answers deliver little value. A Decision Framing Workshop sharpens the problem, goal, and boundaries before the actual weighing begins.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.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.With limited resources, quality, speed, cost, and risk almost always compete with each other. Trade-off Analysis makes these tensions explicit and prevents decisions from producing hidden side effects.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
60-120 min3–4 h for initial assessment; preparation and deeper analysis additionalSeveral meetings plus preparation and analysis; total effort depends on scope45-120 min
Participantsdifferent
4-101 or a small team; particularly suitable for 3–4 peopleEvaluation team, architects, and relevant stakeholders2-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Decision Frame, Decision Question, Criteria List, Evidence PlanLean 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 checksPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsTrade-off Matrix, Criteria List, Decision Rationale, Accepted Downsides
Tagsno overlap
Decision framingAlignmentCriteriaOptions
ArchitectureQualityRiskAssessmentLean
ArchitectureQualityRiskTradeoffsStakeholders
TradeoffsDecisionCriteriaOptions
Add more methods