This report emerged from a series of technical reports, each of which analyzed a single architectural quality attribute. In this report, we take a step back from the details of any specific quality attribute and instead focus on how architectural decisions and architectural analysis spanning multiple quality attributes can be performed in a sustainable and ongoing way. This approach requires taking a holistic view of architectural activities that does not focus on a single quality attribute and that does not end when code is written or released. It is then possible to reason about the synergies and tradeoffs among quality attributes. Synergies present an architect with unparalleled opportunities, where the choice of a single mechanism might result in benefits for multiple quality attribute concerns. In this process, architects and analysts must pay attention to the positive and negative effects of decisions since they may result in unacceptable tradeoffs that undermine system quality. This report emphasizes the importance of ongoing governance, analysis, and evaluation. To make this approach practical, it must be automated (to the extent possible), otherwise the analysis will not be done or will not be done often enough. The report concludes with a six-step meta-playbook, a process you can use for creating your own analysis process.
Publisher Statement
This material is based upon work funded and supported by the Department of Defense under Contract No. FA8702-15-D-0002 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. The view, opinions, and/or findings contained in this material are those of the author(s) and should not be construed as an official Government position, policy, or decision, unless designated by other documentation. References herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by Carnegie Mellon University or its Software Engineering Institute.
This report was prepared for the SEI Administrative Agent AFLCMC/AZS 5 Eglin Street Hanscom AFB, MA 01731-2100.
NO WARRANTY. THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN "AS-IS" BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT.
[DISTRIBUTION STATEMENT A] This material has been approved for public release and unlimited distribution. Please see Copyright notice for non-US Government use and distribution.Copyright Statement
Copyright 2023 Carnegie Mellon University.