When good requirements turn bad

The root cause of the difference between predicted reliability during DoD system development and achieved reliability in OT&E is “bad” reliability requirements being placed on contract, or misinterpreted/misapplied during development. This paper has identified the need for a more accurate and comprehensive approach to developing contractual reliability requirements that meet the end-users´ operational reliability needs. A hypothetical example was provided that showed how good requirements can turn bad, and their general impact on reliability growth curve planning and reliability testing. A formal standard process was recommended that can be used to develop and allocate contractual reliability requirements that are based on all of the failure categories that ultimately impact whether a system will comply with its operational reliability requirements. Finally, a list of forward-looking recommendations was provided that, if implemented, would help ensure the success of the DoD acquisition process for acquiring reliable systems.