Accession Number:



Reducing Risk in DoD Software-Intensive Systems Development

Descriptive Note:

Technical Report

Corporate Author:

Naval Postgraduate School Monterey United States

Personal Author(s):

Report Date:


Pagination or Media Count:



The Department of Defense DoD continues to experience both successful and unsuccessful software-intensive systems development, despite all of the considerable qualifications of the workforce and the significant controls offered by the Defense Acquisition System DAS. The unsuccessful software-intensive systems have suffered dramatic cost and schedule overruns, impacting modernization timetables and reducing funding for other developmental priorities. This research is a continuation and consolidation of previous research projects conducted for the U.S. Navy Open Architecture Task Force. That previous research is identified and cited where appropriate. The purpose of this research is to analyze why DoD risk management processes have not been more effective in reducing software-intensive systems development risk. This research addresses the use of the Technical Readiness Assessment TRA using the nine-level software Technology Readiness Levels TRLs, use of the software developer maturity level assessments using the Software Engineering Institutes SEIs Capability Maturity Model-Integrated for Development CMMI-DEV, and use of the software acquirer maturity level assessments using SEIs CMMI for Acquisition CMMI-ACQ. The recommendations include the use of effective tools, techniques, and analyses presented in the authors previous research efforts. The previously researched tools, techniques, and analyses include the SEIs Quality Attribution Workshop QAW, the MUIRS maintainability, upgradability, interoperability, reliability, and safetysecurity analysis methodology, SEIs Architectural Tradeoff Analysis Methodologysm ATAMsm, Logistics Supportability Analysis LSA, and the Failure Modes and Effects Criticality Analysis FMECA.The major research findings include the following The software TRLs are ineffective in reducing technical risk for the software component development.

Subject Categories:

Distribution Statement: