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:
able in Regulatory Guide 1.152, whereas guidance for cyber security is available in Regulatory Guide 5.71, “Cyber Security Programs for Nuclear Facilities” (Ref. 19). e. Definitions. The following definitions are used in this regulatory guide: (1) Accident. An unplanned event or series of events that result in death, injury, illness, environmental damage, or damage to, or loss of, equipment or property. DG-1210, Page 8 (2) Hazard. A condition that is a prerequisite to an accident. 2. Compliance with IEEE Std. 1074-2006 Criterion II of Appendix B to 10 CFR Part 50 requires all activities affecting quality to be accomplished under suitably controlled conditions. Subclause 1.5, “Conformance,” of IEEE Std. 1074-2006 permits the elimination of some life-cycle activities, although compliance with the standard may not then be claimed. The NRC Staff position is that compliance with IEEE Std. 1074-2006 means that all mandatory activities are performed; the requirements described as “shall” are met; and all the inputs, outputs, activities, preconditions, and postconditions mentioned by IEEE Std. 1074-2006 are described or accounted for in the licensee’s or applicant’s life-cycle model. IEEE Std. 1074-2006 is an organizing standard that ensures that activities deemed important to software quality are performed and are related properly to one another; it does not provide detailed information on the implementation of specific life-cycle activities. 3. Software Safety Analyses Criterion III of Appendix B to 10 CFR Part 50 requires, in part, that measures to ensure that applicable regulatory requirements and the design basis are correctly translated into specifications, drawings, procedures, and instructions. To ensure that safety system software development is consistent 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