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 Report

An Alternative to Technology Readiness Levels for Non-Developmental Item (NDI) Software

  • April 2004
  • By James Smith
  • This report explores the difficulties in using TRLs as they apply to NDI software technology and products, and explores an alternative set of readiness criteria.
  • System of Systems
  • Publisher: Software Engineering Institute
    CMU/SEI Report Number: CMU/SEI-2004-TR-013
  • 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:

    1. TRLs "blur" several aspects of technology and product readiness into a single number.
    2. TRLs do not account for the criticality of a product or technology to the system as a whole.
    3. TRLs don't account for software technology and product aging.
    4. 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.

  • Download

Cite This Report

SEI

Smith, James. An Alternative to Technology Readiness Levels for Non-Developmental Item (NDI) Software. CMU/SEI-2004-TR-013. Software Engineering Institute, Carnegie Mellon University. 2004. http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=7143

IEEE

Smith. James, "An Alternative to Technology Readiness Levels for Non-Developmental Item (NDI) Software," Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pennsylvania, Technical Report CMU/SEI-2004-TR-013, 2004. http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=7143

APA

Smith, James. (2004). An Alternative to Technology Readiness Levels for Non-Developmental Item (NDI) Software (CMU/SEI-2004-TR-013). Retrieved December 09, 2016, from the Software Engineering Institute, Carnegie Mellon University website: http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=7143

CHI

James Smith. An Alternative to Technology Readiness Levels for Non-Developmental Item (NDI) Software (CMU/SEI-2004-TR-013). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2004. http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=7143

MLA

Smith, James. 2004. An Alternative to Technology Readiness Levels for Non-Developmental Item (NDI) Software (Technical Report CMU/SEI-2004-TR-013). Pittsburgh: Software Engineering Institute, Carnegie Mellon University. http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=7143

BibTex

@techreport{SmithAnAlternative2004,
title={An Alternative to Technology Readiness Levels for Non-Developmental Item (NDI) Software},
author={James Smith},
year={2004},
number={CMU/SEI-2004-TR-013},
institution={Software Engineering Institute, Carnegie Mellon University},
address={Pittsburgh, PA},
url={http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=7143} }