Revision as of 15:50, 14 January 2013 edit Mikeblas (talk \| contribs) Administrators 82,114 edits use cite ref ← Previous edit		Revision as of 15:51, 14 January 2013 edit undo Mikeblas (talk \| contribs) Administrators 82,114 edits m →Steps of the ATAM processSoftware Architecture in Practice, Second Edition, Len Bass; Paul Clements; Rick Kazman, Addison Wesley Professional, April 9, 2003 Next edit →
Line 16: The ATAM process consists of gathering stakeholders together to analyze business drivers and from these drivers extract quality attributes that are used to create scenarios. These scenarios are then used in conjunction with architectural approaches and architectural decisions to create an analysis of trade-offs, sensitivity points, and risks (or non-risks). This analysis can be converted to risk themes and their impacts whereupon the process can be repeated. == Steps of the ATAM process<ref>Software Architecture in Practice, Second Edition, Len Bass; Paul Clements; Rick Kazman, Addison Wesley Professional, April 9, 2003{{Page needed}}</ref> == #Present ATAM – Present the concept of ATAM to the stakeholders, and answer any questions about the process. #Present business drivers – everyone in the process presents and evaluates the business drivers for the system in question.

Architecture tradeoff analysis method: Difference between revisions