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 the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for Option Framing.
Decision Making
Option Framing
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.In early decisions, alternatives are often still vague, incomplete, or blended together. Option Framing brings every possibility into a comparable form and makes visible which variant actually fits the question.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.
Complexitydifferent
HighLowMediumHigh
Timedifferent
Preparation, scenario analysis, and findings review; effort depends on scope45-90 min45-120 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
Architecture experts and stakeholders for scenarios and weighting3-123-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshopWorkshop + 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 alternativesForce Field Map, Change Levers, Risk NotesOption Frames, Assumption Notes, Comparable Shortlist, Decision InputsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
ArchitectureChangeAnalysisComparisonQuality
ChangeDecisionStrategy
OptionsDecision framingStrategyComparison
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods