View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Expectation MappingATAM (Architecture Tradeoff Analysis Method)MORT AnalysisBarrier Analysis
| Criterion |  Facilitation Expectation Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations MORT Analysis |  Operations Barrier Analysis |
|---|---|---|---|---|
Purposedifferent | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. |
Complexitydifferent | Low | High | High | Medium |
Timedifferent | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | Mehrere Tage bis Wochen | 2-4 h |
Participantsdifferent | 3-12 | Evaluation team, architects, and relevant stakeholders | 2-6 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | AlignmentStakeholdersTeam | ArchitectureQualityRiskTradeoffsStakeholders | Root causeSafetySystemicIncident | Root causeSafetyIncident |