View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)Hypothesis-Driven TroubleshootingBusiness Model Stress Test
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Engineering Hypothesis-Driven Troubleshooting |  Business Strategy Business Model Stress Test |
|---|---|---|---|
Purposedifferent | 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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. |
Complexitydifferent | High | Medium | High |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30-240 min | Half day |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1-6 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Stress Test Report, Action Plan per Scenario |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | TroubleshootingProblem solvingDiagnosis | StrategyBusiness modelRiskDiagnosis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
