Abstract

With rapid technological advances in airborne control systems, it has become imperative to ensure the reliability, robustness, and adaptability of airborne software since failure of these software could result in catastrophic loss of property and life. DO-333 is a supplement to the DO-178C standard, which is dedicated to guiding the application of formal methods in the review and analysis of airborne software development processes. However, DO-333 lacks theoretical guidance on how to choose appropriate formal methods and tools to achieve verification objectives at each stage of the verification process, thereby limiting their practical application. This paper is intended to illustrate the formal methods and tools available in the verification process to lay down a general guide for the formal development and verification of airborne software. We utilized the Air Data Computer (ADC) software as the research object and applied different formal methods to verify software lifecycle artifacts. This example explains how to apply formal methods in practical applications and proves the effectiveness of formal methods in the verification of airborne software.

Highlights

  • The aviation industry has seen a gradual increase in the application of software in airborne systems.The software’s failure to perform the designated task, can have undesirable consequences, such as equipment damage and risk to human life

  • This paper proposes a methodology for formal analysis and verification of airborne software based on DO-333 to provide guidance in integrating formal methods in software development and verification

  • Based on research on DO-333, this paper proposes a methodology to apply formal methods to the development and verification processes of airborne software

Read more

Summary

Introduction

The aviation industry has seen a gradual increase in the application of software in airborne systems. This paper proposes a methodology for formal analysis and verification of airborne software based on DO-333 to provide guidance in integrating formal methods in software development and verification It showcases the Air Data Computer (ADC) software to illustrate how this research’s methodology could be applied and how formal methods and tools have to be selected to verify specific objectives. The rest of the paper is organized as follows: Section 2 provides a brief introduction of airworthiness certification standards and formal methods; Section 3 describes the methodology used, providing advice on how to apply formal methods to the software development process (based on DO-333); Section 4 illustrates ADC software’s formal verification process and shows how to use formal methods to verify specific objectives; and Section 5 concludes the work and discusses further research

Airworthiness Certification Standards
Formal Methods
Methodology and Process
Design
Formal
Formal Analysis of Source Code
Formal Analysis of Executable Object Code
Static Analysis of Worst-case Execution Time and Stack Usage
Formal Verification of Air Data Computer Software
In Section
Compliance and Traceability from Low- to High-Level Requirements
Compliance from Source Code to Requirements
Static
Traceability from Executable Object Code to Source Code
Traceability to sample sample source source code: code
Consistency from sample object code to ADC software object code
Consistency from sample source source code decompiled
Assembly
Analysis of the Verification Results
Conclusion and Future Work
Full Text
Published version (Free)

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 call