1

Quality AssuranceSoftware Quality Assurance

Implementation PlansOctober 16, 2003

Defense Nuclear Facilities Safety Board

Beverly Cook

Assistant Secretary

Office of Environment, Safety and Health

2

Accomplishments

• Quality Assurance Improvement Plan

- EM: 14 of 16 commitments completed

- NNSA: 4 of 8 commitments completed

• SQA Improvement Plan

- EH: 7 of 26 commitments completed

3

Software Quality Assurance

October 16, 2003

Defense Nuclear Facilities Safety Board

Chip Lagdon

Director, Office of Quality Assurance Programs

Environment, Safety and Health

4

SQA IP – Completed Activities

• DOE Notice 411.1 Issued

• Office or Quality Assurance Programs

Established

• Industry & Federal Standards Report Issued

• Design Code Survey Issued

5

SQA IP – Completed Activities (Cont.)

• SQA Criteria Established

• Interim Code Specific Guidance Reports Issued

• Central Registry Established

• Revision 1 of the Safety Software Assessment

CRADs Issued

6

Purpose of the Central Registry

• Coordinate use of toolbox codes

• Assist code users in configuration control

• POC for resolving user issues

• Work with code owners to ensure technical support and training are available

• Communication Functions

- SQA problem reports

- Lessons Learned & Best Practices

- Sharing assessment results

7

Central Registry

• Central Registry is Part of TSP

• Web Site Contains:

• Toolbox Code Information (6)

• SQA Criteria

• Code Specific Guidance Reports

• Industry & Federal Standards Report

• Design Code Survey Form

8

Current Toolbox Codes

CODE APPLICATION SPONSOR SOURCE REMARKS

ALOHA 5.2.3

 

Project Manager: Mark.W.Miller@NOAA.gov

http://www.nwn.noaa.gov/sites/hazmat/cameo/aloha.html

Chemical release, plume and consequence

NOAA CAMEO Designed as a immediate response tool Code is distributed in machine language only, since the source code listing contains information that is copyrighted by AICHE, and NOAA can use it only for licensed purposes.

CFAST 3.1.6

http://fast.nist.gov/

Fire effects NIST NIST “FAST” website

Source code openly available on the internet in three versions.

EPICode 6.0

 

Website under construction.

E-mail epicode@aol.com

Chemical release, plume and consequence

Homann Associates, Inc.

Homann Associates, Inc.

Code has built-in function that verifies installed code against trial cases. Validation was against EPA test cases. Code has just been converted from DOS to Windows, with substantial increase in the number of hazardous substances in the library.

GENII 2.0

http://www.pnl.gov/eshs/software/genii.html

Radioactivity release, plume and consequence

EPA/NRC PNNL Version 1.45 is stable, since it hasn’t changed in several years. Version 2 is being tested by EPA and NRC.

MACCS2 1.12

No website provided, Nathan Bixler at SNL (505-845-3144) maintains code under direction of Jocelyn Mitchell at NRC JAM@nrc.gov (301-415-5289), who controls distribution and maintains QA.

Radioactivity release, plume and consequence

NRC SNL Developed to NQA-1, except for monetary consequence calculations.

MELCOR 1.8.5

http://melcor.sandia.gov/

Radioactivity leakage pathway

NRC SNL Code is chiefly of value in nuclear reactor accident simulations. Developed to NQA-1.

9

What is Coming Up?

• Identification of Federal SQA Positions – October

• Functional Area Qualification Standard – November

• Schedule Established for Conducting Safety Software Assessments – October

• Design Code Survey Report Issued – December

• Relationship Established with Outside SQA Groups and POC identified – December

• SQA Information Sharing Mechanism – October

• Schedule Established for Developing/Revising Directives – October

10

SQA IP Commitments

Schedule established to complete assessment

Schedule established to complete assessment

4.2.3.2

4.2.4.2

CRAD developed

for SSS and Firmware

Code specific

guidance reports issued

Central registry

established

EstablishSQA

toolbox criteria1

Gap analysis p

schedule developed

erformed and

CRAD developed for design software

Survey conducted for toolbox

design codes

4.2.3.1

4.2.1.4

4.2.2

4.2.1.2 4.2.1.3

4.2.4.1

4.2.1.5

Directives implementation

plan and schedule approved

4.3.3

SMEpanel

established

Review of industry and Fed

standards completed

Methods established

for SQA information

sharing

Participate with

outsideSQA

Groups

EH QA function

established

Schedule established to develop or revise directives

SMEpanel

established

SMEpanel

established

SMEpanel

established

SMEpanel

established

SMEpanel

established

DOE Notice Issued1

FRAMRevised

Directives issuedper schedule

in 4.3.2.1

Assessmentscompleted per schedule

in 4.2.3.2

Assessmentscompleted per schedule

in 4.2.4.2

SQAFAQS

Developed

SQA personnel qualified

Fed SQA Positions Identified

FRARevised

JUNE JULY AUG SEPT OCT NOV DEC JAN FEB MARCH APRIL MAY JUNE JULY AUG SEPT OCT NOV DEC

4.1.1 4.1.5

4.1.44.1.3

4.3.1 4.3.2.1 4.3.2.2

4.2.3.3

4.2.4.3

4.4.2

4.4.3

BoardBrief

5.2.1

BoardBrief

5.2.1

BoardBrief

5.2.1

BoardBrief

5.2.1

4.4.1

4.1.2

4.1.6

2 OFTWARE UALITY SSURANCE MPLEMENTATION LAN OMMITMENTS002-1 S Q A I P C

Roles and Responsibilities

Computer Codes

Requirements and Guidance

Continuous Improvement

Board Briefings

2003 2004

NOTE

1 Commitment due date changed from July to September in July 16, 2003 letter to DNFSB.