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 RAID Log |  Architecture C4 Model |  Agile ROAM Board |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30 min Setup, dann laufend | 1-4 h | 20-40 min initial, dann laufend | 1-2 Tage |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-5 | 3-15 | 1-4 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Context Diagram, Container Diagram, Component Diagram | ROAM Board, Owner List | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationVisualization | RiskAgileTrackingAlignment | ArchitectureDocumentationCommunication |