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 Theory of Constraints Thinking Process.
Systems Thinking
Theory of Constraints Thinking Process
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 Current Reality Tree
Systems Thinking
Current Reality Tree
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
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.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.A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once.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.
Complexitydifferent
HighMediumHighHigh
Timedifferent
0.5-3 Tage3–4 h for initial assessment; preparation and deeper analysis additional2-6 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
4-101 or a small team; particularly suitable for 3–4 people3-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Current Reality Logic, Conflict Cloud, Future Reality Tree, Implementation ObstaclesLean 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 Tree, Core Problems, Intervention IdeasPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
Theory of ConstraintsConstraintsSystems thinkingCausality
ArchitectureQualityRiskAssessmentLean
Systems thinkingRoot causeConstraintsCausality
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods