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
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Purposedifferent
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 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.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.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
HighMediumMediumMedium
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope1-3 h1-3 h1-3 h
Participantsdifferent
Evaluation team, architects, and relevant stakeholders3-103-82-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsDomain Context Map, Boundary Notes, Ownership MapContext Canvas, Glossary, Integration NotesContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
Domain-Driven DesignContextBoundaries
Domain-Driven DesignBoundariesModeling
Domain-Driven DesignBoundariesStrategy
Add more methods