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 Intervention Mapping.
Systems Thinking
Intervention Mapping
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.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.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.
Complexitysame
HighHighHighHigh
Timedifferent
1-5 TageSeveral meetings plus preparation and analysis; total effort depends on scopeHalf dayPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
4-12Evaluation team, architects, and relevant stakeholders3-12Architecture experts and stakeholders for scenarios and weighting
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Logic Model, Change Objectives, Intervention Components, Evaluation PlanPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsLeverage Map, Action StrategyDomain 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
ChangeSystems thinkingCapability
ArchitectureQualityRiskTradeoffsStakeholders
Systems thinkingChangeStrategy
ArchitectureChangeAnalysisComparisonQuality
Add more methods