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 C4 Model |  UX Research Affinity Diagramming |  Architecture Quality Attribute Workshop |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | 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 research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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. | 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 | Low | Low | Medium | Low |
Timedifferent | 1-4 h | 45–90 min | 2-4 h | 60-90 min |
Participantsdifferent | 1-5 | 3-10 | 5-15 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Theme clusters, Insight statements, Opportunity areas | Quality Scenarios, Priority List, Architecture Concerns | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureCommunicationVisualization | SynthesisQualitativeRoot cause | RequirementsArchitectureWorkshop | RiskArchitectureWorkshopValidation |