View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Failure Scenario AnalysisFailure Mode and Effects AnalysisChange AnalysisSAAM (Software Architecture Analysis Method)
| Criterion |  Engineering Failure Scenario Analysis |  Operations Failure Mode and Effects Analysis |  Operations Change Analysis |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
Purposedifferent | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | 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. | 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. | 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 | Medium | High | Medium | High |
Timedifferent | 1-3 h | 2-6 h | 45-120 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 3-8 | 3-10 | 2-6 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | FMEA Table, Risk Priority, Mitigation Actions | Change Matrix, Cause Hypotheses, Validation Questions, Action List | 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 | FailureResilienceRisk | RiskQualityOperationsRoot cause | ChangeRoot causeTroubleshootingComparison | ArchitectureChangeAnalysisComparisonQuality |