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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
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)
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent
LowLowMediumLow
Timedifferent
1-2 Tage20–45 min3–4 h for initial assessment; preparation and deeper analysis additional15-45 min
Participantsdifferent
1-4Small cross-functional group1 or a small team; particularly suitable for 3–4 people1-3
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewRisk list, Mitigation plan, Assumption logLean 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 checksADR File, Decision Log, Rationale
Tagsno overlap
ArchitectureDocumentationCommunication
RiskDecisionFailurePlanning
ArchitectureQualityRiskAssessmentLean
ArchitectureRationaleDocumentationGovernance
Add more methods