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)Outcome-Driven InnovationChange AnalysisATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Product Discovery Outcome-Driven Innovation |  Operations Change Analysis |  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. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | 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. | 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 | High | High | Medium | High |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | Mehrere Wochen | 45-120 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 2-6 researchers plus sample | 2-6 | Evaluation team, architects, and relevant stakeholders |
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 | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Prioritized 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 | OutcomesInnovationResearchQuantitative | ChangeRoot causeTroubleshootingComparison | ArchitectureQualityRiskTradeoffsStakeholders |