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 Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration of a six-field PESTLE grid
Business Strategy
PESTLE Analysis
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 problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.PESTLE Analysis makes political, economic, social, technological, legal, and environmental influences visible. The environment of an initiative is thereby read systematically instead of through isolated trends.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 scope1-4 h1-3 h45-120 min
Participantsdifferent
Architecture experts and stakeholders for scenarios and weighting3-82-102-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + 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 alternativesProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanPESTLE Map, External Risks, Strategic QuestionsChange Matrix, Cause Hypotheses, Validation Questions, Action List
Tagsno overlap
ArchitectureChangeAnalysisComparisonQuality
Root causeProblem solvingQualityIncident
StrategyMarketAnalysis
ChangeRoot causeTroubleshootingComparison
Add more methods