View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Systems Mapping |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Change Analysis |
|---|---|---|---|
Purposedifferent | 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. | 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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 1-3 h | Preparation, scenario analysis, and findings review; effort depends on scope | 45-120 min |
Participantsdifferent | 3-12 | Architecture experts and stakeholders for scenarios and weighting | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | System Map, Dependencies, Leverage Points | 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 | Change Matrix, Cause Hypotheses, Validation Questions, Action List |
Tags1 shared | Systems thinkingMappingBoundariesChange | ArchitectureChangeAnalysisComparisonQuality | ChangeRoot causeTroubleshootingComparison |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
