With flight software becoming ever more complex, assuming that it behaves perfectly is no longer realistic. At the same time Verification and Validation (V&V) is consuming up to 50% of flight software development costs. The adaptation of fault protection concepts to flight software is attractive, particularly in the context of the fault containment and health management capabilities of ARINC 653. We propose a proactive, unified, model-based approach in which the behavior of the software is monitored against a model of its expected behavior. We describe how that may be incorporated into the ARINC 653 health management architecture. We describe software capabilities that facilitate software fault protection. These capabilities include enhancements to the ARINC 653 application executive, tools for software instrumentation, and a temporal logic runtime monitoring framework for high-level specification and monitoring. We analyze the aspects of the software that should be modeled and the types of failure responses. We show how these concepts may be applied to the Mission Data System (MDS) flight software framework.


    Access

    Check access

    Check availability in my library

    Order at Subito €


    Export, share and cite



    Title :

    Software Fault Protection with ARINC 653


    Contributors:


    Publication date :

    2007-03-01


    Size :

    14912813 byte





    Type of media :

    Conference paper


    Type of material :

    Electronic Resource


    Language :

    English



    `ARINC 653 - achieving software re-use'

    Cook, A. / Hunt, K. J. R. / ERA Technology | British Library Conference Proceedings | 1996


    ARINC 653-achieving software re-use

    Cook, A. / Hunt, K.J.R. | Tema Archive | 1997


    Field Repairable Arinc 404 and Arinc 600 Filter Connectors

    Adams, John | Emerald Group Publishing | 1990


    Guidelines for Modelling the ARINC 653 Software Architecture

    Lopez, R. / Casas, N. / Fornis, J. et al. | British Library Conference Proceedings | 2008


    Why ARINC 818?

    Grunwald, Paul | IEEE | 2017