Risk Themes Discovered Through Architecture Evaluations
September 2006 • Technical Report
Len Bass, Robert Nord, William G. Wood, David Zubrow
This 2006 report analyzes the output of 18 evaluations conducted using the Architecture Tradeoff Analysis (ATAM). The goal of the analysis was to find patterns in the risk themes identified during those evaluations.
Software Engineering Institute
CMU/SEI Report Number
DOI (Digital Object Identifier):10.1184/R1/6583481.v1
This technical report analyzes the output of 18 evaluations conducted using the Architecture Tradeoff Analysis Method (ATAM) developed by the Carnegie Mellon Software Engineering Institute. The goal of this analysis was to find patterns in the risk themes identified during those evaluations. The major results are
- a categorization of risk themes
- the observation that twice as many risk themes are risks of "omission" as are risks of "commission"
- a failure to find a relationship between the business/mission goals of a system and the risk themes revealed during an ATAM evaluation of that system
- a failure to find a relationship between the domain of a system being evaluated and the risk themes associated with the development of that system