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 Decision Tree | ![]() Decision Making OODA Loop | ![]() Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|
Purposedifferent | For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch. | 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. | 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 | Medium | Medium | High |
Timedifferent | 30-90 min | 15-60 min je Zyklus | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 1-6 | 1-8 | Architecture experts and stakeholders for scenarios and weighting |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Decision Tree, Option Map, Assumption List | Situation Assessment, Decision Loop, Action Updates | 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 | DecisionTreeOptions | DecisionChangeLearningStrategy | ArchitectureChangeAnalysisComparisonQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






