Technical innovation

DESERVE aims to design and develop a tool platform for embedded Advanced Driver Assistance Systems to exploit the benefits of cross-domain software reuse, standardised interfaces, and easy and safety-compliant integration of heterogeneous modules to cope with the expected increase of function complexity and the urgent need to reduce costs.
The joint research opportunities for Industry and Academia will foster the creation of a European standard reference technology platform, embodying meta-models, methods and tools for safety-critical, hard real-time ADAS development supported by European tool vendors.
The DESERVE Tool Platform will provide the environment for ADAS design, development, pre-validation and even pre-certification of software and hardware modules to be integrated in ADAS applications. With safety-critical requirements considered in the design and systems development, integrated, trusted, interoperable tools and tool-chains will become available.

The benefits of the Tool Platform will be demonstrated to the stakeholders by developing different types of prototypes: urban vehicles (passenger and freight), passenger car, and long distance freight transport vehicle. These demonstrators will implement next generation ADAS such as low speed manoeuvring assistance, urban driving support, pedestrian detection and avoidance, collision mitigation, adaptive cruise control and lane keeping integration, driver monitoring, eco driving and cooperative applications.


The DESERVE key innovation aspects are briefly summarised as follows:

• A standard platform for development of a new generation of ADAS
• Natural active support as the standard intervention
• Vehicle-Driver sharing control
• Actual deployment of model-based approach including holistical driver – vehicle– scenario
• Easy extension towards cooperative systems
• Flexibility at sensors/actuators/vehicles/architecture/HMI levels
• High reliability and Fail Safe
• Low cost via SW reuse and sharing of HW (i.e. standard components and interfaces)
• Decision support on heterogeneous system-on-chip-architectures (cost modelling on basic building blocks for next generation implementations)
• Virtual testing of the applications

Some of these innovation aspects are completely new, as is the virtual testing of the application; other aspects have been already considered in research projects, but only DESERVE is integrating everything in a single development platform. The advantages of the DESERVE approach are not limited to the ease of composing different applications in one single application, but in the availability of common resources, in particular related to the driver interface. This will further reduce the development cost, but it will increase also driver acceptability, since all functions will have a natural, homogeneous behaviour. The driver request to have more (because he/she is tired) or less support could be easily extended in natural way to all support functions, without requiring a specific set up of each one.

Furthermore, the support will be adapted to driver needs, state and behaviour, considering also the environmental conditions (weather, visibility, traffic, type or road, road condition, etc.).
DESERVE will allow safe evolution of the ADAS solutions towards full driver support, including autonomous manoeuvres in specific scenarios, such as automatic parking, supervised autonomous driving on highways or Stop & Go in congested traffic. Due to the safety requirements the current approach is to build monolithic solutions, completely closed, and extensively tested to fulfil such safety requirements.

The aim of is to avoid such a scenario, with the development of a safe architecture together with safety-qualified components. Modern methods for efficient modular software development such as model-based design are not yet available for advanced driver assistance systems. DESERVE modules will be developed on a reusable and easily extensible rapid-prototyping development platform. To get reusable and hardware independent software modules some meta information about the HW characteristics of the software modules must be added to the module description already in an very early stage and a high abstraction level.