View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:System Dynamics SimulationBehavior Over Time GraphLASR (Lightweight Approach for Software Reviews)SAAM (Software Architecture Analysis Method)
| Criterion |  Systems Thinking System Dynamics Simulation |  Systems Thinking Behavior Over Time Graph |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | A Behavior Over Time Graph shows how a metric or observation develops over time. The method makes trends, breaks, and recurring patterns visible that get lost in snapshots. | 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. |
Complexitydifferent | High | Low | Medium | High |
Timedifferent | Mehrere Tage bis Wochen | 20-45 min | 3–4 h for initial assessment; preparation and deeper analysis additional | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 1-5 Modellierende, Stakeholder asynchron | 1-10 | 1 or a small team; particularly suitable for 3–4 people | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Simulation Model, Scenario Reports | Behavior Over Time Graph, Trend Hypotheses, Key Events | 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 |
Tagsno overlap | Systems thinkingDynamicsSimulationAnalysis | Systems thinkingPatternsDynamics | ArchitectureQualityRiskAssessmentLean | ArchitectureChangeAnalysisComparisonQuality |