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 ARID (Active Reviews for Intermediate Designs) |  Delivery RAID Log |  Architecture arc42 |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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. | 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. | 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 review as a planning range; preparation and evaluation additional | 30 min Setup, dann laufend | 1-2 Tage | 60-90 min |
Participantsdifferent | Designers, developers as users, and facilitation | 1-3 maintaining, briefing for everyone | 1-4 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | RAID Log, Status Report Source | Architecture Document, Context View, Runtime View, Deployment View | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | RiskTrackingStakeholdersGovernance | ArchitectureDocumentationCommunication | RiskArchitectureWorkshopValidation |