 |
|||
|
|
|||
|
Page Title:
Safety software design concepts as described in ANSI/IEEE |
|
||
| ||||||||||
|
|  DOE-STD-1172-2003
argument that software is safe.
b.
Define and discuss the following SRS attributes as they relate to safety software
quality:
Unambiguity
Consistency
Verifiability
Modifiability
Traceability
Readability
c.
Describe the methods used to ensure the requirements specifications attributes
are met.
d.
Describe and give specific examples of:
Functional requirements
Performance requirements
Design constraints
Attributes
External interfaces
Input/output requirements
Requirements Traceability Matrix
6.
Safety Software Quality Assurance personnel shall demonstrate a familiarity level
knowledge of the safety software design concepts as described in ANSI/IEEE
1016, IEEE Recommended Practice for Software Design Descriptions and Section
4 of NUREG/CR-6263, High Integrity Software for Nuclear Power Plants.
Supporting Knowledge, Skills, and Abilities
a.
Discuss the following concepts as they relate to safety software quality:
Modular design
External interface
Interfaces between both safety and non-safety components
Interface integrity
Data integrity, flow control
Exception and error handling
7.
Safety Software Quality Assurance personnel shall demonstrate a familiarity level
knowledge of the safety software coding practices that ensure that software
requirements specifications and design requirements are reflected in the source
code.
Supporting Knowledge, Skills, and Abilities
a.
Discuss the following concepts as they relate to safety software coding:
7
|
|
Privacy Statement - Press Release - Copyright Information. - Contact Us |
Click
here for thousands of PDF manuals