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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
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 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 Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
LowLowMediumMedium
Timedifferent
1-2 Tage1-2 h60-120 min1-2 h
Participantsdifferent
1-43-102-84-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewArchitecture Canvas, Goals, Constraints, Quality AttributesCommunication Canvas, Stakeholder Messages, Architecture Communication PlanAlignment Map, Open Issues, Decision Questions
Tagsno overlap
ArchitectureDocumentationCommunication
CanvasArchitectureAlignmentWorkshop
ArchitectureCommunicationStakeholdersCanvas
AlignmentStakeholdersStrategyFacilitation
Add more methods