Advanced Software Safety (ADVSFT)

Course Description

This course builds upon the skills learned in the Software Safety (SFT) course. It is presumed and highly recommended that the student has achieved an understanding of the importance of software safety in the planning, analyses of architecture, design, and code and the testing of automated systems. The course expands upon those skills and presents opportunities to apply them in class in diverse situations using a small unmanned aerial system (sUAS) that is also weaponized.

Objectives: To develop practicing skills in writing a Request for Proposal (RFP) for a safety critical system. To develop the practical use of a Safety Assessment Report (SAR). To develop practical skills in deriving requirements and functions leading to a Functional Hazard Analysis (FHA) and Requirements Hazard Analysis for unmanned sense and avoid. Discussion of how to compose a safety argument using results of many analyses of NASA autonomous aerial systems software that was performed using open source tools. Building confidence with your developer’s tools, looking into why and what to consider in tools, and how to review your story in your SAR. To develop these skills in a team based working environment.

Who Should Attend: System managers and engineers, system safety engineers and software engineers who have attended SFT or have a solid understanding of the basic software safety principles. Principals for Safety (PFS) or Safety Leads who must present to Review Boards. Practicing System Safety and Software Safety Engineers who are lining up a professional trajectory into autonomous systems. Future follow-on courses will cover deeper safety and security issues, autonomous systems, and machine learning models.

Course
ADVSFT 21-1
ADVSFT 22-1
Dates
24-27 May 2021
Spring 2022

Course Outline


  1. Advanced Software Safety
      • Basic Safety Overview
      • Definitions and Concepts
        Goals
      • Small Unmanned Aerial System (sUAS) overview
      • ArduCopter and NASA ICAROUS and DAIDALUS software
      • Concept of Operations (CONOPS) for safety
      • Missions and Functions
      • Payloads and Hazards
      • Best Safety Practices in Request for Proposal (RFP)
      • Performing a Functional Hazard Analyses
      • Partitioning and pitfalls
      • Declaring Software Safety Functions
      • Setting Levels of Rigor (LOR)
      • Work Responsibilities for others…
      • Plans
      • Architecture Analyses, starting with Systems of Systems (SoS)
      • Assessing code, COTS, GOTS, and what to do
      • Code Analysis
      • Software Fault Tree (SFTA)
      • Tools and their use for safety
      • What does all this mean?
      • Final Safety Assessment Report (SAR)
      • You missed your Level of Rigor (LOR) so what now?
      • What about the Review Board?
    • References
      • Joint Software Systems Safety Engineering Handbook, 2010 version
      • MIL STD 882-E
      • Joint Weapons Safety Review Guide
      • FAA Software Safety and National Airspace Requirements
      • FAA Unmanned Airworthiness 8130.34D
      • MIL-HDBK-516C, unmanned systems chapter
      • US Army small unmanned systems RFP
      • Generic Software Systems Safety Program Plan
      • Generic Safety Assessment Report (SAR)
      • NASA Langley Research and software
      • Office of Secretary of Defense Jointly with FAA, Safety guidance
      • USC Software Engineering Center

    CEU: 2.8

    Course Duration: 4.0 Days

    Tuition: $2,250 (July 2020 - June 2021); $TBD (July 2021 - June 2022)