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)Force Field AnalysisRequest for CommentsChange Analysis
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Decision Making Force Field Analysis |  Architecture Request for Comments |  Operations Change 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. | 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 | High | Low | Medium | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 45-120 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-12 | 3-20 Reviewer | 2-6 |
Formatdifferent | Workshop + async | Workshop | Async | 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 | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Change Matrix, Cause Hypotheses, Validation Questions, Action List |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | ChangeDecisionStrategy | ArchitectureDecisionAsyncGovernance | ChangeRoot causeTroubleshootingComparison |