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 |  Architecture arc42 |  Agile Specification by Example |  Architecture Views and Beyond |
|---|---|---|---|---|
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. | 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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 45-90 min | 1-2 Tage | 60-90 min pro Feature | 1-3 Tage |
Participantsdifferent | 2-6 | 1-4 | 3-6 | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Communication Plan, Channel Matrix, Message Cadence | Architecture Document, Context View, Runtime View, Deployment View | Example Table, Acceptance Tests | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | CommunicationStakeholdersDeliveryPlanning | ArchitectureDocumentationCommunication | AgileRequirementsExamplesBehavior-Driven Development | DocumentationStakeholdersArchitecture |