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
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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)
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
1-2 Tage60-120 min3–4 h for initial assessment; preparation and deeper analysis additional1-3 Tage
Participantsdifferent
1-42-81 or a small team; particularly suitable for 3–4 people1-4
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewCommunication Canvas, Stakeholder Messages, Architecture Communication PlanLean 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 checksArchitecture Views, Cross-view Notes, Rationale
Tags1 shared
ArchitectureDocumentationCommunication
ArchitectureCommunicationStakeholdersCanvas
ArchitectureQualityRiskAssessmentLean
DocumentationStakeholdersArchitecture
Add more methods