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 of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects 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.Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.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
HighHighHighMedium
Timedifferent
Preparation, scenario analysis, and findings review; effort depends on scopeHalf day2-6 h45-120 min
Participantsdifferent
Architecture experts and stakeholders for scenarios and weighting3-123-102-6
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + 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 alternativesLeverage Map, Action StrategyFMEA Table, Risk Priority, Mitigation ActionsChange Matrix, Cause Hypotheses, Validation Questions, Action List
Tagsno overlap
ArchitectureChangeAnalysisComparisonQuality
Systems thinkingChangeStrategy
RiskQualityOperationsRoot cause
ChangeRoot causeTroubleshootingComparison
Add more methods