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 arc42 |  Delivery Communication Plan |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 1-2 Tage | 45-90 min | 60-120 min |
Participantsdifferent | 3-8 | 1-4 | 2-6 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Architecture Document, Context View, Runtime View, Deployment View | Communication Plan, Channel Matrix, Message Cadence | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | FailureResilienceRisk | ArchitectureDocumentationCommunication | CommunicationStakeholdersDeliveryPlanning | ArchitectureCommunicationStakeholdersCanvas |