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 ATAM (Architecture Tradeoff Analysis Method) |  Delivery RAID Log |  UX Research Diary Study |
|---|---|---|---|
Purposedifferent | 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. | 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. | When experiences build up over days or weeks and a single session cannot capture them, Diary Study records the course of everyday life. Recurring triggers, moods, and habits become visible this way, beyond the sharpness of memory. |
Complexitydifferent | High | Low | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30 min Setup, dann laufend | 1-4 Wochen |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1-3 maintaining, briefing for everyone | 5-20 |
Formatdifferent | Workshop + async | Async | Async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | RAID Log, Status Report Source | Diary Entries, Longitudinal Patterns, Experience Timeline |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | RiskTrackingStakeholdersGovernance | UX researchTrackingBehavior |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
