View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:SAAM (Software Architecture Analysis Method)Intervention MappingTheory of Constraints Thinking Process
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Systems Thinking Intervention Mapping |  Systems Thinking Theory of Constraints Thinking Process |
|---|---|---|---|
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. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | The Theory of Constraints Thinking Process exposes a system's bottleneck and the logic behind it. It suits situations where many symptoms trace back to the same limiting relationship. |
Complexitysame | High | High | High |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 1-5 Tage | 0.5-3 Tage |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 4-12 | 4-10 |
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 | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Current Reality Logic, Conflict Cloud, Future Reality Tree, Implementation Obstacles |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | ChangeSystems thinkingCapability | Theory of ConstraintsConstraintsSystems thinkingCausality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
