Software Quality Assurance Implementation Plan June 15, 2004

1
Software Quality AssuranceImplementation
PlanJune 15, 2004

• Defense Nuclear Facilities Safety Board
• Chip Lagdon
• Director
• Office of Quality Assurance Programs

2
Overview

• Recent Activities
• SQA Assessment Observations
• SQA Directives Status
• Open 2002-1 IP Commitments
• Path Forward

3
SQA Training

• SQA Training Conducted May 2004
• 22 attendees from NNSA, EM, EH
• ASQ Software Quality Engineer Course Content
• 2nd Course later this year
• 3 FAQS Competencies not Addressed
• 1 Specific to DOE Nuclear Safety
• 3 Specific to DOE Software Applications
• 9 Specific to Safety Analysis Standards
• Assist in Providing Qualification Approaches

4
Toolbox Codes

• Issued final gap analysis reports for ALOHA,
  MACCS2, EPIcode, MELCOR, CFAST GENII
• Posted on SQA Knowledge Portal
• Notified Users via SQA Newsletter/List Server
• Letters to Code Developers
• Will Develop Path Forward with PSOs

5
Toolbox Codes (cont.)

• Update Code Guidance Reports based on Final Gap
  Analysis June 2004
• Code Guidance Reports Toolbox Codes SQA
  Instructions on using code

6
Toolbox Code Gap Analysis Summary
7
Overview of Code Commitments
4.2.1.2 4.2.1.3 4.2.1.4 4.2.1.5
4.2.1.1 2002-1 Implementation Plan
(IP) Commitments 2002-1 IP Deliverables

Identify Safety Analysis Codes
Establish SQA Criteria
Perform Gap Analysis of Each Code
Develop Guidance Report for Each Code
Survey Design Codes
Safety Analysis Survey Report
SQA Plan and Criteria Report
Gap Analysis Reports
Code Guidance Reports
Design Code Survey Report

• CENTRAL REGISTRY
• Procedure for Central Registry
• SQA Criteria upgrade
• 3. Evaluate feasibility of upgrade Codes

8
SQA Assessment Observations

• 16 SQA Assessments Completed
• EH participated in 5 assessments
• EH review in progress
• Assessments are ongoing
• SQA Program Implementation
• Level of implementation varies across the complex
• SQA procedures are established at some sites and
  under development at others
• Control of authorized users of software needs
  improvement
• Procedures for legacy software need to be more
  clearly defined
• Multiple assessments may be needed to verify SQA
  program implementation at some sites

9
SQA Assessment Observations (cont.)

• CRADs
• Could be combined to eliminate duplication
• Supplemental criteria added for some SQA
  assessments
• SQA Documentation
• Configuration management (version control) and
  documentation for internally developed software
  needs to be strengthened
• COTS software documentation generally adequate.
  Error reporting and corrective action needs to be
  strengthened

10
SQA Directives Status

• DOE O 414.1C 2nd Draft Complete
• SME 1st draft comment disposition complete
• Start DOE-wide review (RevCom) August 2004
• Issue DOE O 414.1C December 2004
• DOE G 414.1-4
• 1st draft in progress
• Writing team meeting - Today
• Start DOE-wide review October 2004

11
Other Activities

• SQA Presentation for Subcommittee for Consequence
  Assessment and Protective Action (SCAPA)
• 2 SQA Technical Papers Published
• SQA Knowledge Portal Launched
• June SQA Newsletter Published

12
Open 2002-1 IP Commitments
13
Path Forward

• Develop Central Registry Procedure
• Update toolbox code guidance reports
• Continue to participate and evaluate SQA
  Assessments results
• NNSA and EM to update FRA documents
• Support training and qualification of SQA
  personnel