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 AnalysisSAAM (Software Architecture Analysis Method)Request for CommentsChange Analysis
| Criterion |  Decision Making Force Field Analysis |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture Request for Comments |  Operations Change Analysis |
|---|---|---|---|---|
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. | 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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 | Low | High | Medium | Medium |
Timedifferent | 45-90 min | Preparation, scenario analysis, and findings review; effort depends on scope | 1-3 Wochen vom Draft bis zur Entscheidung | 45-120 min |
Participantsdifferent | 3-12 | Architecture experts and stakeholders for scenarios and weighting | 3-20 Reviewer | 2-6 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | 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 | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Change Matrix, Cause Hypotheses, Validation Questions, Action List |
Tagsno overlap | ChangeDecisionStrategy | ArchitectureChangeAnalysisComparisonQuality | ArchitectureDecisionAsyncGovernance | ChangeRoot causeTroubleshootingComparison |