JOINT SOFTWARE SYSTEMS SAFETY HANDBOOK (SSSH) - DOD JOINT SOFTWARE SYSTEMS SAFETY (27 AUG 2010)

JOINT SOFTWARE SYSTEMS SAFETY HANDBOOK (SSSH) - DOD JOINT SOFTWARE SYSTEMS SAFETY (27 AUG 2010)., The purpose of the Handbook is to provide management and engineering guidelines to achieve a reasonable level of assurance that the software will execute within the system context with an acceptable level of safety risk. This Handbook is both a reference document and management tool for aiding managers and engineers at all levels in any Government or industrial organization. This Handbook describes how to develop and implement an effective SSS process. This process minimizes the likelihood or severity of system hazards caused by poorly specified, designed, developed, or operated software in safety-significant applications. Furthermore, technology refresh, operational upgrades, and operational risk during sustainment must be controlled or mitigated and are an integral part of the complete SSS process. The primary responsibility for management of the SSS process lies with the system safety manager or engineer in both the developer’s (supplier) and acquirer’s (customer) organizations. However, every functional discipline has a vital role and must be involved in the SSS process. The SSS tasks, techniques, and processes outlined in this Handbook can be applied to any system that uses software in critical areas. The JSSSEH highlights the need for all contributing disciplines to understand and apply qualitative analysis techniques to ensure the safety of hardware systems controlled by software. This Handbook, while extensive, is a guide and is not intended to supersede any Agency policy, standard, or guidance pertaining to system safety (e.g., Military Standard (MIL-STD)-882D) or software engineering and development (e.g., International Organization for Standardization (ISO) 12207). This Handbook is written to clarify the SSS requirements and tasks specified in Government and commercial standards and guidance documents.