The RTCA publishes and sells DO-178C (for airborne software development) and DO-254 (for airborne hardware development). You can purchase both of these essential documents here: www.rtca.org.
But there are also a number of publicly available (but often not-easy-to-find) documents from the FAA and EASA that need to be understood and used in conjunction with the guidance of DO-178C and DO-254. Some of the more important ones are included here for your understanding and downloading convenience:
DER Directory
The FAA DER Directory provides a list of Consultant DERs , by state and technical discipline.
AC 20-152A
This document from the FAA recognizes DO-254 and clarifies its use, adding numerous objectives related to pertinent aspects of modern hardware development. Note that this document is harmonized with the EASA document AMC 20-152A.
AMC 20-152A
This document from EASA recognizes DO-254 and clarifies its use, adding numerous objectives related to pertinent aspects of modern hardware development. Note that this document is harmonized with the FAA document AC 20-152A.
AC 20-189
This AC from the FAA, harmonizing with the equivalent AMC from EASA, provides essential terminology and processes with regards to managing Open Problem Reports (OPRs) in the context of systems (ARP 4754A), software (DO-178C) and hardware (DO-254) projects.
AMC 20-189
This document from EASA provides essential terminology and processes with regards to managing Open Problem Reports (OPRs) in the context of systems (ARP 4754A), software (DO-178C) and hardware (DO-254) projects. Note that this document is harmonized with the FAA document AC 20-189.
Order 8110.105B
This document from the FAA advises FAA personnel and their designees on how to apply DO-254. Applicants should read it to understand the discussion and interpretation that the FAA folks will use when auditing their programs. Note that it replaces Order 8110.105A.
Order 8110.49A
This document from the FAA advises FAA personnel and their designees on how to apply DO-178B and DO-178C for airborne software. Applicants should read it to understand the discussion and interpretation that the FAA folks will use when auditing their programs. Note that it replaces Order 8110.49 (Change 2).
AC 00-66
This publication covers the Selection of Cyclic Redundancy Code and Checksum Algorithms to Ensure Critical Data Integrity.
AC 00-69
This publication covers Best Practices for Airborne Software Development Assurance.
AC 00-71
This publication covers the Best Practices in the Management of Open Problem Reports, and is a companion to AC 20-189.
AC 00-72
This publication provides information in the form of ‘best practices’ for the application of DO-254.
EASA CM SWCEH-001 Issue 01 Rev 02
This document, from EASA, which focuses on DO-254/ED-80, updates the earlier certification memos and provides specific guidance material on certification aspects associated with the use of electronic hardware in airborne systems including line replaceable units, circuit board assemblies, application specific integrated circuits, programmable logic devices, microprocessors, microcontrollers, integrated circuits, etc.
CM AS-004
This document from EASA focuses on how to deal with the issue of single event effects (SEE) caused by atmospheric radiation, which is a concern to systems and hardware applicants.
AC 20-193
This AC from the FAA, harmonizing with the equivalent AMC from EASA, covers how to handle the certification aspects of multi-core processors (MCPs) contained in airborne systems and equipment, which is a concern for systems, hardware, and software developers.
AMC 20-193
This AMC from EASA (harmonized with FAA AC 20-193) covers how to handle the certification aspects of multi-core processors (MCPs) contained in airborne systems and equipment, which is a concern for systems, hardware, and software developers.
