DO-178

Edaway DO-254 Training covers all aspects of Hardware Considerations in Airborne Systems and Equipment Certification, introducing the primary standard for commercial avionics hardware development, supported by FAA and EASA.

Training Overview

This course on DO-178C provides a thorough and practical understanding of this essential standard for aviation software safety and reliability. Aimed at software engineers, quality managers, and project managers, the course explores DO-178C requirements, software integrity levels, development and verification processes, and compliance management. Through theoretical lectures, practical examples and interactive discussions, participants will learn how to document and demonstrate software compliance with the standards required for aviation certification, equipping them to meet the challenges of the industry.


Who should attend?

This training course is designed to support the requirements of software development teams, verification and validation teams, and anyone looking to improve the standard of their C language software code. It is especially applicable for those aiming to achieve safety- and security-critical certifications for their projects across the industrial sectors.

  • Software Team Leaders
  • Software Quality Managers
  • Software Engineers
  • System Engineers
  • Test Engineers

Agenda

Day 1

0 – Course Introduction
1 – Introduction to DO178-C
2 – Introduction to ARP4761
3 – Introduction to ARP4754
4 – Safety and Functional Safety Concept
5 – Risk and Hazard Concepts
6 – Hazard Analysis and Risk Assessment
7 – Design Assurance Level
8 – DO178-C Guideline Objectives rev 4
9 – DO178 vs DO254
11 – CAST papers
12 – Tools for Obtaining DO178C Certification
13 – Tool Assessment Qualification

Day 2

1 – Software Life Cycle and Software Life Cycle Data
2 – Software Plans and Plan for Software Aspect of Certification
3 – Software Development Process Data
4 – Software Verification Process
5 – Software Configuration Management and Configuration Index 1
6 – Software Accomplishment Summary
7 – System Requirements
8 – Software Requirements
9 – Derived Requirements
10 – Requirement flow down
11 – Requirements Traceability

Day 3

1 – Requirement traceability using tools
2 – Classical Project Approach
3 – DO178 Project Approach
4 – Formal Verification – Static Analysis rev1
5 – Dynamic Software Verification
6 – Unit Test and Physical Testing on Target
7 – Use of Previously Developed Software Modules
8 – Architectural Considerations
9 – SOI Audits
10 – Appendix A and Appendix B

REQUEST INFO