Length: 3 Days
Print Friendly, PDF & Email

Software Safety and Risk Management Training Workshop

Advanced Computing and Software Training by Tonex

Software Safety and Risk Management Training Workshop is a 3-day hands-on workshop focusing on software safety, software hazards analysis principles and techniques, hazards identification, critical thinking, risk assessment in terms of severity, probability and control, risk mitigation.

Course Description

Software requires special attention in system planning, architecture, design, verification, validation and test.  Software Safety and Risk Management Training Workshop presents techniques and methods of developing and analyzing software and highlights managing a software safety program,  problem solving, solutions and safe designing, FMEA, FMECA, FTA, and FRACAS applicable to software, related system and hardware, embedded systems and firmware.

Software design principles will be taught to create programs that are fault tolerant and acceptably safe.  Several software hazard analyses methods will be evaluated, including Fault Tree/Soft Tree, Software Sneak Analysis and Petri Nets.

Workshop Objectives:

  • Learn the key concepts of software safety, hazards, root causes, risk assessment, risk mitigation,  and management
  • Discuss methods to discover, control and prevent software hazards
  • Recognize various software safety program administrative methods, modeling, management and documentation
  • Build and develop safe software  free of imperfections causing unsafe conditions in safety-critical systems
  • Learn about risk assessment in terms of severity, probability and control
  • Discuss risk mitigation techniques and tools, problem solving/solutions and safe designing

Who Should Attend

Software  engineers and managers, system safety engineers, embedded software engineers who are involved with developing systems that possess major software components.

Course Agenda

Introduction to Software Safety

  • Software Engineering and Software System Safety
  • Introduction to the “Systems” Approach
  • The Software Development Life Cycle
  • Principles of system safety in the design, development, use, and maintenance of software systems
  • Integration with safety-critical hardware systems in an operational environment.
  • Software Safety Directives, Documents, Policies and Regulations
  • Software Safety Requirements and Critical Functionalities
  • Software Hazards and Design Safeguards for Mitigation
  • Software Safety Critical Functions

Software Safety Program Planning 

  • Overview of Software Safety Standards
  • Joint Software Systems Safety Engineering Handbook, 2018
  • IEEE, IEC and ISO Standards
  • IEC 62304 Risk Management
  • AIAA Standards
  • IEEE 1584 Compliant Software for Hazard Analysis
  • MISRA-C and MISRA C++ Software Safety Guidelines
  • Software FMEA and FTA
  • Software Sneak Analysis and Petri Nets
  • Safety verification of Ada programs using software fault trees
  • Software Safety Program Plan
  • Preliminary Hazard List
  • Software Hazard Analysis
  • Safety Critical Functions List
  • Software Safety Checklist
  • Formal Mathematical Models
  • Software Safety Reliability/Maintenance
  • Safety Requirements Criteria Analysis
  • Safety Requirements Verification Report
  • Safety Assessment Report

Introduction to Risk Management and Software Safety

  • A Discussion of Risk in Software Safety
  • Types of Risk
  • Areas of Program Risk
  • System Safety Engineering
  • Safety Risk Management

Software Safety Implementation Process and Tasks       

  • Software Safety Process
  • Software Safety Analyses and Tools
  • Software Safety Planning
  • Hazard Identification
  • Tracking
  • Risk Assessment
  • Risk Mitigation
  • Risk Reduction
  • Failure modes, including hardware, software, human and system are addressed in the design of the software
  • Failure Mode Effect Analysis (FMEA)
  • Failure mode, effects and Criticality Analysis (FMECA)
  • Fault Tree Analysis (FTA)
  • Petri net modeling and software safety analysis
  • Software sneak condition analysis
  • Analyzing unwanted event
  • Sneak conditions and improper operation, loss of system availability, program delays, or even death or injury to personnel
  • Methodologies for embedded military applications
  • Sound software engineering practices
  • Safety issues and safety attributes
  • Software with safety critical functionality

Software Safety Engineering Process

  • Software Safety Engineering Process Charts
  • Software Safety Engineering Products and Tools
  • Software Safety Planning Management
  • Planning
  • Management
  • Software Safety Program Milestones
  • Tailoring Generic Safety-Critical Requirements
  • Preliminary Hazard Analysis Development
  • Derive System Safety-Critical Software Requirements
  • Preliminary Software Design, Subsystem Hazard Analysis
  • Module Safety-Criticality Analysis
  • Program Structure Analysis
  • Traceability Analysis
  • Detailed Software Design, Subsystem Hazard Analysis

