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
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
MediumHighHighMedium
Timedifferent
2-8 hPreparation, scenario analysis, and findings review; effort depends on scope1-6 Wochen1-4 h
Participantsdifferent
5-12Architecture experts and stakeholders for scenarios and weighting4-103-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
ArchitectureChangeAnalysisComparisonQuality
QualityProblem solvingRoot cause
Root causeProblem solvingQualityIncident
Add more methods