DO-248

Last updated
Supporting Information for DO-178C and DO-278A
AbbreviationDO-248C
Latest versionDecember 13, 2011 (2011-12-13)
Organization RTCA SC-205
DomainAviation

DO-248C, Supporting Information for DO-178C and DO-278A, published by RTCA, Incorporated, is a collection of Frequently Asked Questions and Discussion Papers addressing applications of DO-178C and DO-278A [1] in the safety assurance of software for aircraft and software for CNS/ATM systems, respectively. Like DO-178C and DO-278A, it is a joint RTCA undertaking with EUROCAE and the document is also published as ED-94C, Supporting Information for ED-12C and ED-109A. [2] The publication does not provide any guidance additional to DO-178C or DO-278A; rather, it only provides clarification for the guidance established in those standards. [3] The present revision is also expanded to include the "Rationale for DO-178C/DO-278A" section to document items that were considered when developing DO-178B and then DO-178C, DO-278A, and DO-330, as well as the supplements that accompany those publications (DO-331, DO-332, DO-333). [1]

Corresponding with the releases of DO-178C and DO-278A, the present revision, DO-248C, is an update to the previous revision DO-248B, Report for Clarification of DO-178B "Software Considerations in Airborne Systems and Equipment Certification". While new FAQs and discussion papers have been added, most of the FAQs and discussion papers of DO-248C are carried over from DO-248B. Some of these items have been marked as deleted or updated as the subjects were addressed by the releases of DO-178C, DO-330, supplements, or other publications. An errata section is not included as the release of DO-178C addressed the errata of DO-178B and no DO-178C errata have been published. [1]

Initially, this publication was an annual clarification report, DO-248B (2001) was preceded by DO-248A (2000) and DO-248 (1999). [4]

Outline of contents

DO-248C contains the following:

  1. Verification Tool Selection Considerations
  2. The Relationship of DO-178B/ED-12B to the Code of Federal Regulations (CFRs) and Joint Aviation Requirements (JARs)
  3. The Differences Between DO-178A and DO-178B Guidance for Meeting the Objective of Structural Coverage
  4. Service History Use—Rationale for DO-178C
  5. Application of Potential Alternative Methods Compliance for Previously Developed Software (PDS)
  6. Transition Criteria
  7. Definition of Commonly Used Verification Terms
  8. Structural Coverage and Safety Objectives
  9. Certification With Known Software Problems
  10. Considerations Addressed When Deciding to Use Previously Developed Software (PDS)
  11. Qualification of a Tool Using Service History (Removed, see DO-330)
  12. Object Code to Source Code Traceability Issues
  13. Definitions of Statement Coverage, Decision Coverage, and Modified Condition/Decision Coverage (MC/DC)
  14. Partitioning Aspects in DO-178C/DO-278A
  15. Relationship Between Regression Testing and Hardware Changes
  16. Cache Management
  17. Usage of Floating-Point Arithmetic
  18. Service Experience Rationale for DO-278A
  19. Independence in DO-178C/DO-278A
  20. Parameter Data Items and Adaptation Data Items
  21. Clarification on Single Event Upset (SEU) as It Relates to Software

Related Research Articles

In computer science, code coverage is a percentage measure of the degree to which the source code of a program is executed when a particular test suite is run. A program with high test coverage has more of its source code executed during testing, which suggests it has a lower chance of containing undetected software bugs compared to a program with low test coverage. Many different metrics can be used to calculate test coverage. Some of the most basic are the percentage of program subroutines and the percentage of program statements called during execution of the test suite.

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 Organisation for Civil Aviation Equipment (EUROCAE). RTCA published the document as RTCA/DO-178B, while EUROCAE published the document as ED-12B. Although technically a guideline, it was a de facto standard for developing avionics software systems until it was replaced in 2012 by DO-178C.

A hazard analysis is used as the first step in a process used to assess risk. The result of a hazard analysis is the identification of different types of hazards. A hazard is a potential condition and exists or not. It may, in single existence or in combination with other hazards and conditions, become an actual Functional Failure or Accident (Mishap). The way this exactly happens in one particular sequence is called a scenario. This scenario has a probability of occurrence. Often a system has many potential failure scenarios. It also is assigned a classification, based on the worst case severity of the end condition. Risk is the combination of probability and severity. Preliminary risk levels can be provided in the hazard analysis. The validation, more precise prediction (verification) and acceptance of risk is determined in the risk assessment (analysis). The main goal of both is to provide the best selection of means of controlling or eliminating the risk. The term is used in several engineering specialties, including avionics, chemical process safety, safety engineering, reliability engineering and food safety.

<span class="mw-page-title-main">ARP4754</span>

ARP4754, Aerospace Recommended Practice (ARP) ARP4754A, is a guideline 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." Revision A was released in December 2010. It was recognized by the FAA in AC 20-174 published November 2011. EUROCAE jointly issues the document as ED–79.

