Scribd
Upload
83 views1 page

2.6.5 Safety Software Quality Assurance

1. Safety Software at Berkeley Lab must follow quality assurance requirements to ensure proper approval, control, testing and adherence to the lifecycle management policy. 2. The requirements include considering system-wide risks, documenting the software's functions, creating and executing tests across operating conditions, and approving, documenting, testing and archiving any changes. 3. Safety software includes safety system software, safety analysis software, design software, and safety management software that performs safety functions for systems and facilities.

Uploaded by

sami ullah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
83 views1 page

2.6.5 Safety Software Quality Assurance

1. Safety Software at Berkeley Lab must follow quality assurance requirements to ensure proper approval, control, testing and adherence to the lifecycle management policy. 2. The requirements include considering system-wide risks, documenting the software's functions, creating and executing tests across operating conditions, and approving, documenting, testing and archiving any changes. 3. Safety software includes safety system software, safety analysis software, design software, and safety management software that performs safety functions for systems and facilities.

Uploaded by

sami ullah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

2.6.

5 Safety Software Quality Assurance


Safety Software is software whose degradation can have a direct effect on human safety (see full
definition in Section F. below). Safety Software at Berkeley Lab must be appropriately, approved,
controlled and tested. Our lifecycle management policy requires that Safety Software adhere to the
quality assurance requirements in this document.

Management may adopt a subset of these requirements for software that is part of a safety chain,
but where a non-software control protects human safety from software degradation.

Our SSQA approach sets four core requirements:

1. The process owner must consider the system as a whole in considering the risks, taking into
account software and non-software components.
2. The Software must be documented to a level where users, developers, and those providing
oversight can understand its functions.
3. Tests must be created and executed which clearly show that the software is performing as
intended across a range of operating conditions. These tests must be repeated at any time that the
environment or the software changes in a way that could create differences in behavior.
4. Changes to the software must be approved, documented, tested, and archived to provide for
rigorous, continuous oversight

Safety software includes safety system software, safety and hazard analysis software and design
software, and safety management and administrative control software, and performs a safety
function as part of a system, structure or component (SSC), and is cited in either a DOE-approved
safety analysis document (SAD) or a Lab Directorate-approved hazard analysis document (HAD).

 Safety and Hazard Analysis Software and Design Software is used to classify, design or
analyze nuclear/radiological facilities.
 Safety Management and Administrative Controls Software 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

You might also like