Lessons Learned in a Complex Software Safety Program

Nathaniel Ozarin

doi:10.56094/jss.v56i1.30

Authors

Nathaniel Ozarin

DOI:

https://doi.org/10.56094/jss.v56i1.30

Keywords:

software safety, MIL-STD-882, AOP-52, lessons learned

Abstract

Development of a system software safety program was required as part of an effort to secure government safety certification of a complex and intrinsically hazardous software-controlled system under development by several contributing companies. The author was part of a team of software safety support engineers reporting to one of the contributing companies. This paper summarizes some of the highlights of the lessons learned during development of this program.

Author Biography

Nathaniel Ozarin

Nat Ozarin has been a senior engineering consultant for over thirteen years at The Omnicon Group Inc. His background includes hardware engineering, software engineering, systems engineering, programming, and reliability engineering. He received a BSEE from Lehigh University, an MSEE from Polytechnic Institute of New York, and an MBA from Long Island University. He was named 2009 Reliability Engineer of the Year by the IEEE Reliability Society.

References

MIL-STD-882E. "Department Of Defense Standard Practice, System Safety," 2012.

Joint Software Systems Safety Engineering Handbook (JSSSEH), Naval Ordnance Safety and Security Activity, In-dian Head, MD, 2010.

Guidance on Software Safety Design and Assessment of Munition-Related Computing Systems (AOP-52), North Atlantic Treaty Organization, 2009.

SAE ARP5580. "Recommended Failure Modes and Effects Analysis (FMEA) Practices for Non-Automobile Applications," Society of Automotive Engineers, Inc. 2000.

Ozarin, N. W. "Failure Modes and Effects Analysis during Design of Computer Software," Proceedings of the Annual Reliability and Maintainability Symposium, 2004.

Ozarin, N. W. "Applying Software Failure Modes and Effects Analysis to Interfaces," Proc. Ann. Reliability & Main-tainability Symposium, 2009. https://doi.org/10.1109/RAMS.2009.4914732 DOI: https://doi.org/10.1109/RAMS.2009.4914732

Travis, Gregory. "How the Boeing 737 Max Disaster Looks to a Software Developer," IEEE Spectrum, April 18, 2019.

Beatty, Sean M. "Improving Software Safety: Finding the Defects that Testing and Inspection Miss," Proceedings of the 22nd International System Safety Conference, 2004.

DO-178B, "Software Considerations in Airborne Systems and Equipment Certification," RTCA, 2013.