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
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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 C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.
Complexitydifferent
LowMediumLowLow
Timedifferent
1-2 Tage1-3 Tage30 min Setup, dann laufend1-4 h
Participantsdifferent
1-41-41-3 maintaining, briefing for everyone1-5
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewArchitecture Views, Cross-view Notes, RationaleRAID Log, Status Report SourceContext Diagram, Container Diagram, Component Diagram
Tagsno overlap
ArchitectureDocumentationCommunication
DocumentationStakeholdersArchitecture
RiskTrackingStakeholdersGovernance
ArchitectureCommunicationVisualization
Add more methods