View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Quality Attribute WorkshopRequest for CommentsARID (Active Reviews for Intermediate Designs)
| Criterion |  Architecture Quality Attribute Workshop |  Architecture Request for Comments |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|
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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 2-4 h | 1-3 Wochen vom Draft bis zur Entscheidung | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 5-15 | 3-20 Reviewer | Designers, developers as users, and facilitation |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tags1 shared | RequirementsArchitectureWorkshop | ArchitectureDecisionAsyncGovernance | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
