Docstoc

Fermilab Software Quality Assurance

Document Sample
Fermilab Software Quality Assurance Powered By Docstoc
					SUBJECT: RESPONSIBILITY: APPROVED BY:

Software Quality Assurance

NUMBER: REVISION: EFFECTIVE:

10.XX.XX 000 A

SOFTWARE QUALITY ASSURANCE

FQAP 10.01

Page 1 of 7

Rev000

SUBJECT: RESPONSIBILITY: APPROVED BY:

Software Quality Assurance

NUMBER: REVISION: EFFECTIVE:

10.XX.XX 000 A

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43

1.1.1. SOFTWARE QUALITY ASSURANCE 1.1.1.1.INTRODUCTION Software quality assurance (SQA) programs are required contractually by DOE N 203.1, Software Quality Assurance, and DOE O 414.1C, Quality Assurance. Requirements are implemented to ensure that software will perform its intended specific function in relation to Fermi structures, systems, components, data, and activities. Software controls are required to be developed and implemented using national and international consensus standards using a graded approach to ensure that those controls are applied commensurate with the software application. DOE N 203.1 details the requirements for software quality assurance. The SQA requirements apply to all DOE software or software customized for DOE use, proposed for use, under development, or being maintained and used, whether that software was developed in-house, licensed from a commercial vendor for customized use, obtained from another organization or otherwise acquired. (DOE N 203.1) The type of software includes, but is not limited to: (a) administrative/business-oriented software, (b) scientific/engineering software (where governed by 10 CFR 830), (c) manufacturing-oriented software, and (d) process control. Software that is designated "safety software" has additional specific controls imposed as discussed in Section 2.2.2.4. DOE O 414.1C, Contractor Requirements Document. 1.1.1.2.SOFTWARE CONTROL ELEMENTS  Line management must ensure adequacy of training programs to meet current and future personnel skill needs in the areas of SQA, software engineering, and software user training.  Fermilab senior management must ensure the integration of the SQA program planning process with strategic planning, the Integrated Safety Management System (ISMS), and the budget process, as appropriate, to ensure that SQA program decisions are made, adequately funded, and executed to support DOE organizational and site missions and priorities.  Divisions must develop SQA programs as detailed in Section 2.2.2.3.  Divisions must, in developing their management assessment schedules, ensure inclusion of their SQA programs for periodic review. OQBP must conduct systematic reviews to ensure that the requirements of the DOE directives are met. NOTE: Relative to software, these reviews should also ensure that appropriate safety and security controls are in place, are effective, and reflect currently accepted industry practices. (DOE N 203.1) 1.1.1.3.SOFTWARE QUALITY ASSURANCE PROGRAMS SQA programs must be developed and documented for software projects and applications. The expectation is that this documentation will be completed at the division or organizational level matching the type and importance of each organizational unit's software applications. The programs must be commensurate with the size,
FQAP 10.01 Page 2 of 7 Rev000

SUBJECT: RESPONSIBILITY: APPROVED BY:

Software Quality Assurance

NUMBER: REVISION: EFFECTIVE:

10.XX.XX 000 A

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38

complexity, cost, degree of external impact and customization, functions performed, and other factors important to management, and must include:      Identified point of contact Defined authorities Policies, procedures, training requirements Adopted standards Conventions tailored to local needs

SQA processes and procedures used must be software product and project life-cycle based; documented to provide a baseline for auditing; and applied in a consistent, repeatable, and predictable manner. SQA plans must be developed and must address:       Inspections, audits, and any other requirements specified for an application; Configuration Management, Peer reviews, Structured walkthroughs, Testing including acceptance testing, and Verification, and validation.

Each SQA plan must be commensurate with the level of size, complexity, and scope of the software project. An SQA plan can be adopted and/or adapted for subsequent projects within a program. Software quality assurance implementation is described in [Software Quality Assurance] 1.1.1.4.SAFETY SOFTWARE Fermilab does not employ safety software under the definition of safety software in DOE Order 414.1C Quality Assurance. The governing policy, available on the Computing Division web site states: It is Fermilab policy to avoid reliance on a computer as an essential element of any system that is necessary to protect people from serious harm, to protect the environment from significant impact, or to protect property the loss of which would have a serious impact on our mission. The use of computers for monitoring, data logging, and reporting is encouraged, however computers used for these purposes must not be essential for protection. Contact the Fermilab Computer Security Executive for any variance.

FQAP 10.01

Page 3 of 7

Rev000

SUBJECT: RESPONSIBILITY: APPROVED BY:

Software Quality Assurance

NUMBER: REVISION: EFFECTIVE:

10.XX.XX 000 A

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

