View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Quality Attribute Workshop |  Delivery Communication Plan |  Architecture C4 Model |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | 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 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 architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 2-4 h | 45-90 min | 1-4 h | 60-90 min |
Participantsdifferent | 5-15 | 2-6 | 1-5 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Communication Plan, Channel Matrix, Message Cadence | Context Diagram, Container Diagram, Component Diagram | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | RequirementsArchitectureWorkshop | CommunicationStakeholdersDeliveryPlanning | ArchitectureCommunicationVisualization | RiskArchitectureWorkshopValidation |