Search Results

Once the adaptive cruise control systems are already in the market in Japan and Europe, the evolution of these comfort systems is logically going towards implementing new additional functions and safety strategies in order to detect and actuate in case of emergency. This transition has to be done in clear and precise steps to assure an easy adaptation to each improvement. Driver assistance systems will play a major role in the future to minimise the risk and consequences of accidents and to increase the driving comfort level. The impact of such systems on traffic and society is briefly commented. This paper discusses the need of new driver assistance systems and a possible roadmap for them. After a short introduction of present Adaptive Cruise Control (ACC), and based on them, next possible functions are described.

Due to the increase in demand for comfort and safety features in today's automobiles, the internal vehicle communication networks necessary to accommodate these features are very complex. These networks represent a heterogeneous architecture consisting of several ECUs exchanging information via bus systems such as CAN, LIN, MOST, or FlexRay buses. Development and verification of internal vehicle networks include multiple design layers. These layers are the logical layer represented by the software application, the associated data link layer, and the physical connection layer containing bus interfaces, wires, and termination. Verification of these systems in the early stages of the design process (before a physical network is available for testing) has become a critical need. As a result, the need to simulate these designs at all their levels of complexity has become critically important.

With the increasing complexity of electronic vehicle systems, one particular “gap” between function development and ECU integration becomes more and more apparent, and critical; albeit not new. The core of the problem is: as more functions are integrated and share the same E/E resources, they increasingly mutually influence and disturb each other in terms of memory, peripherals, and also timing and performance. This has two consequences: The amount of timing-related errors increases (because of the disturbance) and it becomes more difficult to find root causes of timing errors (because of the mutual influences). This calls for more systematic methods to deal with timing requirements in general and their transformation from function timing requirements to software architecture timing requirements in particular.

In the new century the automotive industry is transforming itself from an entirely mechanical industry to an industry that is driven by electronics and services. The companies who will be most successful are those who are able to control, drive and renew the architectural concepts enabling the introduction of state-of-the-art information technology to the car and its supporting infrastructure. This paper will first define the term architecture and will elaborate about the increasing relevance of architectural thinking in the automotive domain. Architectural leadership will be defined to mean control (proprietary ownership of components and/or interfaces), creation of a de-facto or legal standard as well as renewal (creation of new products and markets utilizing new linkages of existing architectures). In the second part examples of successful and less successful approaches for establishing architectural leadership in the automotive industry are discussed.