Document: NUREG-0800
Document ID: 4f141c71-35ca-4353-9047-a13efe6d56b7
Document Type: srp
Title: Revision 6 - August 2016
Source: NUREG-0800
Source URL: https://www.nrc.gov/docs/ML1601/ML16019A308.pdf
Revision Date: 2023-06
Chapter: 7
Section ID: 7
CFR Part: 
CFR Title: 

Content:
software safety organization and the general system safety organization. Organization involves a description of the software safety organization. The SSP should describe the boundaries and interfaces between the software safety organization and other company organizations. It should show how the software safety activities are integrated with the system safety activities, how the software safety activities are coordinated with the development activities, and the interactions between the software safety organization and the software V&V organization. The SSP should designate a single safety officer that has clear responsibility for the safety qualities of the software being constructed. Responsibilities involve a definition of the responsibilities and authority of the software safety organization. The SSP should specify the person or group responsible for each software safety task. A designated safety officer should have clear authority for enforcing safety requirements in the software requirements specification, the design, and the implementation of the software. The safety officer should have the authority to reject the use of pre-developed software if the software cannot be shown to be adequately safe or if, in using a tool, it cannot be shown that the tool will not impact the safety of the final software system. The SSP should require that safety personnel be aware of the safety implications of hardware, software and interfaces between them. Risks involve a description of the methods to be used to reduce safety risks caused by software failures to an acceptable level. The SSP should describe the method to be used to ensure that hazards which software is expected to control are resolved in an acceptable manner. The SSP should include a requirement that a safety analysis be performed and documented on each of the principal design documents: requirements, design descriptions, and source code. Hazards, including abnormal events and conditions and malicious