An Alternative to Technology Readiness Levels for Non-Developmental Item (NDI) Software
• Technical Report
Publisher
Software Engineering Institute
CMU/SEI Report Number
CMU/SEI-2004-TR-013DOI (Digital Object Identifier)
10.1184/R1/6571889.v1Topic or Tag
Abstract
Defense acquisition policies require that program managers conduct technology readiness assessments for all critical technologies. Technology Readiness Levels (TRLs) are frequently used in performing these assessments. While there is considerable evidence to support the utility of using TRLs in assessing program risk, there are some difficulties in using TRLs with software. This report explores these problems as they apply to non-developmental item (NDI) software technology and products, including commercial off-the-shelf, government off-the-shelf, and open source software. The problems take four principal forms:
- TRLs "blur" several aspects of technology and product readiness into a single number.
- TRLs do not account for the criticality of a product or technology to the system as a whole.
- TRLs don't account for software technology and product aging.
- TRLs do not provide any means to deal with how the relative contributions of the various aspects of readiness vary throughout the life cycle of a system.
This report examines these issues in detail and proposes an alternative approach for determining product readiness of NDI software technology.
Cite This Technical Report
Smith, J. (2004, April 1). An Alternative to Technology Readiness Levels for Non-Developmental Item (NDI) Software. (Technical Report CMU/SEI-2004-TR-013). Retrieved December 22, 2024, from https://doi.org/10.1184/R1/6571889.v1.
@techreport{smith_2004,
author={Smith, James},
title={An Alternative to Technology Readiness Levels for Non-Developmental Item (NDI) Software},
month={{Apr},
year={{2004},
number={{CMU/SEI-2004-TR-013},
howpublished={Carnegie Mellon University, Software Engineering Institute's Digital Library},
url={https://doi.org/10.1184/R1/6571889.v1},
note={Accessed: 2024-Dec-22}
}
Smith, James. "An Alternative to Technology Readiness Levels for Non-Developmental Item (NDI) Software." (CMU/SEI-2004-TR-013). Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, April 1, 2004. https://doi.org/10.1184/R1/6571889.v1.
J. Smith, "An Alternative to Technology Readiness Levels for Non-Developmental Item (NDI) Software," Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, Technical Report CMU/SEI-2004-TR-013, 1-Apr-2004 [Online]. Available: https://doi.org/10.1184/R1/6571889.v1. [Accessed: 22-Dec-2024].
Smith, James. "An Alternative to Technology Readiness Levels for Non-Developmental Item (NDI) Software." (Technical Report CMU/SEI-2004-TR-013). Carnegie Mellon University, Software Engineering Institute's Digital Library, Software Engineering Institute, 1 Apr. 2004. https://doi.org/10.1184/R1/6571889.v1. Accessed 22 Dec. 2024.
Smith, James. An Alternative to Technology Readiness Levels for Non-Developmental Item (NDI) Software. CMU/SEI-2004-TR-013. Software Engineering Institute. 2004. https://doi.org/10.1184/R1/6571889.v1