View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Failure Scenario Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Knowledge Modeling Knowledge Mapping |
|---|---|---|---|
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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 h |
Participantsdifferent | 3-8 | Evaluation team, architects, and relevant stakeholders | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
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 | Knowledge Map, Critical Knowledge Areas, Transfer Plan |
Tags1 shared | FailureResilienceRisk | ArchitectureQualityRiskTradeoffsStakeholders | KnowledgeMappingRisk |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
