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 AnalysisATAM (Architecture Tradeoff Analysis Method)Family Tree AnalysisLASR (Lightweight Approach for Software Reviews)
| Criterion |  Operations MORT Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Family Tree Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. | 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 | High | Medium | Medium |
Timedifferent | Mehrere Tage bis Wochen | Several meetings plus preparation and analysis; total effort depends on scope | 2-4 h | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-6 | Evaluation team, architects, and relevant stakeholders | 2-6 | 1 or a small team; particularly suitable for 3–4 people |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Family Tree Diagram, Pattern Notes, Systemic Measures | 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 | Root causeSafetySystemicIncident | ArchitectureQualityRiskTradeoffsStakeholders | Root causePatternsIncidentSystemic | ArchitectureQualityRiskAssessmentLean |