View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Scatter DiagramArchitecture Decision RecordLASR (Lightweight Approach for Software Reviews)Failure Mode and Effects Analysis
| Criterion |  Operations Scatter Diagram |  Architecture Architecture Decision Record |  Architecture LASR (Lightweight Approach for Software Reviews) |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Low | Low | Medium | High |
Timedifferent | 30-90 min | 15-45 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 2-6 h |
Participantsdifferent | 1-4 | 1-3 | 1 or a small team; particularly suitable for 3–4 people | 3-10 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Scatter Plot, Korrelationsnotiz, Hypothesenliste | ADR File, Decision Log, Rationale | 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 | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | Root causeQualityVisualization | ArchitectureRationaleDocumentationGovernance | ArchitectureQualityRiskAssessmentLean | RiskQualityOperationsRoot cause |