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 AnalysisCausal Factor AnalysisLASR (Lightweight Approach for Software Reviews)ATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Systems Thinking CATWOE Analysis |  Operations Causal Factor Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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. | For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events. | 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. |
Complexitydifferent | Medium | High | Medium | High |
Timedifferent | 45-90 min | 2-6 h | 3–4 h for initial assessment; preparation and deeper analysis additional | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-8 | 3-10 | 1 or a small team; particularly suitable for 3–4 people | Evaluation team, architects, and relevant stakeholders |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions | 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 | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | Systems thinkingFramingStakeholders | CausalityIncidentRoot causeTimeline | ArchitectureQualityRiskAssessmentLean | ArchitectureQualityRiskTradeoffsStakeholders |