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 with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Purposedifferent
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 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.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.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
HighMediumMediumMedium
Timedifferent
Preparation, scenario analysis, and findings review; effort depends on scope1-3 h1-3 h1-3 h
Participantsdifferent
Architecture experts and stakeholders for scenarios and weighting3-103-82-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesDomain Context Map, Boundary Notes, Ownership MapContext Canvas, Glossary, Integration NotesContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
ArchitectureChangeAnalysisComparisonQuality
Domain-Driven DesignContextBoundaries
Domain-Driven DesignBoundariesModeling
Domain-Driven DesignBoundariesStrategy
Add more methods