View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Force Field AnalysisFailure Mode and Effects AnalysisSAAM (Software Architecture Analysis Method)
| Criterion |  Decision Making Force Field Analysis |  Operations Failure Mode and Effects Analysis |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|
Purposedifferent | 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | 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. |
Complexitydifferent | Low | High | High |
Timedifferent | 45-90 min | 2-6 h | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 3-12 | 3-10 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | FMEA Table, Risk Priority, Mitigation Actions | 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 |
Tagsno overlap | ChangeDecisionStrategy | RiskQualityOperationsRoot cause | ArchitectureChangeAnalysisComparisonQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
