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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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.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.With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-3 h15-45 min1-2 h Setup, laufend1-2 Tage
Participantsdifferent
3-81-311-4
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop + async
Outputdifferent
Context Canvas, Glossary, Integration NotesADR File, Decision Log, RationaleAction Lists, Project List, Review RoutineArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
Domain-Driven DesignBoundariesModeling
ArchitectureRationaleDocumentationGovernance
ProductivityPlanningTasksExecution
ArchitectureDocumentationCommunication
Add more methods