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 for Change Analysis.
Operations
Change Analysis
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
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)
Purposedifferent
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.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 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.
Complexitydifferent
MediumHighMediumHigh
Timedifferent
45-120 min1-6 Wochen2-8 hPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
2-64-105-12Architecture experts and stakeholders for scenarios and weighting
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Change Matrix, Cause Hypotheses, Validation Questions, Action List8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanEvent 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 alternatives
Tagsno overlap
ChangeRoot causeTroubleshootingComparison
QualityProblem solvingRoot cause
Domain-Driven DesignEventsDiscoveryWorkshop
ArchitectureChangeAnalysisComparisonQuality
Add more methods