View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Domain Context Map |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Decision Making Force Field Analysis |
|---|---|---|---|
Purposedifferent | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min |
Participantsdifferent | 3-10 | Evaluation team, architects, and relevant stakeholders | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | Domain-Driven DesignContextBoundaries | ArchitectureQualityRiskTradeoffsStakeholders | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
