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
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
1-2 Tage30 min Setup, dann laufend60-120 min1-2 h
Participantsdifferent
1-41-3 maintaining, briefing for everyone2-83-8
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewRAID Log, Status Report SourceCommunication Canvas, Stakeholder Messages, Architecture Communication PlanInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
ArchitectureDocumentationCommunication
RiskTrackingStakeholdersGovernance
ArchitectureCommunicationStakeholdersCanvas
AlignmentArchitectureCanvas
Add more methods