Document: NUREG-0800
Document ID: 4cca74ec-66e0-4765-9c61-cf547e17c308
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/ML1601/ML16019A114.pdf
Revision Date: 2023-06
Chapter: 7
Section ID: 7.6
CFR Part: 
CFR Title: 

Content:
ne 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 for tracking resolution progress. (These risks may include technical, schedule, or resource-related project risks that could compromise the ability of the safety computer system to perform safety-related functions). vi. Take corrective actions when expected quality is not achieved. vii. Establish a project environment that supports effective communications between individuals and groups for the resolution of software project risks. Additional guidance on the topic of risk management is provided in IEEE/EIA 12207.0-1996 and IEEE Std 1540-2001, “IEEE Standard for Life-cycle Processes - Risk Management.” Software project risk management differs from hazard analysis. A hazard is a condition that is prerequisite to an accident. Hazards include external events as well as conditions internal to computer hardware or software. The software and hardware safety plan addresses the identification, evaluation, and resolution of hazards. Hazard analysis is the process that explores and identifies conditions that are not identified by the normal design review and testing process. The scope of hazard analysis extends beyond plant design basis events by including abnormal events and plant operations with degraded equipment and plant systems. The software safety plan should include the safety analysis implementation tasks that are to be carried out by the applicant or licensee. The acceptance criterion for software safety analysis implementation is that the tasks in that plan have been carried out in their