search menu icon-carat-right cmu-wordmark

Categorizing Business Goals for Software Architectures

Technical Report
This report provides a categorization of possible business goals for software-intensive systems, so that individuals have some guidance in the elicitation, expression, and documentation of business goals.
Publisher

Software Engineering Institute

CMU/SEI Report Number
CMU/SEI-2005-TR-021
DOI (Digital Object Identifier)
10.1184/R1/6572174.v1

Abstract

Business goals are the foundation on which software systems are justified, analyzed, and built. Software systems are constructed to realize business or mission goals. Software architecture is the bridge between the business goals and the realized system. Those claims about business goals underlie many methods for designing and analyzing software architectures. However, precisely eliciting and characterizing business goals has always been problematic. Business goals come in many forms and at many levels of abstraction, and the stakeholders of the system are usually not accustomed to making goals explicit.

This report provides a categorization of possible business goals, so that stakeholders can have guidance in the goals' creation, expression, and documentation. The categorization was derived by mining a set of 190 distinct business goals elicited in 25 Architecture Tradeoff Analysis Method (ATAM) evaluations and then by performing an affinity diagram process to group the business goals into categories. For each goal, example scenarios are provided to illustrate how the goal might impact a system. Finally, this report shows how the architecture business cycle (ABC) may be extended by the business goal categorization.

Cite This Technical Report

Kazman, R., & Bass, L. (2005, December 1). Categorizing Business Goals for Software Architectures. (Technical Report CMU/SEI-2005-TR-021). Retrieved July 20, 2024, from https://doi.org/10.1184/R1/6572174.v1.

@techreport{kazman_2005,
author={Kazman, Rick and Bass, Len},
title={Categorizing Business Goals for Software Architectures},
month={Dec},
year={2005},
number={CMU/SEI-2005-TR-021},
howpublished={Carnegie Mellon University, Software Engineering Institute's Digital Library},
url={https://doi.org/10.1184/R1/6572174.v1},
note={Accessed: 2024-Jul-20}
}

Kazman, Rick, and Len Bass. "Categorizing Business Goals for Software Architectures." (CMU/SEI-2005-TR-021). Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, December 1, 2005. https://doi.org/10.1184/R1/6572174.v1.

R. Kazman, and L. Bass, "Categorizing Business Goals for Software Architectures," Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, Technical Report CMU/SEI-2005-TR-021, 1-Dec-2005 [Online]. Available: https://doi.org/10.1184/R1/6572174.v1. [Accessed: 20-Jul-2024].

Kazman, Rick, and Len Bass. "Categorizing Business Goals for Software Architectures." (Technical Report CMU/SEI-2005-TR-021). Carnegie Mellon University, Software Engineering Institute's Digital Library, Software Engineering Institute, 1 Dec. 2005. https://doi.org/10.1184/R1/6572174.v1. Accessed 20 Jul. 2024.

Kazman, Rick; & Bass, Len. Categorizing Business Goals for Software Architectures. CMU/SEI-2005-TR-021. Software Engineering Institute. 2005. https://doi.org/10.1184/R1/6572174.v1