Document: NUREG-0800
Document ID: debf22b1-f3aa-4c75-a43c-f162d22de1c8
Document Type: srp
Title: of the plant safety analysis report (SAR).  Although the NRC did not endorse the annexes of
Source: NUREG-0800
Source URL: https://www.nrc.gov/docs/ML1515/ML15159A491.pdf
Revision Date: 2023-06
Chapter: 7
Section ID: 7.6
CFR Part: 
CFR Title: 

Content:
ions during the design process and after acceptance of the software for use will be made to the appropriate version and revision of the software. This will involve not only a review of the software CM documentation, but also a review of the actual methods being used at both the vendor and licensee sites, to ensure that the methods discussed in the plans are properly implemented. 5.3.6 Software Project Risk Management (IEEE Std 7-4.3.2, Sub-Clause 5.3.6) Software project risk management is a tool for problem prevention: identifying potential problems, assessing their impact, and determining which potential problems should be addressed to ensure that software quality goals are achieved. Risk management should be performed at all levels of the digital system project to provide adequate coverage for each potential problem area. Software project risks may include technical, schedule, or resource- related risks that could compromise software quality goals, and thereby affect the ability of the safety computer system to perform safety-related functions. Risk factors that should be addressed include system risks, mechanical or electrical hardware integration, risks due to the size and complexity of the product, the use of pre-developed software, cost and schedule, technological risk, and risks from program interfaces (e.g., maintenance, user, associate contractors, subcontractors, etc.). Appendix 7.1-D-14 Draft Revision 2 – August 2015 Risk management should include the following items: i. Determine the scope of risk management to be performed for the digital system. ii. Define and implement appropriate risk management strategies. iii. Identify risks to the software project in the project risk management strategy and as they develop during the conduct of the project. iv. Analyze risks to determine the priority for their mitigation. v. Develop risk mitigation plans for risks that have the potential to significantly impact software quality goals, with appropriate metrics