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 Systems Mapping |  Systems Thinking Future Reality Tree |
|---|---|---|---|
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. | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. |
Complexitydifferent | High | Medium | High |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 1-3 h | 2-4 h |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-12 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
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 | System Map, Dependencies, Leverage Points | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tags1 shared | ArchitectureChangeAnalysisComparisonQuality | Systems thinkingMappingBoundariesChange | Theory of ConstraintsSystems thinkingChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
