Joint Software Systems Safety Handbook

Posted on 25-04-2021 by admin

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. Joint Electronic Library - Joint Publications, training manuals, joint doctrine and multinational publications; Joint Technical Data Integration - Single sign-on portal for worldwide access to authoritative technical information for the Utility Helicopter Project Office, AH-64 A/D PM and the 128th Aviation Brigade. Joint Services Software System Safety Handbook Our expertise in software safety (sometimes referred to as software system safety) dates back to. However, the Joint Services Software System Safety. DoD Joint Software Systems Safety Engineering Handbook.engineers implemented SS in aerospace. Techniques (e.g., Joint Services Software Systems. Software: USAF Weapon System Software Management Guide: Aug 08: MIL-STD-498 “Application and Reference Guidebook” Jan 96: Joint Software System Safety Engineering Handbook: Aug 10: Guidebook for Acquisition of Naval Software Intensive Systems: Sep 08: Space: Air Force Manual (AFM) 99-113 “Space Systems Test and Evaluation Process” May 96. SOFTWARE SYSTEM SAFETY HANDBOOK Joint Software System Safety Committee A Technical & Managerial Team Approach December 1999. Under the direction and guidance of the Joint Services Software Safety Committee of the Joint Services System Safety Panel and the Electronic Industries Association, G-48 Committee AUTHORS. C.3.3 Systems.

Software Safety Standards
Joint Software Systems Safety Engineering Handbook

System Safety. Department of Defense (DoD) Manual 5000.69, Joint Services Weapon Safety Review (JSWSR) Process July 30, 2014; Preparation Guide for the Joint Services Weapon Safety Review Safety Data Package, Version 1.1 June 2014; Joint Software Systems Safety Engineering Handbook, Version 1.0 August 27, 2010. JOINT SERVICES-SOFTWARE SAFETY AUTHORIES Joint Software System Safety Engineering Handbook and MIL-STD 882E Implementation Process and Tasks Status and Tutorial Presented at International System Safety Conference San Diego, CA Don Hanline –AMCOM Safety Office Jay Ball –NAVAIR Steve Mattern –Bastion Technologies, Inc.

(Redirected from Software System Safety)

In software engineering, software system safety optimizes system safety in the design, development, use, and maintenance of software systems and their integration with safety-critical hardware systems in an operational environment.

Overview[edit]

Software system safety is a subset of system safety and system engineering and is synonymous with the software engineering aspects of Functional Safety. As part of the total safety and software development program, software cannot be allowed to function independently of the total effort. Both simple and highly integrated multiple systems are experiencing an extraordinary growth in the use of computers and software to monitor and/or control safety-critical subsystems or functions. A software specification error, design flaw, or the lack of generic safety-critical requirements can contribute to or cause a system failure or erroneous human decision. To achieve an acceptable level of safety for software used in critical applications, software system safety engineering must be given primary emphasis early in the requirements definition and system conceptual design process. Safety-critical software must then receive continuous management emphasis and engineering analysis throughout the development and operational lifecycles of the system.

Functional Hazard Analyses (FHA) are often conducted early on - in parallel with or as part of system engineering Functional Analyses - to determine the safety-critical functions (SCF) of the systems for further analyses and verification. Software system safety is directly related to the more critical design aspects and safety attributes in software and system functionality, whereas software quality attributes are inherently different and require standard scrutiny and development rigor. Development Assurance levels (DAL) and associated Level of Rigor (LOR) is a graded approach to software quality and software design assurance as a pre-requisite that a suitable software process is followed for confidence. LOR concepts and standards such as DO-178C are NOT a substitute for software safety. Software safety per IEEE STD-1228 and MIL-STD-882E focuses on ensuring explicit safety requirements are met and verified using functional approaches from a safety requirements analysis and test perspective. Software safety hazard analysis required for more complex systems where software is controlling critical functions generally are in the following sequential categories and are conducted in phases as part of the system safety or safety engineering process: software safety requirements analysis; software safety design analyses (top level, detailed design and code level); software safety test analysis, and software safety change analysis. Once these 'functional' software safety analyses are completed the software engineering team will know where to place safety emphasis and what functional threads, functional paths, domains and boundaries to focus on when designing in software safety attributes to ensure correct functionality and to detect malfunctions, failures, faults and to implement a host of mitigation strategies to control hazards. Software security and various software protection technologies are similar to software safety attributes in the design to mitigate various types of threats vulnerability and risks. Deterministic software is sought in the design by verifying correct and predictable behavior at the system level.

Goals[edit]

Functional safety is achieved through engineering development to ensure correct execution and behavior of software functions as intended
Safety consistent with mission requirements, is designed into the software in a timely, cost effective manner.
On complex systems involving many interactions safety-critical functionality should be identified and thoroughly analyzed before deriving hazards and design safeguards for mitigations.
Safety-critical functions lists and preliminary hazards lists should be determined proactively and influence the requirements that will be implemented in software.
Contributing factors and root causes of faults and resultant hazards associated with the system and its software are identified, evaluated and eliminated or the risk reduced to an acceptable level, throughout the lifecycle.
Reliance on administrative procedures for hazard control is minimized.
The number and complexity of safety critical interfaces is minimized.
The number and complexity of safety critical computer software components is minimized.
Sound human engineering principles are applied to the design of the software-user interface to minimize the probability of human error.
Failure modes, including hardware, software, human and system are addressed in the design of the software.
Sound software engineering practices and documentation are used in the development of the software.
Safety issues and safety attributes are addressed as part of the software testing effort at all levels.
Software is designed for human machine interface, ease of maintenance and modification or enhancement
Software with safety-critical functionality must be thoroughly verified with objective analysis and preferably test evidence that all safety requirements have been met per established criteria.

This article incorporates public domain material from the United States Government document Joint Software System Safety CommitteeSOFTWARE SYSTEM SAFETY HANDBOOK A Technical & Managerial Team Approach This document was originally obtained from the web side 'http://www.monmouth.army.mil/cecom/safety/sys_service/^{[permanent dead link]}'. which is now a dead link since this base closed in 2011. A PDF of the document is available at http://www.system-safety.org/Documents/Software_System_Safety_Handbook.pdf 2.15MB. In addition, an updated version can be obtained from: https://www.acq.osd.mil/se/docs/Joint-SW-Systems-Safety-Engineering-Handbook.pdf 4.6MB.

Uinin