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)
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
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for Change Analysis.
Operations
Change Analysis
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 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.Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.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
HighMediumMediumMedium
Timedifferent
Preparation, scenario analysis, and findings review; effort depends on scope2-8 h2-6 h45-120 min
Participantsdifferent
Architecture experts and stakeholders for scenarios and weighting5-122-82-6
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 alternativesEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsEvent Model, UI Flow, Commands, Read ModelsChange Matrix, Cause Hypotheses, Validation Questions, Action List
Tagsno overlap
ArchitectureChangeAnalysisComparisonQuality
Domain-Driven DesignEventsDiscoveryWorkshop
EventsBlueprintDomain-Driven DesignBehavior
ChangeRoot causeTroubleshootingComparison
Add more methods