Document: NUREG-0800
Document ID: 21b37b7c-b45c-4247-b4a5-c2f28df75be4
Document Type: srp
Title: INSTRUMENTATION AND CONTROLS (Tier 1)
Source: NUREG-0800
Source URL: https://www.nrc.gov/docs/ML0520/ML052070663.pdf
Revision Date: 2023-06
Chapter: 14
Section ID: 14.3.5
CFR Part: 
CFR Title: 

Content:
dard for Software Project Management Plans." 15. IEEE Std P-1228, "Standard for Software Safety Plans." 16. IEEE Std 7-4.3.2-1993, "Standard Criteria for Digital Computers in Safety Systems of Nuclear Power Generating Stations." DRAFT Rev. 0 - April 1996 14.3.5-12 Inspections, Tests, Analyses and Acceptance Criteria Design Commitment Inspections, Tests, Acceptance Criteria or Analyses 7. A quality assurance program 7. The program for quality 7. A quality assurance program is in place encompassing software is employed assurance that encompasses that defines controlled processes for as a controlled process for software software shall be reviewed. software development, hardware development, hardware integration, integration, and final product and system and final product and system testing. testing. As a minimum, the program 8. A Software Management Plan 8. The Software Management Plan shall (SMP) shall be instituted which 8. The Software Management define: establishes that software for Plan shall be reviewed. embedded control hardware shall be a. The organization and responsibilities developed, designed, evaluated, and for development of the software design; documented per a design the procedures to be used in the software development process. The software development; the interrelationships safety issues shall be defined at each between software design activities; and the life-cycle phase of the software methods for conducting software safety development. analyses. For each life-cycle phase, the SMP b. That the software safety analyses to be shall define the current state of that conducted for safety-related software design phase and the input for the applications shall: next design phase. requires a Software Management Plan, Configuration Management Plan and Verification and Validation Plan as described in the following items. (1) Identify software requirements having safety-related implications. (2) Document the identified safety-critical software requirements in