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 ATAM (Architecture Tradeoff Analysis Method) |  Domain Modeling Context Map |  Decision Making OODA Loop |
|---|---|---|---|
Purposedifferent | 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. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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 | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 h | 15-60 min je Zyklus |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-8 | 1-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Context Map, Integration Patterns, Boundary Notes | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | Domain-Driven DesignBoundariesStrategy | DecisionChangeLearningStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
