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) |  Agile Specification by Example |  Delivery RAID Log |
|---|---|---|---|
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. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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. |
Complexitydifferent | High | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 60-90 min pro Feature | 30 min Setup, dann laufend |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-6 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop | 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 | Example Table, Acceptance Tests | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | AgileRequirementsExamplesBehavior-Driven Development | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
