methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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.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.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 contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.
Complexitydifferent
MediumLowHighMedium
Timedifferent
1-3 h45-90 minSeveral meetings plus preparation and analysis; total effort depends on scope1-3 h
Participantsdifferent
3-83-12Evaluation team, architects, and relevant stakeholders2-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Context Canvas, Glossary, Integration NotesForce Field Map, Change Levers, Risk NotesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
Domain-Driven DesignBoundariesModeling
ChangeDecisionStrategy
ArchitectureQualityRiskTradeoffsStakeholders
Domain-Driven DesignBoundariesStrategy
Add more methods