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 Theory of Constraints Thinking Process.
Systems Thinking
Theory of Constraints Thinking Process
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Causal Loop Diagram workspace showing the question, observations, and next decision.
Systems Thinking
Causal Loop Diagram
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.The Theory of Constraints Thinking Process exposes a system's bottleneck and the logic behind it. It suits situations where many symptoms trace back to the same limiting relationship.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.A Causal Loop Diagram makes feedback, reinforcement, and balance in a system legible. It uncovers side effects and self-reinforcement that stay hidden in linear explanations.
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 scope1-3 h
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people4-10Evaluation team, architects, and relevant stakeholders2-8
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 checksCurrent Reality Logic, Conflict Cloud, Future Reality Tree, Implementation ObstaclesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsCausal Loop Diagram, Feedback Notes, Leverage Points
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
Theory of ConstraintsConstraintsSystems thinkingCausality
ArchitectureQualityRiskTradeoffsStakeholders
FeedbackSystems thinkingCausalityDynamics
Add more methods