Search Results

Automotive embedded systems have become very complex, are strongly integrated, and the safety-criticality and real-time constraints of these systems raise new challenges. The OSEK/VDX standard provides an open-ended architecture for distributed real-time capable units in vehicles. This is supported by the OSEK Implementation Language (OIL), a language aiming at specifying the configuration of these real-time operating systems. The challenge, however, is to ensure consistency of the concept constraints and configurations along the entire product development. The contribution of this paper is to bridge the existing gap between model-driven systems engineering and software engineering for automotive real-time operating systems (RTOS). For this purpose a bidirectional tool bridge has been established based on OSEK OIL exchange format files.

During recent years the accident simulation program PC-Crash was developed. This software simulates vehicle movement before, during and after the impact, using 3D vehicle and scene models. When reconstructing car accidents, quite often questions arise regarding occupant movement and loading. Especially important is the influence of different types of restraint systems on the occupant. MADYMO® is a software tool which was developed by TNO in the Netherlands and which is well known in the automotive industry for the simulation of occupant movement. It allows the simulation of all kinds of modern restraint systems such as airbags and seatbelts with and without pretensioners. As the software is used in the automotive industry quite extensively, a huge validated database of dummy and human models is available. Since MADYMO® demands the setup of quite complicated input files, its use normally requires a high level of expertise.

Increasing demands for safety, security, and certifiability of embedded automotive systems require additional development effort to generate the required evidences that the developed system can be trusted for the application and environment it is intended for. Safety standards such as ISO 26262 for road vehicles have been established to provide guidance during the development of safety-critical systems. The challenge in this context is to provide evidence of consistency, correctness, and completeness of system specifications over different work-products. One of these required work-products is the hardware-software interface (HSI) definition. This work-product is especially important since it defines the interfaces between different technologies. Model-based development (MBD) is a promising approach to support the description of the system under development in a more structured way, thus improving resulting consistency.

A steady increasing share and complexity of automotive software is a huge challenge for quality management during software development and in-use phases. In cases of faults occurring in customer’s use, warranty leads to product recalls which are typically associated with high costs. To avoid software faults efficiently, quality management and enhanced development processes have to be realized by the introduction of specific analysis methods and Key Process/Performance Indicators (KPIs) to enable objective quality evaluations as soon as possible during product development process. The paper introduces an application of specific analysis methods by using KPIs and discusses their potential for automotive software quality improvement. Target is to support quality evaluation and risk-analysis for the release process of automotive software.