View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:MORT AnalysisLASR (Lightweight Approach for Software Reviews)Family Tree AnalysisBarrier Analysis
| Criterion |  Operations MORT Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |  Operations Family Tree Analysis |  Operations Barrier Analysis |
|---|---|---|---|---|
Purposedifferent | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | 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 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. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | Mehrere Tage bis Wochen | 3–4 h for initial assessment; preparation and deeper analysis additional | 2-4 h | 2-4 h |
Participantsdifferent | 2-6 | 1 or a small team; particularly suitable for 3–4 people | 2-6 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | 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 | Family Tree Diagram, Pattern Notes, Systemic Measures | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | Root causeSafetySystemicIncident | ArchitectureQualityRiskAssessmentLean | Root causePatternsIncidentSystemic | Root causeSafetyIncident |