|
| DOE-STD-1170-2003
i.
Review a maintenance history file and discuss the potential implications of repeat
maintenance items.
j.
Explain the intent of a Maintenance Problem Analysis Program and discuss a
maintenance problem where this program has been employed.
38.
Personnel shall demonstrate a working level knowledge of the functional
interfaces between safety system software components and the system-level
design.
Knowledge, Skills, and Abilities
a.
Identify how system-level requirements are established and then assigned to
hardware, software, and human components of a digital instrumentation and
control system.
b.
Identify the typical requirements that define functional interfaces between safety
system software components and the system -level design, as described in
standards such as ANSI/IEEE 830, IEEE Guide to Software Requirements
Specifications and IEEE 7-4.3.2, Standard Criteria for Digital Computers in Safety
Systems of Nuclear Power Generating Stations.
c.
Identify the specific records that must be maintained and the requirements for
maintaining these records to document the development of safety system
software.
d.
Review a development project for safety system software. Explain how the
functional interfaces between components and the system level design were
established and controlled.
39.
Personnel shall demonstrate a working level knowledge of the relationships
between the problems being addressed by safety analysis and design codes, the
design requirements for the codes, and the components of the codes.
Knowledge, Skills, and Abilities
a.
Identify how functional requirements and applicability of safety analysis and
design computer codes are defined, documented, and controlled relative to
modeling and data assumptions, design constraints, sizing and timing conditions
and input/output parameters.
b.
Review a development project for safety analysis or design software. Explain
how the problem being addressed by the software was translated into functional
requirements, how the requirements were established and controlled, and how
the code was reconciled with the original problem.
26
|
Privacy Statement - Press Release - Copyright Information. - Contact Us |