View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Force Field Analysis |  Architecture Request for Comments |  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. | 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. | 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 | Medium | High |
Timedifferent | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 3-12 | 3-20 Reviewer | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | 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 | ArchitectureDecisionAsyncGovernance | ArchitectureChangeAnalysisComparisonQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
