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
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.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.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.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
1-2 Tage1-3 Tage1-2 h15-45 min
Participantsdifferent
1-41-43-101-3
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewArchitecture Views, Cross-view Notes, RationaleArchitecture Canvas, Goals, Constraints, Quality AttributesADR File, Decision Log, Rationale
Tags1 shared
ArchitectureDocumentationCommunication
DocumentationStakeholdersArchitecture
CanvasArchitectureAlignmentWorkshop
ArchitectureRationaleDocumentationGovernance
Add more methods