Document: NRC Regulatory Guide
Document ID: 2980f2d9-2e7d-4afa-9e1f-a8abe5fb7507
Document Type: regulatory_guide
Title: Software Requirement Specifications for Digital Computer Software and Complex Electronics Used in Safety Systems of Nuclear Power Plants + HISTORY - HISTORY 08/2012 – DG-1209 , Proposed Revision 1 08/1996 – DG-1058 , Proposed Revision 0 (Rev. 1)
Source: NRC Regulatory Guide Division 1
Source URL: https://www.nrc.gov/docs/ML1030/ML103080963.pdf
Revision Date: 2023-06
Chapter: 
Section ID: RG-1.172
CFR Part: 
CFR Title: 

Content:
ics engineering and computer science fields including multiple tutorials and standards produced by its standardization committees. Endorsement, in whole or in part, of multiple international standards reduces the need for the development of unique NRC standards and is consistent with the agency goal of improved harmonization with international organizations. DG-1209, Page 6 C. STAFF REGULATORY GUIDANCE IEEE Std. 830-1998 provides an approach that the NRC staff considers acceptable for meeting the requirements in 10 CFR Part 50 on the preparation of SRSs for safety system software with the exceptions and additions listed in these regulatory positions. In this section of the guide, the cited criterion refers to Appendix A or B to 10 CFR Part 50 unless otherwise noted. 1. Definitions Clause 3 of IEEE Std. 830-1998 refers to IEEE Std. 610.12-1990, “IEEE Standard Glossary of Software Engineering Terminology,” issued 1990 (Ref. 19), for the definitions of technical terms. These definitions are acceptable with the following clarifications and additions: a. Baseline. Meaning No. 1 of “baseline” in IEEE Std. 610.12-1990 must be used in IEEE Std. 830-1998. “Formal review and agreement” is considered to mean that responsible management has reviewed and approved a baseline. b. Interface. All four variations of the definition of “interface” in IEEE Std. 610.12-1990 must be used in IEEE Std. 830-1998, depending on the context. Meaning No. 1, “a shared boundary across which information is passed,” is interpreted broadly, according to Criterion III of Appendix B to 10 CFR Part 50, to include design interfaces between participating design organizations. 2. Software Requirement Specifications Clause 4.3 of IEEE Std. 830-1998 defines a set of characteristics of an acceptable SRS. The first sentence of this clause should be modified to read, “An SRS must be….” The licensee or applicant should provide the following clarifications and additional information for