search menu icon-carat-right cmu-wordmark

Software Architecture in DoD Acquisition: A Reference Standard for a Software Architecture Document

Technical Note
This report provides a reference standard for a Software Architecture Document (SAD). Acquisition organizations can use this to acquire documentation needed for communicating the architecture design and conducting software architecture evaluations.
Publisher

Software Engineering Institute

CMU/SEI Report Number
CMU/SEI-2005-TN-020
DOI (Digital Object Identifier)
10.1184/R1/6583952.v1

Abstract

The right software architecture is essential for a software-intensive system to meet its functional requirements as well as its quality requirements that govern real-time performance, reliability, maintainability, and a host of other quality attributes. Because an architecture comprises the earliest, most important, and most far-reaching design decisions, it is important for an acquisition organization to exercise its oversight prerogatives with respect to software architecture. Having the right software architecture documentation is a prerequisite for managing and guiding a software development effort and conducting in situ software architecture evaluations. Conducting an architecture evaluation to determine the software architecture's fitness for purpose is one of the most powerful, technical risk mitigation strategies available to a program office. 

This report provides an example reference standard for a Software Architecture Document (SAD). An acquisition organization can use this standard to contractually acquire the documentation needed for communicating the software architecture design and conducting software architecture evaluations. The example used in this report is drawn from an actual SAD written by a major U.S. Department of Defense contractor in a weapon system acquisition. The intent of this report is to provide an example for other acquisition efforts to use (and adapt as appropriate) in their own procurements.

Cite This Technical Note

Bergey, J., & Clements, P. (2005, February 1). Software Architecture in DoD Acquisition: A Reference Standard for a Software Architecture Document. (Technical Note CMU/SEI-2005-TN-020). Retrieved February 27, 2024, from https://doi.org/10.1184/R1/6583952.v1.

@techreport{bergey_2005,
author={Bergey, John and Clements, Paul},
title={Software Architecture in DoD Acquisition: A Reference Standard for a Software Architecture Document},
month={Feb},
year={2005},
number={CMU/SEI-2005-TN-020},
howpublished={Carnegie Mellon University, Software Engineering Institute's Digital Library},
url={https://doi.org/10.1184/R1/6583952.v1},
note={Accessed: 2024-Feb-27}
}

Bergey, John, and Paul Clements. "Software Architecture in DoD Acquisition: A Reference Standard for a Software Architecture Document." (CMU/SEI-2005-TN-020). Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, February 1, 2005. https://doi.org/10.1184/R1/6583952.v1.

J. Bergey, and P. Clements, "Software Architecture in DoD Acquisition: A Reference Standard for a Software Architecture Document," Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, Technical Note CMU/SEI-2005-TN-020, 1-Feb-2005 [Online]. Available: https://doi.org/10.1184/R1/6583952.v1. [Accessed: 27-Feb-2024].

Bergey, John, and Paul Clements. "Software Architecture in DoD Acquisition: A Reference Standard for a Software Architecture Document." (Technical Note CMU/SEI-2005-TN-020). Carnegie Mellon University, Software Engineering Institute's Digital Library, Software Engineering Institute, 1 Feb. 2005. https://doi.org/10.1184/R1/6583952.v1. Accessed 27 Feb. 2024.

Bergey, John; & Clements, Paul. Software Architecture in DoD Acquisition: A Reference Standard for a Software Architecture Document. CMU/SEI-2005-TN-020. Software Engineering Institute. 2005. https://doi.org/10.1184/R1/6583952.v1