Search results
Results from the WOW.Com Content Network
The earliest revisions of the Advisory Circular were brief, serving little more than to call attention to active DO-178 revisions. The Advisory Circular revisions C and D are considerably longer, giving guidance in modifying and re-using software previously approved using DO-178, DO-178A, or DO-178B (preceding revisions of the DO-178 standard).
DO-178B, Software Considerations in Airborne Systems and Equipment Certification is a guideline dealing with the safety of safety-critical software used in certain airborne systems. It was jointly developed by the safety-critical working group RTCA SC-167 of the Radio Technical Commission for Aeronautics (RTCA) and WG-12 of the European ...
Some advisory circulars are only a few pages long and do little more than reference a recommended standard; for example, AC 20-152 referencing DO-254. [8] Others, like AC 20-115 C/D, are considerably longer; in this case including guidance on how to transition from DO-178 revision B to C [ 9 ] while AC 20-152A adds several new objectives to an ...
DO-178C, Software Considerations in Airborne Systems and Equipment Certification is the primary document by which the certification authorities such as FAA, EASA and Transport Canada approve all commercial software-based aerospace systems.
The Advisory Circular 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.
CAST-15, Merging High-Level and Low-Level Requirements is a Certification Authorities Software Team (CAST) Position Paper. It is an FAA publication that "does not constitute official policy or guidance from any of the authorities", but is provided to applicants for software and hardware certification for educational and informational purposes only.
ARP4754(), Aerospace Recommended Practice (ARP) Guidelines for Development of Civil Aircraft and Systems, is a published standard from SAE International, dealing with the development processes which support certification of Aircraft systems, addressing "the complete aircraft development cycle, from systems requirements through systems verification."
Software was still considered to be assessed and controlled by other means; that is, by RTCA/DO-178A or later revision, via Advisory Circular AC 20-115A. [19] In 2002, work was done on Revision B, but it was not formally released; the result is the Rulemaking Advisory Committee-recommended revision B-Arsenal Draft (2002).