1. Clements
P.
Kazman
R.
& Klein
M. (2002). Evaluating Software Architectures: Methods and Case Studies. Addison-Wesley Professional. In Chapter 5
"The Outputs of an ATAM Evaluation
" the key outputs are listed as the utility tree
a set of scenarios
and the identified architectural risks
non-risks
sensitivity points
and tradeoffs (pp. 87-89).
2. Software Engineering Institute
Carnegie Mellon University. (2006). Architecture Tradeoff Analysis Method (ATAM). The ATAM process description explicitly lists the utility tree
scenarios
and risks as primary outputs created during the evaluation. Architecture documentation is listed as a required input.
3. International Software Architecture Qualification Board (ISAQB). (2023). Curriculum for Certified Professional for Software Architecture - Foundation Level (CPSA-F). Section 4.3.2
"Architecture Tradeoff Analysis Method (ATAM)
" describes the method's results
which include "documented risks and non-risks" and the use of a "utility tree" to document quality requirements in the form of scenarios.