1. Software Quality Assurance Implementation Plan June 15, 2004 Defense Nuclear Facilities Safety Board Chip Lagdon Director Office of Quality Assurance Programs

2. 2 Overview Recent Activities SQA Assessment Observations SQA Directives Status Open 2002-1 IP Commitments Path Forward

3. 3 SQA Training SQA Training Conducted – May 2004 22 attendees from NNSA, EM, & EH ASQ Software Quality Engineer Course Content 2 nd 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. 4 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 PSO’s Toolbox Codes

5. 5 Update Code Guidance Reports based on Final Gap Analysis – June 2004 Code Guidance Reports + Toolbox Codes = SQA Instructions on using code Toolbox Codes (cont.)

6. 6 Toolbox Code Gap Analysis Summary Criteria MACCS2ALOHAEPIcodeMELCOR GENII 1.485 GENII 2.0 CFAST Software Classification Yes Procedures/Plan PartialNo PartialYesPartialNo Requirements NoPartial YesPartialNo Design Partial YesPartial Implementation Partial Yes Partial Testing Partial YesPartial Instructions Yes Partial Accept Test PartialNoPartialYes Partial Config. Cont. NoPartial Yes Error Impact Partial Resources (FTE) 2.0 yr1.25 yr 2.0 yr1.0 yrN/A0.5 yr

7. 7 Overview of Code Commitments 4.2.1.24.2.1.34.2.1.44.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 1.Procedure for Central Registry 2.SQA Criteria upgrade 3.Evaluate feasibility of upgrade Codes

8. 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. 9 SQA Assessment Observations (cont.) CRAD’s 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. 10 SQA Directives Status DOE O 414.1C 2 nd Draft Complete SME 1 st 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. 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. 12 Open 2002-1 IP Commitments CommitmentDescriptionResponsibilityStatus 4.1.4 Qualify Federal personnel EM, NNSA Open (9/04) 4.1.6 Revise FRA documents EM, NNSA Open (4/04) 4.2.3.3 4.2.4.3 Conduct site assessments EM, NNSA Open (per schedule) 4.3.2.2 Issue SQA Directive EH Open (12/04) 4.3.3 Implement SQA Directives EM, NNSA Open (per issuance)

13. 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