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 for Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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.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
MediumLowMediumHigh
Timedifferent
1-3 h30 min Setup, dann laufend1-3 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-101-3 maintaining, briefing for everyone3-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Domain Context Map, Boundary Notes, Ownership MapRAID Log, Status Report SourceContext Canvas, Glossary, Integration NotesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
Domain-Driven DesignContextBoundaries
RiskTrackingStakeholdersGovernance
Domain-Driven DesignBoundariesModeling
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods