methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Failure Scenario Analysis.
Engineering
Failure Scenario Analysis
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
1-3 h1-2 Tage3–4 h for initial assessment; preparation and deeper analysis additional60-120 min
Participantsdifferent
3-81-41 or a small team; particularly suitable for 3–4 people2-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Failure Scenarios, Risk Notes, Control Gaps, Test and Response ActionsArchitecture Document, Context View, Runtime View, Deployment ViewLean 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 checksCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
FailureResilienceRisk
ArchitectureDocumentationCommunication
ArchitectureQualityRiskAssessmentLean
ArchitectureCommunicationStakeholdersCanvas
Add more methods