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 Failure Scenario Analysis |  Architecture C4 Model |  Delivery RAID Log |  Delivery Communication Plan |
|---|---|---|---|---|
Purposedifferent | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | 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. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 1-4 h | 30 min Setup, dann laufend | 45-90 min |
Participantsdifferent | 3-8 | 1-5 | 1-3 maintaining, briefing for everyone | 2-6 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Context Diagram, Container Diagram, Component Diagram | RAID Log, Status Report Source | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | FailureResilienceRisk | ArchitectureCommunicationVisualization | RiskTrackingStakeholdersGovernance | CommunicationStakeholdersDeliveryPlanning |