View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Context MapAssumption SurfacingATAM (Architecture Tradeoff Analysis Method)Alignment Mapping
| Criterion |  Domain Modeling Context Map |  Decision Making Assumption Surfacing |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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 people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 1-3 h | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 h |
Participantsdifferent | 2-8 | 2-8 | Evaluation team, architects, and relevant stakeholders | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Assumption List, Critical Assumptions, Learning Plan | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | AssumptionsRiskDecisionDiscovery | ArchitectureQualityRiskTradeoffsStakeholders | AlignmentStakeholdersStrategyFacilitation |