Search

Automotive systems will exhibit increased levels of automation as well as ever tighter integration with other vehicles, traffic infrastructure, and cloud services. From safety perspective, this can be perceived as boon or bane - it greatly increases complexity and uncertainty, but at the same time opens up new opportunities for realizing innovative safety functions. Moreover, cybersecurity becomes important as additional concern because attacks are now much more likely and severe. However, there is a lack of experience with security concerns in context of safety engineering in general and in automotive safety departments in particular. To address this problem, we propose a systematic pattern-based approach that interlinks safety and security patterns and provides guidance with respect to selection and combination of both types of patterns in context of system engineering. A combined safety and security pattern engineering workflow is proposed to provide systematic guidance to support non-expert engineers based on best practices. The application of the approach is shown and demonstrated by an automotive case study and different use case scenarios.

Future automotive technologies become more and more autonomous and connected. This trend requires a rethinking of validation processes due to the amount of test kilometers needed. To be able to test automated and connected functions in many different traffic scenarios, virtual and mixed real-virtual prototypes will be used. Moreover, due to the complexity of such systems, cross-company cooperation is increasing and demands for common prototypes. Spatially distributed prototypes simplify and enhance cross-company collaboration due to faster provisioning of models and better IP protection. However, the setup of such prototypes is very time consuming due to the high integration effort. Here it is shown that the integration effort of spatially distributed prototypes can be massively reduced by using the Distributed Co-Simulation Protocol (DCP). A demonstrator consisting of a small scale test bed located in Graz and a co-simulation containing Bosch driving functions located in Renningen is presented. The demonstrated integration workflow as well as an analysis of the communication challenges of the coupling can be transferred to any other coupling of this kind.

Technical standards are established as a kind of norm or general requirement with respect to the development of technical systems. They shall ensure a uniform way of engineering, to gain benefits when it comes to product comparability, interoperability, assurance of product quality, reliability, safety, and similar properties. Usually, technical standards are developed iteratively, where text documents are used as work products which are subject to continuous negotiations. In this paper, we retrace the requirement-driven development process of the Distributed Co-Simulation Protocol~(DCP) specification. It is the main output of the ACOSAR ("Advanced Co-Simulation Open System Architecture") project. The DCP focuses on the integration of real-time systems into simulation environments. Therefore it poses a significant contribution to development and test of many technical systems. Typical examples are automotive advanced driver assistance system (ADAS), test beds for vehicles and engines, as well as components like electronic control units (ECU). The DCP specification is intended for standardization with a recognized standardization body. Unlike most other technical standards, the DCP specification was engineered on the foundation of written requirements, formulated by an inhomogeneous group of stakeholders. This paper highlights the applied development process, provides examples of requirements, and reports the overall outcome, including benefits and drawbacks.

The exciting new features, such as advanced driver assistance systems, fleet management systems, and autonomous driving, drive the need for built-in security solutions and architectural designs to mitigate emerging security threats. Thus, cybersecurity joins reliability and safety as a cornerstone for success in the automotive industry. As vehicle providers gear up for cybersecurity challenges, they can capitalize on experiences from many other domains, but nevertheless must face several unique challenges. Therefore, this article focuses on the enhancement of state-of-the-art development lifecycle for automotive cyber-physical systems toward the integration of security, safety and reliability engineering methods. Especially, four engineering approaches (HARA at concept level, FMEA and FTA at design level and HSI at implementation level) are extended to integrate security considerations into the development lifecycle.

Future automotive systems will exhibit increased levels of automation as well as ever tighter integration with other vehicles, traffic infrastructure, and cloud services. From safety perspective, this can be perceived as boon or bane - it greatly increases complexity and uncertainty, but at the same time opens up new opportunities for realizing innovative safety functions. Moreover, cybersecurity becomes important as additional concern because attacks are now much more likely and severe. Unfortunately, there is lack of experience with security concerns in context of safety engineering in general and in automotive safety departments in particular. To remediate this problem, we propose a systematic pattern-based approach that interlinks safety and security patterns and provides guidance with respect to selection and combination of both types of patterns in context of system engineering. The application of a combined safety and security pattern engineering workflow is shown and demonstrated by an automotive use case scenario.

The functional mockup interface (FMI) is a tool independent standard to support model exchange and cosimulation, as intended by the automotive industry to unify the exchange of simulation models between suppliers and OEMs. The standard defines functional mockup units (FMU) as components which implement the FMI. The creation and exchange of simulation models with customers and suppliers across the automotive supply chain is highly beneficial: In order to support early phases of development (requirement formulation, creation of executable specifications, and rapid prototyping) the creation of FMUs for co-simulation is reasonable. In this paper, we propose a structured method for generation of FMUs for co-simulation which are versatile, highly transportable and fast simulating. We show how to compile FMUs based on SystemC and SystemCAMS, representing digital as well as analog and mixed signal electric and electronic systems. This tool-independent method allows inclusion of existing simulation models with only minimal adaptations. Additionally, no modifications of the standardized libraries are necessary with the outlined approach. The resulting FMUs allow convenient exchange and fast co-simulation of automotive systems, as they may be integrated by any FMI compatible master tool. An automotive battery system use case is shown to highlight these advantages and to demonstrate the simulation performance of the resulting FMUs.

Due to the high overall complexity of embedded systems in the automotive domain, the concept and system design phases have shown to be important, as they lay the foundations for implementations. Therefore, front-loading principles are advantageous. In this work, we present a methodology for semi-formal notation based system design. In the end, we demonstrate a transformation scheme for the conversion from system models to executable code, featuring full traceability and support for hardware and software paradigms. An automotive use case demonstrates the capabilities of the outlined approach.

The introduction of the new automotive standard on functional safety ISO 26262 raises different challenges from the process point of view. Hence, a standardized process mapping roles, activities and work products according to ISO 26262 needs to be defined. This process has to be tailored according to the automotive safety integrity level (ASIL) and to company specific practices and teams. In this work, we propose a method content approach modeled with SPEM in order to define and formalize development processes, enabling better management and easier tailoring activities.

The CESAR project1 aims at elaborating a Reference Technology Platform usable across several application domains (Aeronautics, Automotive, Industrial Automation, Railway and Space) for the cost effective development and validation of safety related embedded systems. Safety and, more generally, dependability are therefore major topics addressed by the project. This paper focuses on the work performed on safety requirements and approaches to be supported by a common Reference Technology Platform. We analyse and compare the industrial practice, applicable standards and state of the art so as to identify which and how safety views should be supported. We focus in particular on the major axes investigated by the project, formal model-based techniques for requirements engineering and component-based engineering. Preliminary realisations and case studies confirm the interest and provide refined requirements for the final version of the platform.

Validation front-loading using simulation is required to save efforts and support decision making during the development process. For automotive distributed embedded systems, the fast increasing system complexity usually prevents the use of simulation encompassing the entire communication architecture. The simulation is then focused to single domain and/or components. We present in this work a heterogeneous co-simulation model of a FlexRay based system comprising simulation models from the software components down to the waveforms within the FlexRay electrical cables. This platform enables the efficient analysis of the assembled system and more especially of the interactions between the components. The description of the models is supported by three test campaigns in order to highlight the importance of holistic simulation as well as the potential of the proposed approach.