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 DiagramSystem Dynamics SimulationATAM (Architecture Tradeoff Analysis Method)SAAM (Software Architecture Analysis Method)
| Criterion |  Systems Thinking Stock and Flow Diagram |  Systems Thinking System Dynamics Simulation |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitysame | High | High | High | High |
Timedifferent | 2-6 h | Mehrere Tage bis Wochen | Several meetings plus preparation and analysis; total effort depends on scope | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 1-6 | 1-5 Modellierende, Stakeholder asynchron | Evaluation team, architects, and relevant stakeholders | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Stock and Flow Model, Dynamics Notes, Simulation Hypotheses | Simulation Model, Scenario Reports | 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 | DynamicsSimulationFeedbackSystems thinking | Systems thinkingDynamicsSimulationAnalysis | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureChangeAnalysisComparisonQuality |