Assuring Software Reliability
• SEI Report
Publisher
Software Engineering Institute
CMU/SEI Report Number
CMU/SEI-2014-SR-008DOI (Digital Object Identifier)
10.1184/R1/6572060.v1Topic or Tag
Abstract
The 2005 Department of Defense Guide for Achieving Reliability, Availability, and Maintainability (RAM) recommended an emphasis on engineering analysis with formal design reviews with less reliance on RAM predictions. A number of studies have shown the limitations of current system development practices for meeting these recommendations. This document describes ways that the analysis of the potential impact of software failures (regardless of cause) can be incorporated into development and acquisition practices through the use of software assurance.
Cite This SEI Report
Ellison, R. (2014, August 15). Assuring Software Reliability. (SEI Report CMU/SEI-2014-SR-008). Retrieved August 8, 2026, from https://doi.org/10.1184/R1/6572060.v1.
@techreport{ellison_2014,
author={Ellison, Robert},
title={Assuring Software Reliability},
month={Aug},
year={2014},
number={{CMU/SEI-2014-SR-008},
institution={Software Engineering Institute, Carnegie Mellon University},
doi={10.1184/R1/6572060.v1},
url={https://doi.org/10.1184/R1/6572060.v1},
note={Accessed: 2026-Aug-8}
}
Ellison, Robert. "Assuring Software Reliability." (CMU/SEI-2014-SR-008). Software Engineering Institute, Carnegie Mellon University. Software Engineering Institute, August 15, 2014. https://doi.org/10.1184/R1/6572060.v1.
R. Ellison, "Assuring Software Reliability," Software Engineering Institute, Carnegie Mellon University. Software Engineering Institute, SEI Report CMU/SEI-2014-SR-008, 15-Aug-2014 [Online]. Available: https://doi.org/10.1184/R1/6572060.v1. [Accessed: 8-Aug-2026].
Ellison, Robert. "Assuring Software Reliability." (SEI Report CMU/SEI-2014-SR-008). Software Engineering Institute, Carnegie Mellon University, Software Engineering Institute, 15 Aug. 2014. https://doi.org/10.1184/R1/6572060.v1. Accessed 8 Aug. 2026.
Ellison, Robert. Assuring Software Reliability. CMU/SEI-2014-SR-008. Software Engineering Institute. 2014. DOI: 10.1184/R1/6572060.v1. https://doi.org/10.1184/R1/6572060.v1