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 Fishbone Diagram |  Operations Kepner-Tregoe |  Operations Change Analysis |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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. |
Complexitydifferent | Low | High | Medium | High |
Timedifferent | 30-60 min | 2-8 h | 45-120 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 2-8 | 2-8 | 2-6 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Fishbone Diagram, Cause Categories, Investigation Backlog | Problem Analysis, Decision Analysis, Risk Plan | Change Matrix, Cause Hypotheses, Validation Questions, Action List | 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 |
Tagsno overlap | Root causeQualityOperations | Problem solvingRoot causeDecisionOperations | ChangeRoot causeTroubleshootingComparison | ArchitectureChangeAnalysisComparisonQuality |