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 of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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
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.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
LowLowMediumMedium
Timedifferent
15-45 min1-2 Tage3–4 h for initial assessment; preparation and deeper analysis additional60-120 min
Participantsdifferent
1-31-41 or a small team; particularly suitable for 3–4 people2-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleArchitecture 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
Tags1 shared
ArchitectureRationaleDocumentationGovernance
ArchitectureDocumentationCommunication
ArchitectureQualityRiskAssessmentLean
ArchitectureCommunicationStakeholdersCanvas
Add more methods