View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:LASR (Lightweight Approach for Software Reviews)Causal Loop DiagramRisk StormingStock and Flow Diagram
| Criterion |  Architecture LASR (Lightweight Approach for Software Reviews) |  Systems Thinking Causal Loop Diagram |  Architecture Risk Storming |  Systems Thinking Stock and Flow 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. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | A Stock and Flow Diagram shows how stocks, inflows, and outflows shape a system over time. It is especially suited when growth, delays, or capacity limits determine the dynamics. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 3–4 h for initial assessment; preparation and deeper analysis additional | 1-3 h | 60-90 min | 2-6 h |
Participantsdifferent | 1 or a small team; particularly suitable for 3–4 people | 2-8 | 4-12 | 1-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
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 checks | Causal Loop Diagram, Feedback Notes, Leverage Points | Annotated Diagram, Prioritized Risk List, Action Backlog | Stock and Flow Model, Dynamics Notes, Simulation Hypotheses |
Tagsno overlap | ArchitectureQualityRiskAssessmentLean | FeedbackSystems thinkingCausalityDynamics | RiskArchitectureWorkshopValidation | DynamicsSimulationFeedbackSystems thinking |