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 Root Cause Tree Analysis |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Family Tree Analysis |
|---|---|---|---|
Purposedifferent | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | 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. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 1-3 h | Preparation, scenario analysis, and findings review; effort depends on scope | 2-4 h |
Participantsdifferent | 2-8 | Architecture experts and stakeholders for scenarios and weighting | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Cause Tree, Evidence Notes, Countermeasures | 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 |
Tagsno overlap | Root causeTreeIncidentQuality | ArchitectureChangeAnalysisComparisonQuality | Root causePatternsIncidentSystemic |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
