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 Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Paper illustration for ALPEN Method
Operations
ALPEN Method
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.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.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.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.
Complexitysame
LowLowLowLow
Timedifferent
1-2 h1-4 h10-20 min daily1-2 Tage
Participantsdifferent
2-81-511-4
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeContext Diagram, Container Diagram, Component DiagramDaily Plan, Time Estimates, Review NotesArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
ArchitectureCommunicationVisualization
PlanningTime managementProductivityOperations
ArchitectureDocumentationCommunication
Add more methods