Advertisement

Worst–Case Execution Time Analysis Approach for Safety–Critical Airborne Software

  • Esteban Asensio
  • Ismael Lafoz
  • Andrew Coombes
  • Julian Navas
Part of the Lecture Notes in Computer Science book series (LNCS, volume 7896)

Abstract

The fundamental problem in building a system with hard real–time characteristics is guaranteeing that it will deterministically perform its required functionality within specified time constraints. Determining Worst–Case Execution Time (WCET) is key to predictability, that is to ensure that temporal behaviour of the system is correct and hence safe. Furthermore, it is an objective to meet by verification when development of airborne software shall be compliant with DO–178B objectives. Different approaches to WCET analysis could be taken. This paper presents the experience automating such analysis for a Fly–By–Wire system by means of a hybrid approach aiming to combine features of measurement and static analysis. Several challenges arise when integrating the analysis workflow withing the software development process, especially those regarding to instrumentation overhead. Control mechanisms need to be developed to mitigate the drawbacks and achieve realistic WCET estimations to assess temporal correctness of the system.

Keywords

Airborne Software Safety-Critical ARINC 653 IMA DO–178B/C Worst–Case Execution Time Predictability Verification Hybrid Approach 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    ARINC Specification 653: Avionics Application Software Standard Interface. Aeronautical Radio Inc. (1997)Google Scholar
  2. 2.
    Bernat, G., Colin, A., Petters, S.M.: WCET Analysis of Probabilistic Hard Real–Time Systems. In: Proc. 23rd IEEE Real–Time Systems Symposium, RTSS (2002)Google Scholar
  3. 3.
    Wilhelm, R., et al.: The Worst–Case Execution Time Problem – Overview of Methods and Survey of Tools. ACM Transactions on Embedded Computing Systems (2008)Google Scholar
  4. 4.
    RTCA DO-178B: Software Considerations in Airborne Systems and Equipment Certification. RTCA Inc. (1992)Google Scholar
  5. 5.
    RTCA DO-178C: Software Considerations in Airborne Systems and Equipment Certification. RTCA Inc. (2011)Google Scholar
  6. 6.
    RTCA DO-248B: Final Report for Clarification of DO–178B Software Considerations in Airborne Systems and Equipment Certification. RTCA Inc. (2001)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  • Esteban Asensio
    • 3
  • Ismael Lafoz
    • 1
  • Andrew Coombes
    • 2
  • Julian Navas
    • 1
  1. 1.Control Systems Software Department, Air to Air Refuelling SystemsAirbus Military - EADSGetafeSpain
  2. 2.IT CentreRapita Systems Ltd.YorkUnited Kingdom
  3. 3.On-Board Software and Validation Division PTMGMV Aerospace and DefenceTres CantosSpain

Personalised recommendations