View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:SAAM (Software Architecture Analysis Method)Scatter DiagramATAM (Architecture Tradeoff Analysis Method)Change Analysis
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Scatter Diagram |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  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 the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | 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. | 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 | High | Low | High | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 30-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 45-120 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 1-4 | Evaluation team, architects, and relevant stakeholders | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + 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 alternatives | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Change Matrix, Cause Hypotheses, Validation Questions, Action List |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | Root causeQualityVisualization | ArchitectureQualityRiskTradeoffsStakeholders | ChangeRoot causeTroubleshootingComparison |