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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture 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.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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.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.
Complexitysame
LowLowLowLow
Timedifferent
1-2 Tage20–45 min1-2 h1-2 h
Participantsdifferent
1-4Small cross-functional group3-83-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewRisk list, Mitigation plan, Assumption logInception Canvas, Risks, Goal List, Open QuestionsArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
ArchitectureDocumentationCommunication
RiskDecisionFailurePlanning
AlignmentArchitectureCanvas
CanvasArchitectureAlignmentWorkshop
Add more methods