View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Systems Thinking CATWOE Analysis | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Systems Thinking System Dynamics Simulation |
|---|---|---|---|
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. | 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. | System Dynamics Simulation makes assumptions about time, delay, and feedback testable through experiments. It draws relationships, patterns, and feedback loops. The result is captured as a simulation model and scenario reports. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 45-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | Mehrere Tage bis Wochen |
Participantsdifferent | 3-8 | 1 or a small team; particularly suitable for 3–4 people | 1-5 Modellierende, Stakeholder asynchron |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | 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 | Simulation Model, Scenario Reports |
Tagsno overlap | Systems thinkingFramingStakeholders | ArchitectureQualityRiskAssessmentLean | Systems thinkingDynamicsSimulationAnalysis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






