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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture 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)
Paper illustration for Risk Storming.
Architecture
Risk Storming
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.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.
Complexitydifferent
MediumLowMediumLow
Timedifferent
60-120 min1-2 h3–4 h for initial assessment; preparation and deeper analysis additional60-90 min
Participantsdifferent
2-83-101 or a small team; particularly suitable for 3–4 people4-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Communication Canvas, Stakeholder Messages, Architecture Communication PlanArchitecture Canvas, Goals, Constraints, Quality AttributesLean 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 checksAnnotated Diagram, Prioritized Risk List, Action Backlog
Tags1 shared
ArchitectureCommunicationStakeholdersCanvas
CanvasArchitectureAlignmentWorkshop
ArchitectureQualityRiskAssessmentLean
RiskArchitectureWorkshopValidation
Add more methods