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 of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Evaporating Cloud.
Systems Thinking
Evaporating Cloud
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict.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.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
15-45 min60-120 min45-120 minPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
1-32-82-6Architecture experts and stakeholders for scenarios and weighting
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleConflict Cloud, Assumption List, Breakthrough Ideas, Next ExperimentsChange Matrix, Cause Hypotheses, Validation Questions, Action ListDomain 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
ArchitectureRationaleDocumentationGovernance
Theory of ConstraintsAssumptionsSystems thinking
ChangeRoot causeTroubleshootingComparison
ArchitectureChangeAnalysisComparisonQuality
Add more methods