Abstract
Airborne software is invisible and intangible, it can have a significant impact on the safety of the aircraft. However, it cannot be exhaustively tested, and can only be assured through a structured, process, activity, and objective-based approach. This paper studied the similarities and differences of software review policies of the four selected National Airworthiness Authorities (NAAs) by using a comparative approach and analysed the general certification basis of specific regulation clauses from the International Civil Aviation Organization Conventions to each contracting States’ regulations by a traceability method. Then analyzed the development processes and objectives applicable to different software levels based on RTCA/DO-178C. Identified 82 technical focus points based on each airborne software development subprocess, then created a Process Technology Coverage matrix to demonstrate the technical focuses of each process. Developed an objective-oriented top-down and bottom-up sampling strategy for the 4 software Stage of Involvement reviews by taking into account the frequency and depth of involvement. Finally, created the Technology Objective Coverage matrix, which can support the reviewers to perform the efficient risk-based SOI reviews by considering the identified technical points, thus to ensure the safety of the aircraft from the software assurance perspective.
Highlights
With the development of computer technology, more and more aircraft system functions are implemented by airborne software
Software reviews are always treated as a critical part of the system certification process, provided that it is conducted in accordance with each National Airworthiness Authorities (NAAs)’s procedures and handbooks to finding compliance with the safety-related regulations § 25.1301 and § 25.1309
Given that the airborne software review is performed by people, the different working experiences, backgrounds, and technical capabilities of the reviewers may lead to different review conclusions
Summary
With the development of computer technology, more and more aircraft system functions are implemented by airborne software. Quality should be built into the software and be reviewed by assuring the development and verification processes (CASA, 2014) (Rierson, 2013). The software is fundamentally different from the physical components installed on the aircraft. The structural components of the aircraft can be tested to ensure that there are no design and manufacturing defects, whereas the Mean Time between Failures (MTBF) and programmed replacements do not apply to software components (CASA, 2014). The software embedded in these systems has a direct impact on the safety of the aircraft and its occupants (Hilderman & Baghai, 2007). Employing software review technology can ensure that rigor has been applied during the applicant’s design commensurate with the worst-case failure condition associated with airborne software (RTCA, 2011a)
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: International Journal of Software Engineering & Applications
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
