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 AnalysisLASR (Lightweight Approach for Software Reviews)Architecture Communication CanvasC4 Model
| Criterion | ![]() Engineering Failure Scenario Analysis | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Architecture Architecture Communication Canvas | ![]() Architecture C4 Model |
|---|---|---|---|---|
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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-120 min | 1-4 h |
Participantsdifferent | 3-8 | 1 or a small team; particularly suitable for 3–4 people | 2-8 | 1-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response 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 | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | FailureResilienceRisk | ArchitectureQualityRiskAssessmentLean | ArchitectureCommunicationStakeholdersCanvas | ArchitectureCommunicationVisualization |



