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 Change Analysis.
Operations
Change Analysis
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
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.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.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.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
1-3 hPreparation, scenario analysis, and findings review; effort depends on scope45-120 min1-3 h
Participantsdifferent
2-8Architecture experts and stakeholders for scenarios and weighting2-63-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
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 alternativesChange Matrix, Cause Hypotheses, Validation Questions, Action ListDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
ArchitectureChangeAnalysisComparisonQuality
ChangeRoot causeTroubleshootingComparison
Domain-Driven DesignContextBoundaries
Add more methods