search menu icon-carat-right cmu-wordmark

Using the Architecture Tradeoff Analysis Method (ATAM) to Evaluate the Software Architecture for a Product Line of Avionics Systems: A Case Study

Technical Note
This 2003 technical note describes an ATAM evaluation of the software architecture for an avionics system developed for the Technology Applications Program Office (TAPO) of the U.S. Army Special Operations Command Office.
Publisher

Software Engineering Institute

CMU/SEI Report Number
CMU/SEI-2003-TN-012
DOI (Digital Object Identifier)
10.1184/R1/6585797.v1

Abstract

The quality of a software-intensive system depends heavily on the system's software architecture. When used appropriately, software architecture evaluations can have a favorable effect on a delivered or modified government system. This technical note describes the application of the Architecture Tradeoff Analysis Method (ATAM) to an Army avionics system acquisition. A government-contractor team is developing the Common Avionics Architecture System (CAAS) for a family of U.S. Army Special Operations helicopters. This technical note presents the contextual background about the software architecture, the organization, and the system being evaluated. It also provides a general overview of the ATAM process, describes the application of the ATAM to the CAAS, and presents important results and benefits.

Cite This Technical Note

Barbacci, M., Clements, P., Lattanze, A., Northrop, L., & Wood, W. (2003, July 1). Using the Architecture Tradeoff Analysis Method (ATAM) to Evaluate the Software Architecture for a Product Line of Avionics Systems: A Case Study. (Technical Note CMU/SEI-2003-TN-012). Retrieved July 24, 2024, from https://doi.org/10.1184/R1/6585797.v1.

@techreport{barbacci_2003,
author={Barbacci, Mario and Clements, Paul and Lattanze, Anthony and Northrop, Linda and Wood, William},
title={Using the Architecture Tradeoff Analysis Method (ATAM) to Evaluate the Software Architecture for a Product Line of Avionics Systems: A Case Study},
month={Jul},
year={2003},
number={CMU/SEI-2003-TN-012},
howpublished={Carnegie Mellon University, Software Engineering Institute's Digital Library},
url={https://doi.org/10.1184/R1/6585797.v1},
note={Accessed: 2024-Jul-24}
}

Barbacci, Mario, Paul Clements, Anthony Lattanze, Linda Northrop, and William Wood. "Using the Architecture Tradeoff Analysis Method (ATAM) to Evaluate the Software Architecture for a Product Line of Avionics Systems: A Case Study." (CMU/SEI-2003-TN-012). Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, July 1, 2003. https://doi.org/10.1184/R1/6585797.v1.

M. Barbacci, P. Clements, A. Lattanze, L. Northrop, and W. Wood, "Using the Architecture Tradeoff Analysis Method (ATAM) to Evaluate the Software Architecture for a Product Line of Avionics Systems: A Case Study," Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, Technical Note CMU/SEI-2003-TN-012, 1-Jul-2003 [Online]. Available: https://doi.org/10.1184/R1/6585797.v1. [Accessed: 24-Jul-2024].

Barbacci, Mario, Paul Clements, Anthony Lattanze, Linda Northrop, and William Wood. "Using the Architecture Tradeoff Analysis Method (ATAM) to Evaluate the Software Architecture for a Product Line of Avionics Systems: A Case Study." (Technical Note CMU/SEI-2003-TN-012). Carnegie Mellon University, Software Engineering Institute's Digital Library, Software Engineering Institute, 1 Jul. 2003. https://doi.org/10.1184/R1/6585797.v1. Accessed 24 Jul. 2024.

Barbacci, Mario; Clements, Paul; Lattanze, Anthony; Northrop, Linda; & Wood, William. Using the Architecture Tradeoff Analysis Method (ATAM) to Evaluate the Software Architecture for a Product Line of Avionics Systems: A Case Study. CMU/SEI-2003-TN-012. Software Engineering Institute. 2003. https://doi.org/10.1184/R1/6585797.v1