View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Family Tree Analysis |  Operations Barrier Analysis |
|---|---|---|---|
Purposedifferent | 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 series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. | 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 | High | Medium | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 2-4 h | 2-4 h |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 2-6 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | 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 | Family Tree Diagram, Pattern Notes, Systemic Measures | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | Root causePatternsIncidentSystemic | Root causeSafetyIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
