Software Engineering Institute | Carnegie Mellon University
Software Engineering Institute | Carnegie Mellon University

Digital Library

Javascript is currently disabled for your browser. For an optimal search experience, please enable javascript.

Advanced Search

Basic Search

Content Type

Topics

Publication Date

Technical Note

Software Architecture in DoD Acquisition: An Approach and Language for a Software Development Plan

  • February 2005
  • By John K. Bergey, Paul C. Clements
  • This report discusses the Software Development Plan (SDP), providing an example approach and corresponding SDP language that enable software architecture to play a central role in the technical and organizational management of a software development effort.
  • Acquisition Support Software Architecture
  • Publisher: Software Engineering Institute
    CMU/SEI Report Number: CMU/SEI-2005-TN-019
  • Abstract

    The right software architecture is essential for a software-intensive system. Meeting behavioral requirements and providing quality attributes such as real-time performance, reliability, and maintainability are essential architectural drivers. Because an architecture comprises the earliest, most important, and most far-reaching design decisions, making sure that the architecture will be fit for purpose is one of the most powerful, technical risk mitigation strategies available to a program office. This technical note covers one avenue of exercising architectural control—the Software Development Plan (SDP). The report provides an example approach and corresponding SDP language that enable software architecture to play a central role in the technical and organizational management of a software development effort. The example is drawn from an actual SDP written by a major U.S. Department of Defense contractor in a weapon-system procurement. The intent is to provide an example for other acquisition organizations to use (and adapt as appropriate) in their own procurements. While the example is based on a contracting approach with a lead system integrator, it can serve as a model for using an architecture-centric approach effectively to unify and manage software development across multiple suppliers, as found in the conventional prime-with-subcontractors acquisition context.

  • Download

Cite This Report

SEI

Bergey, John; & Clements, Paul. Software Architecture in DoD Acquisition: An Approach and Language for a Software Development Plan. CMU/SEI-2005-TN-019. Software Engineering Institute, Carnegie Mellon University. 2005. http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=7431

IEEE

Bergey. John, and Clements. Paul, "Software Architecture in DoD Acquisition: An Approach and Language for a Software Development Plan," Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pennsylvania, Technical Note CMU/SEI-2005-TN-019, 2005. http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=7431

APA

Bergey, John., & Clements, Paul. (2005). Software Architecture in DoD Acquisition: An Approach and Language for a Software Development Plan (CMU/SEI-2005-TN-019). Retrieved December 11, 2016, from the Software Engineering Institute, Carnegie Mellon University website: http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=7431

CHI

John Bergey, & Paul Clements. Software Architecture in DoD Acquisition: An Approach and Language for a Software Development Plan (CMU/SEI-2005-TN-019). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2005. http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=7431

MLA

Bergey, John., & Clements, Paul. 2005. Software Architecture in DoD Acquisition: An Approach and Language for a Software Development Plan (Technical Report CMU/SEI-2005-TN-019). Pittsburgh: Software Engineering Institute, Carnegie Mellon University. http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=7431

BibTex

@techreport{BergeySoftwareArchitecture2005,
title={Software Architecture in DoD Acquisition: An Approach and Language for a Software Development Plan},
author={John Bergey and Paul Clements},
year={2005},
number={CMU/SEI-2005-TN-019},
institution={Software Engineering Institute, Carnegie Mellon University},
address={Pittsburgh, PA},
url={http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=7431} }