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 |  Delivery Shape Up |  Architecture arc42 |  Architecture Views and Beyond |
|---|---|---|---|---|
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. | Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts. | 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 | Low | Medium | Low | Medium |
Timedifferent | 1-4 h | 6 Wochen Cycle + 2 Wochen Cool-Down | 1-2 Tage | 1-3 Tage |
Participantsdifferent | 1-5 | 2-4 pro Pitch | 1-4 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Architecture Document, Context View, Runtime View, Deployment View | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | ArchitectureCommunicationVisualization | PlanningDeliveryAutonomy | ArchitectureDocumentationCommunication | DocumentationStakeholdersArchitecture |