View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Communication Plan |  Delivery RAID Log |  Architecture arc42 |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 30 min Setup, dann laufend | 1-2 Tage | 1-4 h |
Participantsdifferent | 2-6 | 1-3 maintaining, briefing for everyone | 1-4 | 1-5 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Communication Plan, Channel Matrix, Message Cadence | RAID Log, Status Report Source | Architecture Document, Context View, Runtime View, Deployment View | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | CommunicationStakeholdersDeliveryPlanning | RiskTrackingStakeholdersGovernance | ArchitectureDocumentationCommunication | ArchitectureCommunicationVisualization |