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
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Paper illustration for ALPEN Method
Operations
ALPEN Method
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
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.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.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.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
MediumLowHighHigh
Timedifferent
1-3 h10-20 min daily2-6 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-813-10Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Context Canvas, Glossary, Integration NotesDaily Plan, Time Estimates, Review NotesFMEA Table, Risk Priority, Mitigation ActionsPrioritized 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 DesignBoundariesModeling
PlanningTime managementProductivityOperations
RiskQualityOperationsRoot cause
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods