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) |  Decision Making Force Field Analysis |  Decision Making Constraint Analysis |
|---|---|---|---|
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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. |
Complexitydifferent | High | Low | Low |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 45-90 min | 30-90 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop | 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 | Force Field Map, Change Levers, Risk Notes | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | ChangeDecisionStrategy | ConstraintsDecisionPlanningOptions |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
