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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Purposedifferent
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.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.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.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
LowLowLowMedium
Timedifferent
1-2 h1-2 h15-45 min60-120 min
Participantsdifferent
3-103-81-32-8
Formatdifferent
WorkshopWorkshopAsyncWorkshop + async
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesInception Canvas, Risks, Goal List, Open QuestionsADR File, Decision Log, RationaleCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tags1 shared
CanvasArchitectureAlignmentWorkshop
AlignmentArchitectureCanvas
ArchitectureRationaleDocumentationGovernance
ArchitectureCommunicationStakeholdersCanvas
Add more methods