View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Operations After-Action Review |  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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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 | Low | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 20-45 min | 15-60 min je Zyklus |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-12 | 1-8 |
Formatsame | 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 | Lessons learned, Action items, Event summary | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | LearningOperationsImprovement | DecisionChangeLearningStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
