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 Scatter Diagram |  Operations Change Analysis |  Operations 5 Whys |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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 | Medium | Low | High |
Timedifferent | 30-90 min | 45-120 min | 15-30 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 1-4 | 2-6 | 2-6 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Root cause 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 |
Tagsno overlap | Root causeQualityVisualization | ChangeRoot causeTroubleshootingComparison | Root causeIncidentLeanProblem solving | ArchitectureChangeAnalysisComparisonQuality |