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)Fault Tree AnalysisChange AnalysisLASR (Lightweight Approach for Software Reviews)
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Fault Tree Analysis |  Operations Change Analysis |  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. | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | 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. | 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 | Preparation, scenario analysis, and findings review; effort depends on scope | 2-6 h | 45-120 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-8 | 2-6 | 1 or a small team; particularly suitable for 3–4 people |
Formatsame | Workshop + async | Workshop + async | Workshop + async | 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 | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Change Matrix, Cause Hypotheses, Validation Questions, Action List | 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 | RiskRoot causeSafety | ChangeRoot causeTroubleshootingComparison | ArchitectureQualityRiskAssessmentLean |