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) | ![]() Decision Making Constraint Analysis | ![]() Business Strategy GAP Analysis |
|---|---|---|---|
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 an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. |
Complexitydifferent | High | Low | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30-90 min | 1-3 h |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-8 | 2-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 | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Gap Matrix, Action Plan, Risk Notes |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | ConstraintsDecisionPlanningOptions | StrategyAnalysisPlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






