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 Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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
Purposedifferent
When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.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.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.
Complexitydifferent
MediumLowLowMedium
Timedifferent
1-3 h30 min Setup, dann laufend1-2 Tage1-3 Tage
Participantsdifferent
3-81-3 maintaining, briefing for everyone1-41-4
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Context Canvas, Glossary, Integration NotesRAID Log, Status Report SourceArchitecture Document, Context View, Runtime View, Deployment ViewArchitecture Views, Cross-view Notes, Rationale
Tagsno overlap
Domain-Driven DesignBoundariesModeling
RiskTrackingStakeholdersGovernance
ArchitectureDocumentationCommunication
DocumentationStakeholdersArchitecture
Add more methods