Class description
Software is not safe or unsafe, but it can contribute to system hazards and therefore represents an important component of a thorough and effective System Safety program. The most important consequence of a system containing software is that system engineering and system safety as practiced in the past are no longer adequate. Software allows enormously complex systems to be built that overwhelm the traditional system safety techniques and require changes throughout development and operations. This class will cover the changes in and additions to traditional system safety programs introduced by the use of software.
Topics Covered:
What is different about software and why it requires special treatment.
The impact of software the system safety program and on MIL-STD-882 tasks
The role of software in hazards and accidents
Generating software safety requirements
The impact of software on traditional hazard analysis methods
A new hazard analysis method (STPA) that includes software
Software requirements analysis
Principles of system and software design for safety
Documentation to manage a software/system safety program
Human-computer interaction and safety
Case studies and lessons learned will be covered throughout
Length of class: 4 days