View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Systems Thinking System Dynamics Simulation |  Systems Thinking Wardley Mapping |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | High | High | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | Mehrere Tage bis Wochen | 1-3 h |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 1-5 Modellierende, Stakeholder asynchron | 2-10 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | 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 | Simulation Model, Scenario Reports | Wardley Map, Strategic Options, Evolution Notes |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | Systems thinkingDynamicsSimulationAnalysis | StrategySystems thinkingDynamics |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
