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
Paper illustration for PERT Estimation.
Decision Making
PERT Estimation
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
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.On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes.When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets.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 Tage15-45 min5-20 min1-4 h
Participantsdifferent
1-41-83-201-5
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewPERT Estimate, Expected Value, Risk NotesEffort Heatmap, Risk Signals, Discussion TargetsContext Diagram, Container Diagram, Component Diagram
Tagsno overlap
ArchitectureDocumentationCommunication
EstimationUncertaintyRisk
EstimationEffortRisk
ArchitectureCommunicationVisualization
Add more methods