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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Change Analysis.
Operations
Change Analysis
Purposedifferent
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.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.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.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
1-3 hPreparation, scenario analysis, and findings review; effort depends on scope1-4 h45-120 min
Participantsdifferent
2-8Architecture experts and stakeholders for scenarios and weighting3-82-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Context Map, Integration Patterns, Boundary NotesDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanChange Matrix, Cause Hypotheses, Validation Questions, Action List
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
ArchitectureChangeAnalysisComparisonQuality
Root causeProblem solvingQualityIncident
ChangeRoot causeTroubleshootingComparison
Add more methods