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 Standard Work Analysis.
Operations
Standard Work Analysis
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
Purposedifferent
When the same task is done differently depending on the person, the method exposes the reliable core. It creates comparability without unnecessarily choking off needed latitude.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.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
1-3 h1-3 hSeveral meetings plus preparation and analysis; total effort depends on scope1-3 h
Participantsdifferent
2-63-10Evaluation team, architects, and relevant stakeholders3-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Standard Work Sheet, Deviation List, Improved Standard, Training NeedsDomain 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 Notes
Tagsno overlap
LeanProcessQuality
Domain-Driven DesignContextBoundaries
ArchitectureQualityRiskTradeoffsStakeholders
Domain-Driven DesignBoundariesModeling
Add more methods