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 AnalysisSoftware Architecture CanvasFishbone Diagram
| Criterion |  Engineering Failure Scenario Analysis |  Operations Failure Mode and Effects Analysis |  Architecture Software Architecture Canvas |  Operations Fishbone Diagram |
|---|---|---|---|---|
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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 1-3 h | 2-6 h | 1-2 h | 30-60 min |
Participantsdifferent | 3-8 | 3-10 | 3-10 | 2-8 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | FMEA Table, Risk Priority, Mitigation Actions | Architecture Canvas, Goals, Constraints, Quality Attributes | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | FailureResilienceRisk | RiskQualityOperationsRoot cause | CanvasArchitectureAlignmentWorkshop | Root causeQualityOperations |