Architecture tradeoff analysis method: Difference between revisions

Revision as of 09:00, 11 November 2011

Revision as of 09:01, 11 November 2011

Line 1:

In [[software engineering]], '''Architecturearchitecture Tradeofftradeoff Analysisanalysis Methodmethod''' (ATAM) is a risk-mitigation process used early in the [[software development life cycle]].

ATAM was developed by the [[Software Engineering Institute]] at the [[Carnegie Mellon University]]. Its purpose is to help choose a suitable architecture for a software system by discovering [[trade-off]]s and sensitivity points.

Line 5:

ATAM is most beneficial when done early in the software development life-cycle, when the cost of changing architectures is minimal.

== ATAM Benefitsbenefits ==

The following are some of the benefits of the ATAM process {{Citation needed|date=May 2010}}:

* Promotes the gathering of precise quality requirements

Line 13:

* Encourages increased communication among stakeholders

== ATAM Processprocess ==

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 Processprocess<ref>Software Architecture in Practice, Second Edition, Len Bass; Paul Clements; Rick Kazman, Addison Wesley Professional, April 9, 2003</ref> ==

#Present ATAM -– Present the concept of ATAM to the stakeholders, and answer any questions about the process.

#Present Businessbusiness Driversdrivers -– Everyoneeveryone in the process presents and evaluates the business drivers for the system in question.

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

#Identify Architecturalarchitectural Approachesapproaches -– Differentdifferent architectural approaches to the system are presented by the team, and discussed.

#Generate Qualityquality Attributeattribute Utilityutility Treetree -– Definedefine the core business and technical requirements of the system, and map them to an appropriate architectural property. Present a scenario for this given requirement.

#Analyze architectural approaches -– Analyze each scenario, rating them by priority. The architecture is then evaluated against each scenario.

#Brainstorm and prioritize scenarios -– among the larger stakeholder group, present the current scenarios, and expand.

#Analyze architectural approaches -– Perform step 6 again with the added knowledge of the larger stakeholder community.

#Present results -– provide all documentation to the stakeholders.

== See Alsoalso ==

[[ilities]]