View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Bounded Context CanvasContext MapATAM (Architecture Tradeoff Analysis Method)Business Model Stress Test
| Criterion | ![]() Domain Modeling Bounded Context Canvas | ![]() Domain Modeling Context Map | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Business Strategy Business Model Stress Test |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. |
Complexitydifferent | Medium | Medium | High | High |
Timedifferent | 1-3 h | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | Half day |
Participantsdifferent | 3-8 | 2-8 | Evaluation team, architects, and relevant stakeholders | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Canvas, Glossary, Integration Notes | Context Map, Integration Patterns, Boundary Notes | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Stress Test Report, Action Plan per Scenario |
Tagsno overlap | Domain-Driven DesignBoundariesModeling | Domain-Driven DesignBoundariesStrategy | ArchitectureQualityRiskTradeoffsStakeholders | StrategyBusiness modelRiskDiagnosis |



