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

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

Embed Size (px)

Citation preview

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

Software Quality AssuranceImplementation Plan

June 15, 2004

Defense Nuclear Facilities Safety Board

Chip Lagdon

Director

Office of Quality Assurance Programs

Page 2: Software Quality Assurance Implementation Plan June 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

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

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

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

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

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

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

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

6

Toolbox Code Gap Analysis Summary

Criteria MACCS2 ALOHA EPIcode MELCORGENII1.485

GENII2.0

CFAST

SoftwareClassification Yes Yes Yes Yes Yes Yes Yes

Procedures/Plan Partial No No Partial Yes Partial No

Requirements No Partial Partial Partial Yes Partial No

Design Partial Partial Partial Partial Yes Partial Partial

Implementation Partial Partial Partial Yes Yes Partial Partial

Testing Partial Partial Partial Partial Yes Partial Partial

Instructions Yes Yes Yes Yes Yes Partial Partial

Accept Test Partial No Partial Yes Yes Partial Partial

Config. Cont. No Partial Partial Yes Yes Yes Yes

Error Impact Partial Partial Partial Partial Partial Partial Partial

Resources (FTE) 2.0 yr 1.25 yr 1.25 yr 2.0 yr 1.0 yr N/A 0.5 yr

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

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-1ImplementationPlan (IP)Commitments

2002-1 IPDeliverables

Identify Safety Analysis Codes

Establish SQA

Criteria

Perform Gap Analysi

s of Each Code

Develop Guidance Report for Each

Code

Survey Design Codes

Safety Analysi

s Survey Report

SQA Plan and Criteria Report

Gap Analysis Reports

Code Guidanc

e Reports

Design Code

Survey Report

CENTRAL REGISTRY1. Procedure for Central Registry2. SQA Criteria upgrade3. Evaluate feasibility of upgrade Codes

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

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

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

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

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

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

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

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

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

12

Open 2002-1 IP Commitments

Commitment

DescriptionResponsibili

tyStatus

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

Conduct site assessments EM, NNSA Open(per schedule)

4.3.2.2 Issue SQA Directive EH Open(12/04)

4.3.3Implement SQA Directives

EM, NNSA Open (per issuance)

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

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