View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture C4 Model |  Architecture arc42 |  Agile Ideal Days |  Agile Planning Poker |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 1-4 h | 1-2 Tage | 15-60 min | 2-5 min je Item |
Participantsdifferent | 1-5 | 1-4 | 2-9 | 3-9 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Architecture Document, Context View, Runtime View, Deployment View | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | ArchitectureCommunicationVisualization | ArchitectureDocumentationCommunication | EstimationEffortAgile | EstimationAgileRelative sizingTeam |