View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Failure Scenario AnalysisC4 ModelFailure Mode and Effects AnalysisLASR (Lightweight Approach for Software Reviews)
| Criterion |  Engineering Failure Scenario Analysis |  Architecture C4 Model |  Operations Failure Mode and Effects Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. | 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 | Medium | Low | High | Medium |
Timedifferent | 1-3 h | 1-4 h | 2-6 h | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 3-8 | 1-5 | 3-10 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Context Diagram, Container Diagram, Component Diagram | FMEA Table, Risk Priority, Mitigation Actions | 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 | FailureResilienceRisk | ArchitectureCommunicationVisualization | RiskQualityOperationsRoot cause | ArchitectureQualityRiskAssessmentLean |