View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Value Chain AnalysisHypothesis-Driven TroubleshootingSAAM (Software Architecture Analysis Method)
| Criterion |  Business Strategy Value Chain Analysis |  Engineering Hypothesis-Driven Troubleshooting |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|
Purposedifferent | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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 | High | Medium | High |
Timedifferent | Half day | 30-240 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 3-8 | 1-6 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Value Chain Map, Lever List | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | 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 |
Tagsno overlap | StrategyBusiness modelDiagnosisAnalysis | TroubleshootingProblem solvingDiagnosis | ArchitectureChangeAnalysisComparisonQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
