Towards verified automotive software

Abstract

Automotive software is one of the most challenging fields of software engineering: it must meet real time requirements, is safety critical and distributed over multiple processors. With the increasing complexity of automotive software, as for example in the case of drive-by-wire, automated driving and driver assitents, software correctness becomes more and more a crucial issue. In order that these innovations can become reality, it is necessary to be able to guarantee software correctness.The presented work aims at verification of automotive software. For this purpose it introduces a verification approach, including a framework of verified modules which assists the verification of the actual application. Feasibility of this approach was validated on a case study that also showed how verification can be integrated into the development process.

Verification of clock synchronization algorithms: experiments on a combination of deductive tools

“…These formalized proofs can serve as the basis for verification of more concrete clock synchronization protocols, such as the ones used in the FlexRay protocol [Fle04] (for drive-by-wire application in automotive industries). There has indeed been on-going work in the verification of FlexRay using Isabelle/HOL [BKKS05,KS06] which is complementary to our work.…”

Towards the Pervasive Verification of Automotive Systems

“…An update to a shared variable in round k is visible to all application programs that poll this variable in round k + 2. This programming model is very close to the model used in [12], where formal correctness proofs for a distributed emergency call application in cars are reported.Worst case timing analysis permits to guarantee, that applications and drivers satisfy the requirements of the schedule. If the requirements of the schedule are satisfied and the interfaces are programmed as prescribed by the schedule, then one can show that the user model is implememented by compiler, operating system and hardware [6].…”

“…An update to a shared variable in round k is visible to all application programs that poll this variable in round k + 2. This programming model is very close to the model used in [12], where formal correctness proofs for a distributed emergency call application in cars are reported.…”

Formal-Based Framework for Analysis of Logical Architecture

“…This direction has been touched for the first time by Botaschanjan et al (2008) though only for upper layer of automotive systems and focused on later verification phases. The first steps towards a methodology for development of verified embedded system have been done in (Botaschanjan et al, 2005;Botaschanjan et al, 2006). For example, a typical setting found in the automotive domain, a time-triggered operating and communication bus system, has been verified (Spichkova, 2006;Kühnel, Spichkova, 2006;Kühnel, Spichkova, 2007).…”