View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ARID (Active Reviews for Intermediate Designs)Scatter DiagramRoot Cause AnalysisATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Operations Scatter Diagram |  Operations Root Cause Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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. | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 30-90 min | 1-4 h | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | Designers, developers as users, and facilitation | 1-4 | 3-8 | Evaluation team, architects, and relevant stakeholders |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | Root causeQualityVisualization | Root causeProblem solvingQualityIncident | ArchitectureQualityRiskTradeoffsStakeholders |