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
Paper illustration of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.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.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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.
Complexitysame
LowLowLowLow
Timedifferent
30-60 min1-2 h1-2 Tage60-90 min
Participantsdifferent
3-103-101-44-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Risk Matrix, Top Risk ListArchitecture Canvas, Goals, Constraints, Quality AttributesArchitecture Document, Context View, Runtime View, Deployment ViewAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
RiskDecisionPrioritizationAssessment
CanvasArchitectureAlignmentWorkshop
ArchitectureDocumentationCommunication
RiskArchitectureWorkshopValidation
Add more methods