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 AnalysisRisk StormingArchitecture Decision RecordQuality Attribute Workshop
| Criterion | ![]() Engineering Failure Scenario Analysis | ![]() Architecture Risk Storming | ![]() Architecture Architecture Decision Record | ![]() Architecture Quality Attribute Workshop |
|---|---|---|---|---|
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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 60-90 min | 15-45 min | 2-4 h |
Participantsdifferent | 3-8 | 4-12 | 1-3 | 5-15 |
Formatdifferent | Workshop | Workshop | Async | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Annotated Diagram, Prioritized Risk List, Action Backlog | ADR File, Decision Log, Rationale | Quality Scenarios, Priority List, Architecture Concerns |
Tagsno overlap | FailureResilienceRisk | RiskArchitectureWorkshopValidation | ArchitectureRationaleDocumentationGovernance | RequirementsArchitectureWorkshop |



