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 SimulationATAM (Architecture Tradeoff Analysis Method)Stakeholder MappingSAAM (Software Architecture Analysis Method)
| Criterion |  Systems Thinking System Dynamics Simulation |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Stakeholder Mapping |  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. | 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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 | High | Low | High |
Timedifferent | Mehrere Tage bis Wochen | Several meetings plus preparation and analysis; total effort depends on scope | 60–90 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 1-5 Modellierende, Stakeholder asynchron | Evaluation team, architects, and relevant stakeholders | 2-8 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | 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 | Stakeholder Map, Engagement Plan, Risk Notes | 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 | ArchitectureQualityRiskTradeoffsStakeholders | StakeholdersAlignmentFacilitationChange | ArchitectureChangeAnalysisComparisonQuality |