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
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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
The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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.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
MediumLowMediumMedium
Timedifferent
60-120 min15-45 min3–4 h for initial assessment; preparation and deeper analysis additional1-3 Tage
Participantsdifferent
2-81-31 or a small team; particularly suitable for 3–4 people1-4
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Communication Canvas, Stakeholder Messages, Architecture Communication PlanADR File, Decision Log, RationaleLean 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
ArchitectureCommunicationStakeholdersCanvas
ArchitectureRationaleDocumentationGovernance
ArchitectureQualityRiskAssessmentLean
DocumentationStakeholdersArchitecture
Add more methods