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 AnalysisATAM (Architecture Tradeoff Analysis Method)Stakeholder Salience ModelRAID Log
| Criterion |  Engineering Failure Scenario Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Stakeholder Salience Model |  Delivery RAID Log |
|---|---|---|---|---|
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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 60-90 min | 30 min Setup, dann laufend |
Participantsdifferent | 3-8 | Evaluation team, architects, and relevant stakeholders | 3-6 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop | Workshop + async | Workshop | Async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Salience Diagram, Strategy per Class | RAID Log, Status Report Source |
Tagsno overlap | FailureResilienceRisk | ArchitectureQualityRiskTradeoffsStakeholders | StakeholdersFacilitationAlignmentGovernance | RiskTrackingStakeholdersGovernance |