View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:SAAM (Software Architecture Analysis Method)Scatter Diagram5 WhysLASR (Lightweight Approach for Software Reviews)
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Scatter Diagram |  Operations 5 Whys |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
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. | 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 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. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 30-90 min | 15-30 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 1-4 | 2-6 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Workshop + async | Workshop | 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 | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Root cause notes, Countermeasures | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | Root causeQualityVisualization | Root causeIncidentLeanProblem solving | ArchitectureQualityRiskAssessmentLean |