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)Request for CommentsForce Field AnalysisOODA Loop
| Criterion | ![]() Architecture SAAM (Software Architecture Analysis Method) | ![]() Architecture Request for Comments | ![]() Decision Making Force Field Analysis | ![]() Decision Making OODA Loop |
|---|---|---|---|---|
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. | 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. | 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. | In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 15-60 min je Zyklus |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-20 Reviewer | 3-12 | 1-8 |
Formatdifferent | Workshop + async | 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 | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Force Field Map, Change Levers, Risk Notes | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | ArchitectureDecisionAsyncGovernance | ChangeDecisionStrategy | DecisionChangeLearningStrategy |



