The
Advisory Circular __NOTOC__
Advisory circular (AC) refers to a type of publication offered by the Federal Aviation Administration (FAA) to provide guidance for compliance with airworthiness regulations, pilot certification, operational standards, training standards, ...
AC 00-69, ''Best Practices for Airborne Software Development Assurance Using EUROCAE ED-12( ) and RTCA DO-178( )'', initially issued in 2017, supports application of the active revisions of
ED-12C/DO-178C and
AC 20-115
The Advisory Circular __NOTOC__
Advisory circular (AC) refers to a type of publication offered by the Federal Aviation Administration (FAA) to provide guidance for compliance with airworthiness regulations, pilot certification, operational standa ...
. The AC does not state
FAA guidance, but rather provides information in the form of complementary "
best practices
A best practice is a method or technique that has been generally accepted as superior to other known alternatives because it often produces results that are superior to those achieved by other means or because it has become a standard way of doing ...
".
* Notably, the guidance of
FAA Order 8110.49 regarding "Software
Change Impact Analysis
Change impact analysis (IA) or impact analysis is the analysis of changes within a deployed product or application and their potential consequences.
Change impact analysis is defined by Bohnner and Arnold as "identifying the potential consequenc ...
" was removed in Rev A of that notice in 2018. The best practices that AC 00-69 now describes for Software Change Impact Analysis are much reduced and less prescriptive than what was removed from 8110.49.
* This AC clarifies that
Data Coupling Analysis and
Control Coupling Analysis are distinct activities and that ''both'' are required for satisfying objective A-7 (8) of ED-12C/DO-178C and ED-12B/DO-178B, adding that data and control coupling analyses rely upon
detailed design specification of interfaces and dependencies between components.
* The AC also recommends that error handling (how the software avoids, detects, and handles
runtime error) should be defined in explicit, reviewed design specifications rather than implemented ''ad hoc'' in the source code.
References
{{reflist
External links
AC 00-69, ''Best Practices for Airborne Software Development Assurance Using EUROCAE ED-12( ) and RTCA DO-178( )''
Avionics
Safety
Software requirements
RTCA standards
Computer standards