View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Barrier Analysis |  Architecture SAAM (Software Architecture Analysis Method) |  Operations MORT Analysis |
|---|---|---|---|
Purposedifferent | 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. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | 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. |
Complexitydifferent | Medium | High | High |
Timedifferent | 2-4 h | Preparation, scenario analysis, and findings review; effort depends on scope | Mehrere Tage bis Wochen |
Participantsdifferent | 2-6 | Architecture experts and stakeholders for scenarios and weighting | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | Root causeSafetyIncident | ArchitectureChangeAnalysisComparisonQuality | Root causeSafetySystemicIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
