#4721 Defining Criteria for Requiring a Formal RCCA for Software Defects Identified by Problem Reports
#4721 Defining Criteria for Requiring a Formal RCCA for Software Defects Identified by Problem Reports #4721 <Inputs for RCCA Decision> Software development lifecycle includes requirements, design, implementation, unit and development testing, regression testing, formal verification and validation, integration testing, build, release ad delivery. Peer reviews of each lifecycle products are intended to catch and remove errors. Still, defects are found at different phases, possibly in the same release cycle, and possibly in later release cycles. Problem reports are filed when defects are found. The problem reports include type of error, where found, and severity level (1:loss of life, 2:loss of vehicle, 3:loss of mission, 4 and 5). When and why should formal root cause and corrective action (RCCA) analysis be performed? Formal Root Cause and Corrective Action (RCCA) analysis should not be treated as a routine bug-fix activity, but rather as an institutional m...