RTCA DO-254 / EUROCAE ED-80, Design Assurance Guidance for Airborne Electronic Hardware is a document providing guidance for the development of airborne electronic hardware, published by RTCA, Incorporated and EUROCAE. The DO-254/ED-80 standard was formally recognized by the FAA in 2005 via AC 20-152 as a means of compliance for the design assurance of electronic hardware in airborne systems. The guidance in this document is applicable, but not limited, to such electronic hardware items as

<span class="mw-page-title-main">MIL-STD-810</span> Military standard

MIL-STD-810, U S Department of Defense Test Method Standard, Environmental Engineering Considerations and Laboratory Tests, is a United States Military Standard that emphasizes tailoring an equipment's environmental design and test limits to the conditions that it will experience throughout its service life, and establishing chamber test methods that replicate the effects of environments on the equipment rather than imitating the environments themselves. Although prepared specifically for U.S. military applications, the standard is often applied for commercial products as well.

Integrated modular avionics (IMA) are real-time computer network airborne systems. This network consists of a number of computing modules capable of supporting numerous applications of differing criticality levels.

Modified condition/decision coverage (MC/DC) is a code coverage criterion used in software testing.

<span class="mw-page-title-main">Liverpool Data Research Associates</span> Software companies of the United Kingdom

Liverpool Data Research Associates (LDRA) is a provider of software analysis, and test and requirements traceability tools for the Public and Private sectors and a pioneer in static and dynamic software analysis.

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 document is published by RTCA, Incorporated, in a joint effort with EUROCAE, and replaces DO-178B. The new document is called DO-178C/ED-12C and was completed in November 2011 and approved by the RTCA in December 2011. It became available for sale and use in January 2012.

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, and any other rules within the 14 CFR Aeronautics and Space Title. They define acceptable means, but not the only means, of accomplishing or showing compliance with airworthiness regulations. Generally informative in nature, Advisory Circulars are neither binding nor regulatory; yet some have the effect of de facto standards or regulations.

<span class="mw-page-title-main">AC 25.1309-1</span> American aviation regulatory document

AC 25.1309–1 is an FAA Advisory Circular (AC) that identifies acceptable means for showing compliance with the airworthiness requirements of § 25.1309 of the Federal Aviation Regulations. Revision A was releases in 1988. 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). The Arsenal Draft is "considered to exist as a relatively mature draft". The FAA and EASA have subsequently accepted proposals by type certificate applicants to use the Arsenal Draft on development programs.

Cantata++, or simply Cantata in newer versions, is a commercial computer program for dynamic testing, specifically unit testing and integration testing, and code coverage at run time of C and C++ programs. It is developed and sold by QA Systems, and was formerly a product of IPL Information Processing Ltd.

<span class="mw-page-title-main">AC 20-115</span>

The Advisory Circular AC 20-115( ), Airborne Software Development Assurance Using EUROCAE ED-12( ) and RTCA DO-178( ), identifies the RTCA published standard DO-178 as defining a suitable means for demonstrating compliance for the use of software within aircraft systems. The present revision D of the circular identifies ED-12/DO-178 Revision C as the active revision of that standard and particularly acknowledges the synchronization of ED-12 and DO-178 at that revision.

<span class="mw-page-title-main">FAA Order 8110.105</span> American regulatory order

FAA Order 8110.105A, Simple and Complex Electronic Hardware Approval Guidance, supplements RTCA DO-254 by explaining how FAA aircraft certification staff can use that document "when working on certification projects" and is recommended as a reference for developers applying for certification under DO-254. A particular focus is on clarification of the application of DO-254 guidance to "simple" custom micro-coded components as opposed to the more rigorous assurance expected of complex custom micro-coded components. Micro-coded devices are typically presumed to be complex components that cannot be verified through testing alone; however, some applicants have proposed their specific micro-coded device applications as simple components.

DO-297, Integrated Modular Avionics (IMA) Development Guidance and Certification Considerations is one of the primary document by which certification authorities such as the FAA and EASA approve Integrated Modular Avionics (IMA) systems for flight. The FAA Advisory Circular (AC) 20-170 refers to DO-297.

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. The AC does not state FAA guidance, but rather provides information in the form of complementary "best practices".

<span class="mw-page-title-main">CAST-31</span> Certified Authorities Software Team position paper

CAST-31, Technical Clarifications Identified for RTCA DO-254 / EUROCAE ED-80 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 for educational and informational purposes only for applicants for software and hardware certification.

The Certification Authorities Software Team (CAST) is an international group of aviation certification and regulatory authority representatives. The organization of has been a means of coordination among representatives from certification authorities in North and South America, Europe, and Asia, in particular, the FAA and EASA. The focus of the organization has been harmonization of Certification Authorities activities in part though clarification and improvement of the guidance provided by DO-178 and DO-254.

<span class="mw-page-title-main">CAST-15</span>

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.

References

  1. 1 2 3 Leanna Rierson. Developing Safety-Critical Software: A Practical Guide for Aviation Software and DO-178C Compliance. p. 70-71. ISBN   978-1-4398-1368-3.
  2. AC 20-115D, FAA, Office AIR-134, 2017, page 2.
  3. RTCA DO-178C, page A-2.
  4. Rierson, page 52-53.