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 Soft Systems Methodology.
Systems Thinking
Soft Systems Methodology
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
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.Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action.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.
Complexitydifferent
MediumHighHighMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional0.5-3 TageSeveral meetings plus preparation and analysis; total effort depends on scope60-180 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people5-15Evaluation team, architects, and relevant stakeholders4-20
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
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 checksRich Picture, Root Definitions, Conceptual Models, Change AgendaPrioritized 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 Notes
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
Soft systemsComplexitySensemakingSystems thinking
ArchitectureQualityRiskTradeoffsStakeholders
ComplexitySensemakingDecision
Add more methods