The automotive domain has seen safety engineering at the forefront of the industry’s priorities for the last decade. Therefore, additional safety engineering efforts, design approaches, and well-established safety processes have been stipulated. Today many connected and automated vehicles are available and connectivity features and information sharing are increasingly used. This increases the attractiveness of an attack on vehicles and thus introduces new risks for vehicle cybersecurity. Thus, just as safety became a critical part of the development in the late 20th century, the automotive domain must now consider cybersecurity as an integral part of the development of modern vehicles. Aware of this fact, the automotive industry has, therefore, recently taken multiple efforts in designing and producing safe and secure connected and automated vehicles.
The replacement of safety-critical mechanical components with electro-mechanical systems has led to the fact that safety aspects play a central role in development of embedded automotive systems. Recently, consumer demands for connectivity (e.g., infotainment, car-2-car or car-2-infrastructure communication) as well as new advances toward advanced driver assistance systems (ADAS) or even autonomous driving functions make cybersecurity another key factor to be taken into account by vehicle suppliers and manufacturers. Although these can capitalize on experiences from many other domains, they still have to face several unique challenges when gearing up for specific cybersecurity challenges. A key challenge is related to the increasing interconnection of automotive systems with networks (such as Car2X). Due to this connectivity, it is no longer acceptable to assume that safety-critical systems are immune to security risks.
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.
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.