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 InnovationATAM (Architecture Tradeoff Analysis Method)Design Thinking
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Product Discovery Outcome-Driven Innovation |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Innovation Design Thinking |
|---|---|---|---|---|
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. | 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 complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. |
Complexitysame | High | High | High | High |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | Mehrere Wochen | Several meetings plus preparation and analysis; total effort depends on scope | 1 Tag bis mehrere Wochen |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 2-6 researchers plus sample | Evaluation team, architects, and relevant stakeholders | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
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 | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Problem Statement, Prototype, Test Learnings |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | OutcomesInnovationResearchQuantitative | ArchitectureQualityRiskTradeoffsStakeholders | InnovationPrototypeResearch |