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
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration for ALPEN Method
Operations
ALPEN Method
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
1-2 Tage60-120 min10-20 min daily15-45 min
Participantsdifferent
1-42-811-3
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewCommunication Canvas, Stakeholder Messages, Architecture Communication PlanDaily Plan, Time Estimates, Review NotesADR File, Decision Log, Rationale
Tagsno overlap
ArchitectureDocumentationCommunication
ArchitectureCommunicationStakeholdersCanvas
PlanningTime managementProductivityOperations
ArchitectureRationaleDocumentationGovernance
Add more methods