View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:CATWOE AnalysisConstraint AnalysisATAM (Architecture Tradeoff Analysis Method)LASR (Lightweight Approach for Software Reviews)
| Criterion |  Systems Thinking CATWOE Analysis |  Decision Making Constraint Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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. | 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. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 45-90 min | 30-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 3-8 | 2-8 | Evaluation team, architects, and relevant stakeholders | 1 or a small team; particularly suitable for 3–4 people |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | 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 checks |
Tagsno overlap | Systems thinkingFramingStakeholders | ConstraintsDecisionPlanningOptions | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureQualityRiskAssessmentLean |