View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Stock and Flow DiagramLASR (Lightweight Approach for Software Reviews)SAAM (Software Architecture Analysis Method)Causal Loop Diagram
| Criterion |  Systems Thinking Stock and Flow Diagram |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture SAAM (Software Architecture Analysis Method) |  Systems Thinking Causal Loop Diagram |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | 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. |
Complexitydifferent | High | Medium | High | Medium |
Timedifferent | 2-6 h | 3–4 h for initial assessment; preparation and deeper analysis additional | Preparation, scenario analysis, and findings review; effort depends on scope | 1-3 h |
Participantsdifferent | 1-6 | 1 or a small team; particularly suitable for 3–4 people | Architecture experts and stakeholders for scenarios and weighting | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Stock and Flow Model, Dynamics Notes, Simulation Hypotheses | 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 | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Causal Loop Diagram, Feedback Notes, Leverage Points |
Tagsno overlap | DynamicsSimulationFeedbackSystems thinking | ArchitectureQualityRiskAssessmentLean | ArchitectureChangeAnalysisComparisonQuality | FeedbackSystems thinkingCausalityDynamics |