Document: NRC Regulatory Guide
Document ID: c6321e39-3d1b-40a6-ace3-8c6a0c54e2cd
Document Type: regulatory_guide
Title: Developing Software Life Cycle Processes for Digital Computer Software Used in Safety Systems of Nuclear Power Plants + HISTORY - HISTORY 08/2012 – DG-1210 , Proposed Revision 1 08/1996 – DG-1059 , Proposed Revision 0 (Rev. 1)
Source: NRC Regulatory Guide Division 1
Source URL: https://www.nrc.gov/docs/ML1031/ML103120727.pdf
Revision Date: 2023-06
Chapter: 
Section ID: RG-1.173
CFR Part: 
CFR Title: 

Content:
istent with the defined system safety analyses, an additional activity group, “Software Safety Analysis Activity Group,” is necessary. This activity group will include additional activities beyond those specified in IEEE Std. 1074-2006. Planned and documented software safety analysis activities should be conducted for each phase of the software development life cycle. Therefore, these analyses should be identified in the licensee’s or applicant’s life-cycle model, including the following input information, activity descriptions, and output information: a. Input Information. Input information necessary to support software safety analyses includes (1) regulatory requirements and guidance, (2) system safety analysis information, (3) information from previous phases for the software safety analysis, (4) design information from previous and current system and software phase activities, and (5) established baseline SDOE objectives. b. Activity Description. The analyses should ensure that (1) system safety requirements have been correctly addressed, (2) no new hazards have been introduced, (3) software elements that can affect safety are identified, (4) there is evidence that other software elements do not affect safety, (5) safety problems and resolutions identified in these analyses are documented, (6) there are developed threat model(s) for the safety software product(s), (7) system software architecture(s) are explored for known and potential SDOE vulnerabilities and their impact, and (8) SDOE accreditation is confirmed. These activities should be conducted according to a software safety plan that addresses the organization to perform the analyses, the responsibilities of its safety officer, the management of the software safety activities, and the analyses to be performed for each phase to address hazards and abnormal conditions and events. c. Output Information. The software safety analysis reports the information for the current phase activities. The