DOE Safety Software Quality Assurance Approach

1
DOE Safety Software Quality Assurance Approach

• Debra Sparkman
• January 2005

2
Purpose General Information

• Improve DOE and contractor safety software
• Secretarial Commitment to DNFSB (Rec 2002-1)
• Focused on nuclear facility safety
• Compatible with national standards
• Compatible with current program requirements
• Does not supersede externally regulated software

3
Safety Software Definitions

• SAFETY SYSTEM SOFTWARE. Software for a nuclear
  facility that performs a safety function as part
  of an SSC and is cited in either 1) DOE approved
  documented safety analysis or, 2) an approved
  hazard analysis per DOE P 450.4 safety management
  system policy and the dear clause.

4
Safety Software Definitions - cont

• SAFETY AND HAZARD ANALYSIS SOFTWARE AND DESIGN
  SOFTWARE. Software that is used to classify,
  design, or analyze nuclear facilities.  This
  software is not part of an SSC but helps to
  ensure the proper accident or hazards analysis of
  nuclear facilities or an SSC that performs a
  safety function.

5
Safety Software Definitions - cont

• SAFETY MANAGEMENT AND ADMINISTRATIVE CONTROLS
  SOFTWARE. Software that performs a hazard control
  function in support of Safety Management Programs
  or Technical Safety Requirements or, other
  software that performs a control function
  necessary to provide adequate protection from
  hazards. This software supports eliminating,
  limiting, or mitigating hazards to workers, the
  public, or the environment. Per 10 CFR 830,
  quality assurance requirements apply to all DOE
  nuclear facilities including radiological
  facilities (see 10 CFR 830, DOE Std 1120, and the
  DEAR Clause).

6
The DOE Focus

• 3 Basic Areas
• Roles, Responsibilities Qualifications of DOE
  Staff
• Quality of the Software
• Continuous Improvement

7
Roles, Responsibilities Qualifications

• Develop qualification standard for Fed staff
• Identify the Feds responsible for SQA
• Qualify the Feds
• Courses (e.g., ASQ CQE BOK, SEI, Sw Safety)
• Job Experience
• Expectations for contractor qualifications

8
Quality of Software

• Create a Central Location for Commonly Used
  Software establish criteria for being in CR,
  establish minimum SQA criteria, assess codes
  determine gaps, close gaps.
• Assess Existing Software Establish assessment
  criteria, determine what to assess and when,
  perform the assessments.
• Establish New SQA Requirements graded approach,
  NQA-1 based.

9
Basic Safety Software Requirements DOE O 414.C

• Facility design authority involvement in
  identifying software specification acquisition,
  design, development, verification and validation
  (including inspection and test), configuration
  management, maintenance, and retirement.
• Identify, document, and maintain safety software
  inventory.
• Establishes ASME NQA-1-2000 as the standard to
  use for safety software supplemented by other
  consensus standards.
• Designate safety software as either grade Level
  A, Level B, or Level C.
• Select and implement the applicable software
  quality assurance work activities using the
  grading levels.

10
10 Required SQA Work Activities

• Software project management
• Software risk management
• Software configuration management
• Procurement vendor management
• Software requirements identification management
• Software design implementation
• Software safety design
• Verification validation
• Problem reporting corrective action
• Training of personnel in the design, development,
  use evaluation of safety software

11
Continuous Improvement

• Communications
• List Server
• SQA Knowledge Management Portal
• Collaborations
• Subject Matter Expert Panel
• DOE participation on standards working groups
  (ANSI/ASQ, IAEA, ASME/NQA-1, ANS)
• Safety Critical Community Discussion Board
• DOE Liaison for IEEE S2ESC

12
Path Forward

• Roles and Responsibilities
• Federal Staff is being qualified
• Quality of Software
• Initial software assessments completed
• Central Registry and tool box codes in place
• Tool box codes will be upgraded to remove gaps
• Directives waiting to be issued
• Continuous Improvement
• In place and continually expanding