PURPOSE
|
. The purpose of Task 203 is to perform and document the safety design requirements/design criteria for a facility or system under development/design.
| |
TASK DESCRIPTION
|
The Safety Requirements/Criteria Analysis (SRCA) relates the hazards identified to the system design and identifies or develops design requirements to eliminate or reduce the risk of the identified hazards to an acceptable level. The SRCA uses the Preliminary Hazard List (Task 201) or the Preliminary Hazard Analysis (Task 202) as a basis, if available. The SRCA is also used to incorporate design requirements that are safety related but not tied to a specific hazard. The analysis includes the following efforts:
| |
The contractor shall determine applicable generic system safety design requirements and guidelines for facilities; hardware and software from federal, military, national and industry regulations, codes, standards, specifications; and other documents for the system under development. The contractor shall incorporate these requirements and guidelines into the high level system specifications and design documents as appropriate.
| |
The contractor shall analyze the System Design Requirements, System/Segment Specifications (SSS), Preliminary Hardware Configuration Item Development Specification, Software Requirements Specifications (SRS), and the Interface Requirements Specifications (IRS), or equivalent documents as appropriate, to include the following sub-tasks:
| |
The contractor shall ensure that the system safety design requirements and guidelines are developed; refined; correctly and completely specified; properly translated into system hardware and software requirements and guidelines where appropriate; and implemented in the design and development of the system hardware and associated software.
| |
The contractor shall identify hazards and relate them to the specifications or documents listed above and develop design requirements to reduce the risk of those hazards.
| |
The contractor shall identify safety critical computer software components (SCCSCs) and ensure they are placed under configuration control.
| |
The contractor shall analyze the preliminary system design to identify potential hardware/ software interfaces at a gross level that may cause or contribute to potential hazards. Interfaces identified shall include control functions, monitoring functions, safety systems and functions that may have indirect impact on safety. These interfaces and the associated software shall be designated as safety critical
| |
The contractor shall perform a preliminary hazard risk assessment on the identified safety critical software functional requirements using the hazard risk matrix or software hazard criticality matrix of Appendix A or another process as mutually agreed to by the contractor and the MA.
| |
The contractor shall ensure that System Safety design requirements are properly incorporated into the operator, user, and diagnostic manuals.
| |
The contractor shall develop safety related design change recommendations and testing requirements and shall incorporate them into Preliminary Design Documents and the hardware, software and system test plans. The following sub-tasks shall be accomplished:
| |
The contractor shall develop safety-related change recommendations to the design and specification documents listed above and shall include a means of verification for each design requirement.
| |
The contractor shall develop safety related test requirements for incorporation into the test documents. Tests shall be developed for hardware, software and system integration testing.
| |
The contractor shall support the System Requirements Review (SRR), System Design Review (SDR) and Software Specification Review (SSR) from a system safety viewpoint. The contractor shall address the system safety program, analyses performed and to be performed, significant hazards identified, hazard resolutions or proposed resolutions, and means of verification.
| |
REPORT REQUIREMENTS
|
The contractor shall prepare a report that contains the results from the work task described by paragraph 203.2 above to include the following:
| |
System Description
|
This will consist of summary descriptions of the physical and functional characteristics of the system and its components. Reference to more detailed system and component descriptions, including specifications and detailed review documentation shall be supplied when such documentation is available. The capabilities, limitations and interdependence of these components shall be expressed in terms relevant to safety. The system and components shall be addressed in relation to its mission and its operational environment. System block diagrams or functional flow diagrams may be used to clarify system descriptions. Software and its role(s) shall be included in this description.
| |
A list of the applicable generic system safety design requirements and guidelines for facilities; hardware and software from federal, military, national and industry regulations, codes, standards, specifications; and other documents for the system under development which have been determined to be applicable.
| |
Data
|
This will consist of summaries of data used to determine the safety aspects of design features
| |
Hazard Analysis Results
|
This will consist of a summary or a total listing of the results of hazard analysis. Contents and formats may vary according to the individual requirements of the program. The following are the content and format requirements for Hazard Analysis Results
| |
A summary of the results
| |
Recommended action. The recommended action required to eliminate or control the hazard. Sufficient technical detail is required in order to permit the design engineers and the customer to adequately develop and assess design criteria resulting from the analysis. Include alternative designs and life cycle cost impact where appropriate.
| |
DETAILS TO BE SPECIFIED IN THE SOW
|
Imposition of Tasks 101 and 203 tailored to the developmental program
| |
Definition of acceptable level of risk within the context of the system, subsystem, or component under analysis
| |
Level of contractor support required for design reviews.
| |
Specification of the type(s) of risk assessment process.
| |