View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Architecture arc42 |  Architecture Views and Beyond |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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. | 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 | Medium | Low | Medium | Low |
Timedifferent | Ongoing | 1-2 Tage | 1-3 Tage | 1-4 h |
Participantsdifferent | 2-12 | 1-4 | 1-4 | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Architecture Document, Context View, Runtime View, Deployment View | Architecture Views, Cross-view Notes, Rationale | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | FlowVisual managementDelivery | ArchitectureDocumentationCommunication | DocumentationStakeholdersArchitecture | ArchitectureCommunicationVisualization |