ACROYNYMS AC –Advisory Council on Integrated Assurance (Assurance Council) ACC – Accelerator Advisory Committee AD (when referring to a Division) – Accelerator Division AD (when referring to the Directorate) – Associate Director ANL – Argonne National Laboratory ANSI – American National Standards Institute ASQ – American Society for Quality BSS – Business Services Section CAP – Corrective Action Plan CAS – Contractor Assurance System CD – Computing Division CE – Cognizant Engineer CERN - Organisation Européenne pour la Recherche Nucléaire, Europe’s central treaty-based particle physics laboratory CEU – Continuing Education Units CFO – Chief Financial Officer CFR – U.S. Code of Federal Regulations CMP – Configuration Management Plan C of A – Certificate of Assurance C of C – Certificate of Conformance COO – Chief Operating Officer CRD – Contractor Requirements Document DA – Design Authority DEAR – Department of Energy Acquisition Regulation DOE - U.S. Department of Energy ECO – Engineering Change Order

FQAP 10.01

Page 4 of 7

Rev000

SUBJECT: RESPONSIBILITY: APPROVED BY:

Software Quality Assurance

NUMBER: REVISION: EFFECTIVE:

10.XX.XX 000 A

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44

ES&H – Environment, Safety & Health Section ESHTRK – ES&H Event Tracking System FAI – First Article Inspection FAR – Federal Acquisition Regulation FEMP – Fermilab Engineering Manual & Procedures FESM – Fermilab ES&H Manual FESS – Fermilab Engineering Services Section FNAL – Fermi National Accelerator Laboratory, also known as Fermilab FRA – Fermilab Research Alliance, LLC FTP – Field Task Proposal GERT – General Employee Radiation Training HA – Hazard Analysis HEP – High Energy Physics HEPAP – DOE High Energy Physics Advisory Panel ICTP – Integrated Contractor Purchasing Team Agreement IEPA – Illinois Environmental Protection Agency ILC – International Linear Collider IMS – Issues Management System ISS – Integrated Stores System ITNA – Individual Training Needs Assessment LCC – Laboratory Collaboration Council LOTO – Lock Out / Tag Out (also LO/TO) M&TE – Measurement & Test Equipment MIS – Management Information Systems MOU - Memorandum of Understanding MSDS – Material Safety Data Sheet NCR – Nonconformance Report NIST – National Institute of Standards & Technology ODH – Oxygen Deficiency Hazard OHSAS – Occupational Health & Safety Assessment System OJT – On the Job Training OPMO – Office of Project Management Oversight OQBP – Office of Quality & Best Practices ORTA – Office of Research & Technology Assessment PAC – Physics Advisory Committee PEP – Project Execution Plan PPD – Particle Physics Division PPE – Personal Protective Equipment PEMP – Performance Evaluation Measurement Plan QA – Quality Assurance QAIM – Quality Assurance Inspection Manual QAP – Quality Assurance Plan QAR – Quality Assurance Representative QDT – Quality Development Team

FQAP 10.01

Page 5 of 7

Rev000

SUBJECT: RESPONSIBILITY: APPROVED BY:

Software Quality Assurance

NUMBER: REVISION: EFFECTIVE:

10.XX.XX 000 A

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

QMS – Quality Management System QSL – Qualified Supplier List R&D – Research & Development S/CI – Suspect/Counterfeit Items SQA – Software Quality Assurance SSC – Structures Systems & Components TD – Technical Division TRAIN – Fermilab’s Training Database for Plans and Records WAAF – Medical Department’s Work Activities Analysis Form WDRS – Workforce Development & Resources Section

References (1) DOE G 414.1-1A, Management Assessment and Independent Assessment Guide for Use with 10 CFR, Part 830, Subpart A, and DOE O 414.1A, Attachment 2 DOE O 414.1C dated 4 6-17-05 Quality Assurance; DOE P 450.4, Safety Management System Policy; and DOE P 450.5, Line ES&H Oversight Policy, dated 5-31-01. (2) DOE G 414.1-2A, Quality Assurance Management System Guide for Use with 10 CFR 830 Subpart A Quality Assurance Requirements and DOE O 414.1C, Quality Assurance, dated 6-17-05. (3) DOE G 414.1-3, Suspect/Counterfeit Items Guide for Use with 10 CFR 830 Subpart A, Quality Assurance Requirements, and DOE O 414.1B, Quality Assurance, dated 11-03-04. (4) DOE G 414.1-4, Safety Software Guide for use with 10 CFR 830 Subpart A, Quality Assurance Requirements, and DOE O 414.1C, Quality Assurance, dated 6-17-05. Fermilab Director’s Policy Manual, policy number 10, Quality Assurance

FQAP 10.01

Page 6 of 7

Rev000

SUBJECT: RESPONSIBILITY: APPROVED BY:

Software Quality Assurance

NUMBER: REVISION: EFFECTIVE:

10.XX.XX 000 A

1 2

Table of Revisions Author(s) Jed Heyes

Description Extracted from QAP by QDT

Revision Draft

Date 11/26/07

3 4 5 6

FQAP 10.01

Page 7 of 7

Rev000


				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:6
posted:1/12/2010
language:English
pages:7