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 |  Business Strategy Ansoff Matrix |  Domain Modeling Bounded Context Canvas |
|---|---|---|---|---|
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. | The Ansoff Matrix organizes growth options by market and product relation. It helps weigh expansion, diversification, and adaptation cleanly against each other. | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 h | 45-90 min | 1-3 h |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-8 | 2-8 | 3-8 |
Formatsame | Workshop + async | 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 | Ansoff Matrix, Growth Options, Risk Notes | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | Domain-Driven DesignBoundariesStrategy | GrowthStrategyMarketPortfolio | Domain-Driven DesignBoundariesModeling |