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 Pareto Analysis |  Architecture SAAM (Software Architecture Analysis Method) |  Decision Making OODA Loop |
|---|---|---|---|
Purposedifferent | In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle. | 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 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 | Low | High | Medium |
Timedifferent | 30-60 min | Preparation, scenario analysis, and findings review; effort depends on scope | 15-60 min je Zyklus |
Participantsdifferent | 1-6 | Architecture experts and stakeholders for scenarios and weighting | 1-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pareto Chart, Top Causes, Focus List | 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 | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | PrioritizationQualityFocusRoot cause | ArchitectureChangeAnalysisComparisonQuality | DecisionChangeLearningStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
