icon-carat-right menu search cmu-wordmark

Robustness Testing of Software-Intensive Systems: Explanation and Guide

Technical Note
This 2005 technical note provides guidance and procedures for performing robustness testing as part of DoD or federal acquisition programs that have a software component.
Publisher

Software Engineering Institute

CMU/SEI Report Number
CMU/SEI-2005-TN-015
DOI (Digital Object Identifier)
10.1184/R1/6583508.v1
Topic or Tag

Abstract

Many Department of Defense (DoD) programs engage in what has been called "happy-path testing" (that is, testing that is only meant to show that the system meets its functional requirements). While testing to ensure that requirements are met is necessary, often tests aimed at ensuring that the system handles errors and failures appropriately are neglected. Robustness has been defined by the Food and Drug Administration as "the degree to which a software system or component can function correctly in the presence of invalid inputs or stressful environmental conditions." This technical note provides guidance and procedures for performing robustness testing as part of DoD or federal acquisition programs that have a software component. It includes background on the need for robustness testing and describes how robustness testing fits into DoD acquisition, including source selection issues, development issues, and developmental and operational testing issues.

Cite This Technical Note

Cohen, J., Plakosh, D., & Keeler, K. (2005, April 1). Robustness Testing of Software-Intensive Systems: Explanation and Guide. (Technical Note CMU/SEI-2005-TN-015). Retrieved December 2, 2024, from https://doi.org/10.1184/R1/6583508.v1.

@techreport{cohen_2005,
author={Cohen, Julie and Plakosh, Daniel and Keeler, Kristi},
title={Robustness Testing of Software-Intensive Systems: Explanation and Guide},
month={{Apr},
year={{2005},
number={{CMU/SEI-2005-TN-015},
howpublished={Carnegie Mellon University, Software Engineering Institute's Digital Library},
url={https://doi.org/10.1184/R1/6583508.v1},
note={Accessed: 2024-Dec-2}
}

Cohen, Julie, Daniel Plakosh, and Kristi Keeler. "Robustness Testing of Software-Intensive Systems: Explanation and Guide." (CMU/SEI-2005-TN-015). Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, April 1, 2005. https://doi.org/10.1184/R1/6583508.v1.

J. Cohen, D. Plakosh, and K. Keeler, "Robustness Testing of Software-Intensive Systems: Explanation and Guide," Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, Technical Note CMU/SEI-2005-TN-015, 1-Apr-2005 [Online]. Available: https://doi.org/10.1184/R1/6583508.v1. [Accessed: 2-Dec-2024].

Cohen, Julie, Daniel Plakosh, and Kristi Keeler. "Robustness Testing of Software-Intensive Systems: Explanation and Guide." (Technical Note CMU/SEI-2005-TN-015). Carnegie Mellon University, Software Engineering Institute's Digital Library, Software Engineering Institute, 1 Apr. 2005. https://doi.org/10.1184/R1/6583508.v1. Accessed 2 Dec. 2024.

Cohen, Julie; Plakosh, Daniel; & Keeler, Kristi. Robustness Testing of Software-Intensive Systems: Explanation and Guide. CMU/SEI-2005-TN-015. Software Engineering Institute. 2005. https://doi.org/10.1184/R1/6583508.v1