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 Risk Storming.
Architecture
Risk Storming
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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 problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.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
LowMediumMediumHigh
Timedifferent
60-90 min45-120 min1-4 hPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
4-122-63-8Architecture experts and stakeholders for scenarios and weighting
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogChange Matrix, Cause Hypotheses, Validation Questions, Action ListProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanDomain 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
RiskArchitectureWorkshopValidation
ChangeRoot causeTroubleshootingComparison
Root causeProblem solvingQualityIncident
ArchitectureChangeAnalysisComparisonQuality
Add more methods