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
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)
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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 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.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
MediumMediumHighMedium
Timedifferent
1-3 h1-3 hSeveral meetings plus preparation and analysis; total effort depends on scope1-3 h
Participantsdifferent
2-63-8Evaluation team, architects, and relevant stakeholders2-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Standard Work Sheet, Deviation List, Improved Standard, Training NeedsContext 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 investigationsContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
LeanProcessQuality
Domain-Driven DesignBoundariesModeling
ArchitectureQualityRiskTradeoffsStakeholders
Domain-Driven DesignBoundariesStrategy
Add more methods