1 / 15

New DOE Software Quality Assurance Requirements: Implications for Meteorological Software

New DOE Software Quality Assurance Requirements: Implications for Meteorological Software . Cliff Glantz Pacific Northwest National Laboratory cliff.glantz@pnl.gov 509.375.2166 Presented at NUMUG 2006 – St. Louis. Overview.

vivi
Télécharger la présentation

New DOE Software Quality Assurance Requirements: Implications for Meteorological Software

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. New DOE Software Quality Assurance Requirements: Implications for Meteorological Software Cliff Glantz Pacific Northwest National Laboratory cliff.glantz@pnl.gov 509.375.2166 Presented at NUMUG 2006 – St. Louis

  2. Overview • Background information on the new DOE Software Quality Assurance (SQA) Order and Guide • What type of software does this new Order impact? • What will be required? • What does this mean for DOE-related meteorological programs and vendors of meteorological software? 2

  3. Background Info • Defense Nuclear Facility Safety Board (DNFSB) issued “Quality Assurance for Safety Related Software at Department of Energy Defense Nuclear Facilities” inJanuary 2000 • Little progress was made in addressing issues raised by the DNFSB 3

  4. Background Info (cont) • DNFSB issued Quality Assurance for Safety-Related Software in September 2002 • Calls for prompt actions in: • Defining SQA responsibility and authority • Recommending standards for computer codes used for safety analysis and design 4

  5. Implementation Plan for DNFSB Recommendation • DOE accepted the DNFSB Recommendation in November 2002 • Issued Implementation Plan in March 2003 • Prepared and issued an SQA Order and Guide for Safety Software in the summer of 2005 5

  6. Safety Software is Defined to Include: • (1) Safety System Software. Software for a nuclear facility that performs a safety function as part of a structure, system, or component (SSC). • (2) Safety and Hazard Analysis Software and Design Software. Software that is used to classify, design, or analyze nuclear facilities. This software helps to ensure the proper accident or hazards analysis of nuclear facilities or an SSC that performs a safety function 6

  7. Safety Software defined (continued) • (3) Safety Management and Administrative Controls Software. Software that performs a hazard control function in support of nuclear facility or radiological safety management programs or technical safety requirements or other software that performs a control function necessary to provide adequate protection from nuclear facility or radiological hazards. This software supportseliminating, limiting, or mitigating nuclear hazards to workers, the public, or the environment… 7

  8. Application of the SQA Order SQA requirements apply to consequence assessment models used for: • hazards assessment/safety planning purpose. • emergency response purposes and provide a direct hazard control function. These are models used to make protection action recommendations (PARs), such as HOTSPOT, EPI, ALOHA,… 8

  9. Application (cont) SQA requirements appear to apply to meteorological software that is used to : • provide data/information used in a safety or hazard analysis • provide data used in emergency preparedness and response, fire protection, waste management, or radiological protection. 9

  10. Applications (cont) • Applicable meteorological software is used to: • measure, process, store, and communicate data at meteorological monitoring locations • process, store, and communicate meteorological data at central weather stations or data repositories • process, store, and display meteorological data at Emergency Operation Centers. 10

  11. SQA Requirements in a Nutshell Five types of software are mentioned in the Order: • Custom developed • Configurable • Acquired (includes commercial off-the-shelf meteorological software) • Utility calculations • Commercial design and analysis tools. For each type of software, three different levels (A, B, or C) can be assigned based on how the software is being used. Ten work activities are required. Depending on the assigned SQA level, a full or graded approach to the work activity is required. 11

  12. 12

  13. DOE/EH SQA Webpage http://www.eh.doe.gov/sqa/dir.htm 13

  14. What Does this Mean for Vendors? • DOE customers may be coming back to you for additional information on your SQA practices and documentation • DOE customers will be asking more of you in the SQA arena when they acquire new software • A vendor’s existing SQA program may be sufficient to meet DOE needs. • Vendors should review the DOE SQA Order and Guide to prepare for questions their DOE customers may have. 14

  15. Conclusions • DOE Sites will need to make sure that their meteorological software complies with the DOE SQA Order and Guide. • Software vendors will be asked to provide documentation to ensure that their software design, development, testing, and maintenance program is in compliance with the SQA Order and Guide. 15

More Related