View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Wardley MappingSAAM (Software Architecture Analysis Method)ATAM (Architecture Tradeoff Analysis Method)System Dynamics Simulation
| Criterion |  Systems Thinking Wardley Mapping |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Systems Thinking System Dynamics Simulation |
|---|---|---|---|---|
Purposedifferent | Wardley Mapping makes visible where an offering stands today and where it can evolve. The method connects user need, value chain, and evolution stages into a strategic basis for platform, build, or buy decisions. | 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. | 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. | 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. |
Complexitydifferent | Medium | High | High | High |
Timedifferent | 1-3 h | Preparation, scenario analysis, and findings review; effort depends on scope | Several meetings plus preparation and analysis; total effort depends on scope | Mehrere Tage bis Wochen |
Participantsdifferent | 2-10 | Architecture experts and stakeholders for scenarios and weighting | Evaluation team, architects, and relevant stakeholders | 1-5 Modellierende, Stakeholder asynchron |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Wardley Map, Strategic Options, Evolution 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 | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Simulation Model, Scenario Reports |
Tagsno overlap | StrategySystems thinkingDynamics | ArchitectureChangeAnalysisComparisonQuality | ArchitectureQualityRiskTradeoffsStakeholders | Systems thinkingDynamicsSimulationAnalysis |