Certification Authorities Software Team

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[1][2] of Certification Authorities activities in part though clarification and improvement of the guidance provided by DO-178() and DO-254().

Certification Authorities Software Team
AbbreviationCAST
Formation1990
ProductsCAST Position Papers
FieldsCertification of airborne software and hardware
No meetings since 2016.

Activities

Since 1982, RTCA publication DO-178 has provided guidance on certification aspects of safety-critical software use in civil aircraft. In 1985, the first revision DO-178A was issued. The CAST organization first met November 1990 to develop consistent international certification authority input to the drafting of the next revision, DO-178B, which was released in 1992. In 2003, the organization expanded its scope to address the published certification guidance for airborne electronic hardware provided in the RTCA publication DO-254 released in 2000.[1]

With application of DO-178B, it was discovered that many projects were not complying with DO-178B, but there was also wide variations in how various certification authorities conducted project assessments. In response, the CAST developed a standard software compliance assessment approach. In a manner similar to standard staged engineering design review practices (e.g., 10%-50%-90%-100% Complete), this introduced four standard milestones in a software development project where an FAA authority or representative would assess the applicant's progress towards compliance. A goal was to detect issues in time to for the applicant to make adjustments to maximize successful accomplishment of all certification objectives. The FAA further developed this approach in the "Mega" FAA Order 8110.49 Chapter 2, defining the four Stages of Involvement (SOI) Audits as Planning, Development, Verification (Test), and Final.[3]

From 1998 on, the CAST provided informational recommendations in the form of a series of position papers that were neither policy nor guidance documents.[4] These position papers were among the inputs to the joint RTCA/EUROCAE committee that developed DO-178C, DO-278A, DO-248C, and DO-330, and the technology supplements to these publications (DO-331, DO-332, and DO-333).[1]

The model for international certification authority harmonization has changed since CAST's inception.[5] Certification Management Team Collaboration Strategy now emphasizes direct collaboration with industry on technical topics.[6] CAST has not met since October 2016 and the FAA has removed links to past CAST position papers from its website; Position Papers 1-26 were archived in 2015 and this archive was removed in 2017. All but one remaining position papers were later removed from the website and the link to the remaining CAST-32A will be removed after publication of AC 20-193.[5]

Even though these legacy items have been removed, not all information they contain has been included in replacement publications, so, they remain a source of insight into present guidance.

Position Papers

Series Subject Year
CAST-1Guidance for Assessing the Software Aspects of Product Service History of Airborne Systems and Equipment1998
CAST-2Guidelines for Assessing Software Partitioning/Protection Schemes2001
CAST-3Guidelines for Assuring the Software Aspects of Certification When Replacing Obsolete Electronic Parts Used in Airborne Systems and Equipment1999
CAST-4Object-Oriented Technology (OOT) in Civil Aviation Projects: Certification Concerns
Status: Cancelled
2000
CAST-5Guidelines for Proposing Alternate Means of Compliance to DO-178B2000
CAST-6Rationale for Accepting Masking MC/DC in Certification Projects2001
CAST-7Open Problem Report (OPR) Management for Certification2001
CAST-8Use of the C++ Programming Language2002
CAST-9Considerations for Evaluating Safety Engineering Approaches to Software Assurance2002
CAST-10What is a "Decision" in Application of Modified Condition/Decision Coverage (MC/DC) and Decision Coverage (DC)?2002
CAST-11Criteria for Assuring Complete Software Verification Processes
Status: Superseded by CAST 11A
2002
CAST-11ACriteria for Assuring Continuous and Complete Software Verification Processes2007
CAST-12Guidelines for Approving Source Code to Object Code Traceability2002
CAST-13Automatic Code Generation Tools Development Assurance2002
CAST-14Use of a Level D Commercial Off-the-Shelf Operating System in Systems with Other Software of Levels C and/or D
Status: Cancelled
2002
CAST-15Merging High-Level and Low-Level Requirements2003
CAST-16Databus Evaluation Criteria2003
CAST-17Structural Coverage of Object Code2003
CAST-18Reverse Engineering in Certification Projects2003
CAST-19Clarification of Structural Coverage Analyses of Data Coupling and Control Coupling2004
CAST-20Addressing Cache in Airborne Systems and Equipment2003
CAST-21Compiler-Supplied Libraries2004
CAST-22Reuse of Software Tool Qualification Data Across Company Boundaries (Applying the Reusable Software Component Concept to Tools)2005
CAST-23Software Part Numbering2005
CAST-24Reliance on Development Assurance Alone when Performing a Complex and Full-Time Critical Function2006
CAST-25Considerations When Using a Qualifiable Development Environment (QDE) in Certification Projects2005
CAST-26Verification Independence2006
CAST-27Clarifications on the use of RTCA Document DO-254 and EUROCAE Document ED-80, Design Assurance Guidance for Airborne Electronic Hardware2006
CAST-28Frequently Asked Questions (FAQs) on the use of RTCA Document DO-254 and EUROCAE Document ED-80, Design Assurance Guidance for Airborne Electronic Hardware2006
CAST-29Use of COTS Graphical Processors (CGP) in Airborne Display Systems2007
CAST-30Simple Electronic Hardware and RTCA Document DO-254 and EUROCAE Document ED-80, Design Assurance Guidance for Airborne Electronic Hardware2007
CAST-31Technical Clarifications Identified for RTCA DO-254 / EUROCAE ED-802012
CAST-32Multi-core Processors
Status: Superseded by CAST 32A
2014
CAST-32AMulti-core Processors2016
CAST-33Compliance to RTCA DO-254/ EUROCAE ED-80, "Design Assurance Guidance for Airborne Electronic Hardware", for COTS Intellectual Property Used in Programmable Logic Devices and Application Specific Integrated Circuits2014

References

  1. Leanna Rierson (19 December 2017) [7 January 2013]. Developing Safety-Critical Software: A Practical Guide for Aviation Software and DO-178C Compliance. CRC Press. p. 52-55. ISBN 9781351834056. Retrieved 2022-03-03.
  2. Cary Spitzer; Uma Ferrell; Thomas Ferrell, eds. (2015). Digital Avionics Handbook, Avionics, Development and Implementation (3rd ed.). Boca Raton, FL: CRC Press. p. 14-18. ISBN 978-1138076983. CAST was formed to promote harmonization of certification and regulatory positions on software and complex hardware aspects of safety.
  3. Rierson. p. 289-313.
  4. Cary Spitzer; Uma Ferrell; Thomas Ferrell, eds. (2015). Digital Avionics Handbook, Avionics, Development and Implementation (3rd ed.). Boca Raton, FL: CRC Press. p. 14-18. ISBN 978-1138076983. CAST position papers are for education and information purposes and do not constitute official [FAA] policy or guidance.
  5. "Certification Authorities Software Team (CAST)". Federal Aviation Administration. Retrieved 2021-10-29.
  6. "ANAC-EASA-FAA-TCCA Certification Management Team Collaboration Strategy" (PDF). Federal Aviation Administration. 2016. Retrieved 2021-10-29. The CMT should actively engage with industry and promote common solutions and approaches to aircraft certification within the international community.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.