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
Affinity Diagramming
UX Research
Affinity Diagramming
Empathy Mapping
UX Research
Empathy 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.When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer.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.
Complexitysame
LowLowLowLow
Timedifferent
1-2 Tage1-2 h45–90 min30–60 min
Participantsdifferent
1-43-103-104-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewArchitecture Canvas, Goals, Constraints, Quality AttributesTheme clusters, Insight statements, Opportunity areasEmpathy Map, Assumptions List, Research Gaps
Tagsno overlap
ArchitectureDocumentationCommunication
CanvasArchitectureAlignmentWorkshop
SynthesisQualitativeRoot cause
SynthesisQualitativeWorkshop
Add more methods