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
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
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
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.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.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
1-2 Tage1-2 h1-2 h1-2 h
Participantsdifferent
1-44-123-103-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewAlignment Map, Open Issues, Decision QuestionsArchitecture Canvas, Goals, Constraints, Quality AttributesInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
ArchitectureDocumentationCommunication
AlignmentStakeholdersStrategyFacilitation
CanvasArchitectureAlignmentWorkshop
AlignmentArchitectureCanvas
Add more methods