Content deleted Content added
rv, someone inserted 'not' at a critical point |
|||
Line 18:
== ATAM Process ==
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 ==
1.) Present ATAM - Present the concept of ATAM to the stakeholders, and answer an questions about the process.
2.) Present Business Drivers - Everyone in the process presents and evaluates the business drivers for the system in question.
3.) Present the Architecture - The archiect presents the high level architecture to the team, with an 'appropriate level of detail'
4.) Identify Architectural Approaches - Different architecural approaches to the system are presented by the team, and discussed.
5.) 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.
6.) Analyze architectural approaches - Analyze each scenario, rating them by priority. The architecure is then evaluated against each scenario.
7.) Brainstorm and prioritize scenarios - among the larger stakeholder group, present the current scenarios, and expand.
8.) Analyze architectural approaches - Perform step 6 again with the added knowledge of the larger stakeholder community.
9.) Present results - provide all documentation to the stakeholders.
<ref>Software Architecture in Practice, Second Edition, Len Bass; Paul Clements; Rick Kazman, Addison Wesley Professional, April 09, 2003</ref>
==External links==
| |||