Software Safety Engineering Process Cross Lifecycle Activities

  • Software Requirements Hazard Analysis
  • Top-level Design Hazard Analysis
  • Preliminary Design Review (PDR)
  • Detailed Design Hazard Analysis
  • Critical Design Review (CDR)
  • Code-level Software Hazard Analysis
  • Software Safety Testing
  • Software/User Interface Analysis
  • Software Change Hazard Analysis
  • Test & Evaluation Strategy (TES)
  • Software Safety Plan (SSP)

Software Hazard Analysis Process

  • Software Safety Testing & Risk Assessment
  • Software Safety Test Planning
  • Software Safety Test Analysis
  • Software Standards and Criteria Assessment
  • Software Safety Residual Risk Assessment
  • Safety Assessment Report
  • Safety Assessment
  • Planning and Management
  • Task Implementation
  • Software Risk Assessment and Acceptance

Types of Software Safety Requirements and Procedures

  • Hardware and Human Interface Requirements
  • Interface Requirements
  • Operations and Support Requirements
  • Safety/Warning Device Requirements
  • Protective Equipment Requirements
  • Procedures and Training Requirements
  • Determination of Safety Critical Computing System Functions
  • Design and Development Process Requirements And Guidelines
  • Configuration Control
  • Software Quality Assurance Program
  • Software Design Verification and Validation
  • System Design Requirements and Guidelines
  • Designed Safe States

Software Safety Requirements Verification   

  • Hierarchy Tree Example
  • Detailed Software Design Analysis
  • Verification Methods
  • Example of a Data Flow Diagram
  • Flow Chart Examples
  • System Hazard Analysis
  • Example of a System Hazard Analysis Interface Analysis
  • Documentation of Interface Hazards and Safety Requirements
  • Documenting Evidence of Hazard Mitigation
  • Software Safety Test Planning
  • Software Safety Testing and Analysis
  • Software Requirements Verification
  • Residual Safety Risk Assessment
  • SSHA & SHA Hazard Record Example
  • Hazard Requirement Verification Document Example
  • Software Safety SOW Paragraphs
  • Hazard Severity
  • Hazard Probability
  • Table HRI Matrix
  • Process Tradeoff Analyses
  • Example of a Software Safety Requirements Verification Matrix
  • Safety critical Function Matrix

Software Planning Interfaces 

  • Engineering Management
  • Design Engineering
  • Systems Engineering
  • Software System Safety Handbook
  • Software Development
  • Integrated Logistics Support
  • Other Engineering Support

Meetings and Reviews 

  • Program Management Reviews
  • Integrated Product Team Meetings
  • System Requirements Reviews
  • System/Subsystem Design Reviews
  • Preliminary Design Review
  • Critical Design Review
  • Test Readiness Review
  • Functional Configuration Audit
  • Physical Configuration Audit
  • Resource Allocation
  • Safety Personnel
  • Safety Schedules and Milestones
  • Safety Tools and Training
  • Required Hardware and Software

Software Safety Program Plans 

  • Risk Management Plan
  • Quality Assurance Plan
  • Reliability Engineering Plan
  • Software Development Plan
  • Systems Engineering Management Plan
  • Test and Evaluation Master Plan
  • Software Test Plan
  • Software Installation Plan
  • Software Transition Plan

Workshop and Case Studies

  • Software Safety Activities
  • Tasks and Methods
  • Requirements Hazard Analysis
  • Architectural Design Hazard Analysis
  • Detailed Design Hazard Analysis
  • Code Hazard Analysis
  • System Safety Analysis Techniques
  • Working with Software Safety Analysis Techniques
  • Software FMEA/FMECA
  • Software HAZOP
  • Software FTA
  • Comparison of Software Safety Analysis Methods
  • Sample System Safety Requirements
  • Sample Software Safety Requirements
  • Software and System Hazard Analysis (SHA)
  • System hazard analysis (SHA)
  • Sample Software Requirements Hazard Analysis
  • Sample Software FMEA and FMECA Analysis
  • Sample Software Fault Tree Analysis (FTA)
  • Software Sneak Analysis
  • MISRA-C and MISRA-C++ Overview

Case Studies

  • Software safety and hazard analysis case studies are presented regarding catastrophic situations that resulted from software faults that could have been avoided.
  • Specific techniques of risk analysis, hazard analysis, fault tolerance, and safety tradeoffs within the software engineering paradigm applicable to embedded systems, medical devices and instruments
  • Software hazard analysis applicable to medical devices
  • Medical device software development lifecycle methodologies tools and risk management
  • Medical device software validation and traceability

Request More Information

Please enter contact information followed by your questions, comments and/or request(s):
  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.