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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects 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.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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
MediumHighMediumHigh
Timedifferent
1-3 hSeveral meetings plus preparation and analysis; total effort depends on scope1-3 h2-6 h
Participantsdifferent
3-10Evaluation team, architects, and relevant stakeholders3-83-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Domain Context Map, Boundary Notes, Ownership MapPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsContext Canvas, Glossary, Integration NotesFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
Domain-Driven DesignContextBoundaries
ArchitectureQualityRiskTradeoffsStakeholders
Domain-Driven DesignBoundariesModeling
RiskQualityOperationsRoot cause
Add more methods