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 Workshop5 WhysARID (Active Reviews for Intermediate Designs)Root Cause Analysis
| Criterion |  Architecture Quality Attribute Workshop |  Operations 5 Whys |  Architecture ARID (Active Reviews for Intermediate Designs) |  Operations Root Cause Analysis |
|---|---|---|---|---|
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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 2-4 h | 15-30 min | 2–4 h review as a planning range; preparation and evaluation additional | 1-4 h |
Participantsdifferent | 5-15 | 2-6 | Designers, developers as users, and facilitation | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Root cause notes, Countermeasures | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | RequirementsArchitectureWorkshop | Root causeIncidentLeanProblem solving | ArchitectureEngineeringFeedbackValidationTasks | Root causeProblem solvingQualityIncident |