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 GraphATAM (Architecture Tradeoff Analysis Method)SAAM (Software Architecture Analysis Method)
| Criterion |  Systems Thinking System Dynamics Simulation |  Systems Thinking Behavior Over Time Graph |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  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. | 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. | 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 | High | High |
Timedifferent | Mehrere Tage bis Wochen | 20-45 min | Several meetings plus preparation and analysis; total effort depends on scope | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 1-5 Modellierende, Stakeholder asynchron | 1-10 | Evaluation team, architects, and relevant stakeholders | 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 | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | 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 | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureChangeAnalysisComparisonQuality |