Impact of dependable software development guidelines on timing analysis
Wenzel, I; Kirner, Raimund; Schlager, M.; Rieder, B; Huber, B.
Citation: Wenzel , I , Kirner , R , Schlager , M , Rieder , B & Huber , B 2005 , ' Impact of dependable software development guidelines on timing analysis ' . in In: Procs of the International Conference on Computer as a Tool : Eurocon 2005 . IEEE , pp. 575-578 , International Conference on Computer as a Tool (EUROCON 2005) , Belgrade , 21-24 November .
The knowledge of the worst-case execution time (WCET) of real-time tasks is mandatory to ensure correct timing behavior of real-time systems. However, in practice an exact WCET analysis is often intractable due to limitations in computability and analysis complexity of real-size programs. In this paper we analyze how development guidelines for dependable software support and simplify WCET analysis. We investigate three guidelines and their impact on WCET analyzability. DO-178B as a production guide for avionics software expresses requirements that are relevant for timing analysis. The MISRA guidelines include C programming guidelines that improve the WCET analyzability of software. Finally, ARINC 655, a standard for software architectures of avionic systems, provides examples on how to simplify timing analysis already at the design level as early as in system design. The argument of this paper is that careful system design and programming improves the timing analyzability of real-time systems.
“This material is presented to ensure timely dissemination of scholarly and technical work. Copyright and all rights therein are retained by authors or by other copyright holders. All persons copying this information are expected to adhere to the terms and constraints invoked by each author's copyright. In most cases, these works may not be reposted without the explicit permission of the copyright holder." “Copyright IEEE. Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from the IEEE.”