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)Failure Mode and Effects AnalysisValue Chain Analysis
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Failure Mode and Effects Analysis |  Business Strategy Value Chain 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | 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. |
Complexitysame | High | High | High |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 2-6 h | Half day |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop | 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 | FMEA Table, Risk Priority, Mitigation Actions | Value Chain Map, Lever List |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | RiskQualityOperationsRoot cause | StrategyBusiness modelDiagnosisAnalysis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
