Architecture tradeoff analysis method: Difference between revisions

Revision as of 08:05, 22 February 2019

Revision as of 15:49, 5 August 2019

Line 17:

== Steps of the ATAM process ==

ATAM formally consists of nine steps, outlined below:<ref>{{cite book |title=Software Architecture in Practice, Second Edition, [[|first1=Len |last1=Bass]]; |author-link=Len Bass |first2=Paul |last2=Clements; |first3=Rick |last3=Kazman, |publisher=Addison Wesley Professional, |date=April 9, 2003}}{{Page needed|date=January 2013}}</ref> formally consists of nine steps, outlined below:

#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.

#Present the architecture – the architect presents the high -level architecture to the team, with an 'appropriate level of detail'

#Identify architectural approaches – different architectural approaches to the system are presented by the team, and discussed.

#Generate quality attribute utility tree – define the core business and technical requirements of the system, and map them to an appropriate architectural property. Present a scenario for this given requirement.