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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.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.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-3 h1-2 h15-45 min1-2 Tage
Participantsdifferent
3-103-101-31-4
Formatdifferent
WorkshopWorkshopAsyncWorkshop + async
Outputdifferent
Process Map, Handoff List, Improvement BacklogArchitecture Canvas, Goals, Constraints, Quality AttributesADR File, Decision Log, RationaleArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ProcessOperationsImprovement
CanvasArchitectureAlignmentWorkshop
ArchitectureRationaleDocumentationGovernance
ArchitectureDocumentationCommunication
Add more methods