Contact   |   User Forum
 
About HAVEit   |   Events   |   Media   |   Sub-Projects   |   Highly Automated Driving   |   Public Documents   |   Imprint
 
 
  SP1000 - Integration Tasks
  Objectives
  Structure
  Expected Results
  Deliverables
  Milestones
  SP2000 - Safety Architecture implementation
  SP3000 - Joint driver - Co-pilot system
  SP4000 - Safety Architecture applications
  SP5000 - Highly Automated Driving


SP1000 - Integration Tasks

One of the main issues in European cooperation projects consists in an exhaustive definition, as of the beginning of the project, of the functional specifications, in an agreed and validated set of specifications. In HAVEit, Knowllence (KN) will care for the systematic collection and tracking of any requirements throughout the project. Work in this sub-project includes the design of general systems structure, e.g. of the joint system driver - co-pilot system (to give just one example). The different levels of automation must be defined as well as the relevant factors (both from the driver and the Co-pilot) which are used to select the automation level. Feedback strategies must be developed both to maintain and to get back mode awareness of the driver. During the requirements phase of the project all partners will contribute to define and agree on requirements at function, system, module and component levels. On basis of the requirements, partners will derive clear and measurable specifications. Standard v-shape process will be used after that by the partners working on the vehicle platform as the technology will be mature enough. However the partners working on the command level (joint system) will need an iterative process until a freeze of the development will be done to go through integration phase.

On basis of and partly in parallel with the definition of requirements at the before mentioned different system levels partners will develop and agree on a common overall system architecture. In the meaning of a top-down-approach, partners agreed to define and implement common interfaces and protocols from top system levels down to as much as possible component levels. For the example of the joint system this means: Based on the general structure of the joint system of HAVEit a core framework will be established which allows integrating the different ADAS used in the project. Criteria will be defined in order to assess the functionality and usability of the joint system. These criteria will be used in the validation of the different demonstrators as well as in the final evaluation of the HAVEit philosophy. Additionally, the core framework will be implemented in the IZVW simulation tool, allowing using the simulation tool within all steps of the design, development and evaluation of the joint system. Subsequent to the common architecture and interface definition, effective groups of partners will enter the technical development phases in SP 2000 - SP 5000. Due to the relevance of WPs 1100 and 1200 for the entire project, milestone M1 - requirements and specification phase successfully completed - has been introduced in the work plan.

It is planned that sub-projects 2000, 3000, 4000 and 5000 will be finished after project month 33, thereby having achieved their major deliverables: Successful vehicle integration and availability of first highly automated driving functionality. At that point, a third integration element will start: Partners will enter and closely cooperate during the common optimization and validation phase of the project. First, to foster the common understanding and the sharing of key knowledge achieved in terms of the various horizontal and vertical activities and second to prepare for the common, final demonstration of the validation vehicles.





 
   HAVEit - Highly Automated Vehicles for Intelligent Transport