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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
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.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.When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additionalSeveral meetings plus preparation and analysis; total effort depends on scope60-180 min1-3 h
Participantsdifferent
1 or a small team; particularly suitable for 3–4 peopleEvaluation team, architects, and relevant stakeholders4-201-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + 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 checksPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsCynefin Map, Domain-specific Actions, Sensemaking NotesArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
ArchitectureQualityRiskTradeoffsStakeholders
ComplexitySensemakingDecision
SensemakingDecisionRationale
Add more methods