View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:OODA LoopDecision MatrixATAM (Architecture Tradeoff Analysis Method)LASR (Lightweight Approach for Software Reviews)
| Criterion |  Decision Making OODA Loop |  Decision Making Decision Matrix |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | 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. | When several options collide with several criteria, comparison quickly becomes subjective. A Decision Matrix makes the trade-off visible and brings weighting, criteria, and options into a shared logic. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 15-60 min je Zyklus | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 1-8 | 2-8 | Evaluation team, architects, and relevant stakeholders | 1 or a small team; particularly suitable for 3–4 people |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Situation Assessment, Decision Loop, Action Updates | Decision Matrix, Scoring Rationale, Selected Option | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks |
Tagsno overlap | DecisionChangeLearningStrategy | DecisionCriteriaScoringTradeoffs | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureQualityRiskAssessmentLean |