Search Results

The increasing complexity of electric/electronic architectures (EEA) in the automotive domain raised the necessity of model-based development processes for the design of such heterogeneous systems, which combine different engineering principles with different viewpoints. High-level simulation is a great means to evaluate the EEA in the concept phase of the design, since it reduces costly real-world experiments. However, model-based EEA design and analysis as well as its simulation are often separate processes in the development lifecycle. In this paper, we present a novel approach that extends state-of-the-art model-based systems engineering principles of EEA by a behavior specification reusing library components. The specification is seamlessly integrated in the development process of a single source EEA model. Therewith, the starting point is the abstract logical function architecture of the EEA.

To fulfil the increasing requirements of electric/electronic architectures in automotive environments new concepts for future Electronic Control Units (ECU) are needed. Novel hardware architectures offer much higher potential compared to standard microcontroller devices. In previous publications the advantages of modular gateway architectures over standard microcontroller solutions were shown, especially regarding performance, low latency times, busload independency and configurability. However developing hardware gateway configurations is neither convenient nor practical. But recent development showed a trend towards early e/e-architecture models in tools like PREEvision which are usually used for architecture exploration. In this contribution we demonstrate an approach that closes the gap between such modeling tools and the reconfigurable gateway architecture.

Model based architecture methods for designing and optimizing electrical and electronic systems of vehicles are becoming more and more popular. However, there is still no standard on the models which are vital for design and description of architectures. Most methods and tools begin with a functional abstraction. The functional elements are mapped to electronic control units [ECU] which are connected through bus systems and supplied with electrical power via clamps. An open, unanswered question is the determination of specific control unit numbers and location in a vehicle platform. To do so, a new model layer is proposed: the “technological model” with so called “technological building blocks”. It sits in-between the “functional model” and the “communication model” and describes the necessary constraints for designing the optimum number and position for electronic control units.