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
Empathy Mapping
UX Research
Empathy Mapping
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.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.When a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing.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.
Complexitysame
LowLowLowLow
Timedifferent
1-2 Tage1-2 h30–60 min1-2 h
Participantsdifferent
1-43-104-83-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewArchitecture Canvas, Goals, Constraints, Quality AttributesEmpathy Map, Assumptions List, Research GapsInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
ArchitectureDocumentationCommunication
CanvasArchitectureAlignmentWorkshop
SynthesisQualitativeWorkshop
AlignmentArchitectureCanvas
Add more methods