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 MapATAM (Architecture Tradeoff Analysis Method)Power Interest GridStakeholder Mapping
| Criterion |  Domain Modeling Context Map |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Power Interest Grid |  Facilitation Stakeholder 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. | 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 many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min | 60–90 min |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | 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 | Power Interest Grid, Strategy per Stakeholder | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ArchitectureQualityRiskTradeoffsStakeholders | StakeholdersFacilitationAlignmentPlanning | StakeholdersAlignmentFacilitationChange |