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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
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)
Purposedifferent
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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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
LowMediumHighMedium
Timedifferent
1-2 Tage1-3 Tage2-6 h3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
1-41-43-101 or a small team; particularly suitable for 3–4 people
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewArchitecture Views, Cross-view Notes, RationaleFMEA Table, Risk Priority, Mitigation ActionsLean 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
ArchitectureDocumentationCommunication
DocumentationStakeholdersArchitecture
RiskQualityOperationsRoot cause
ArchitectureQualityRiskAssessmentLean
Add more methods