View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Change Analysis |  Domain Modeling Context Map |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|
Purposedifferent | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 45-120 min | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-6 | 2-8 | Evaluation team, architects, and relevant stakeholders |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Change Matrix, Cause Hypotheses, Validation Questions, Action List | 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 |
Tagsno overlap | ChangeRoot causeTroubleshootingComparison | Domain-Driven DesignBoundariesStrategy | ArchitectureQualityRiskTradeoffsStakeholders |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
