Warning |
---|
title | Filling instructions |
---|
|
Please add your name in the "Owner" column for the tasks you would like to take over and add comments in the last colum if any. Please for the task(s) you selected, please add a short description and a definition of done Thanks for your cooperation in making the PoC happen |
>>>>>>>>>>>>>>>>>> WORK IN PROGRESS
0:10-12:15 | Vehicle HAL / Vehicle Data Access Track | Work Breakdown Structure for the External Data Server Proof-Of-Concept - The objective of this session is to develop an initial WBS for implementing the External Data Server.
- The TODOs listed below were added to the EA block-diagram, look at ExternalDataServerPoC-WBS.pptx
- After review and addition of a description of work and definition of done to each TODO, these TODOs will be entered into Jira.
|
Vehicle HAL split meeting participants elaborated the WBS belowTODO Develop an initial WBS for implementing an InternalDataServer (Priority 2) Proof-Of-Concept) | Owner | Comment |
2 | VSS feeder component - todo finalize permissions layer concept (independent work item)
- description TBD
- definition of done TBD
|
|
|
3 | - todo create a layer concept for the Franca to VSS leaf mapping (model transformation)
|
|
|
4 | - todo design and implement franca service (SomeIP)
|
|
|
5 | - todo implement feeder as PoC
|
|
|
6 | - todo check signal to service translation in Adaptive Autosar
|
|
|
7 | - todo agree on PoC use cases for the implementation
|
|
|
8 | - todo create PoC Someip simulation component to playback agreed use cases
- note: we could consider using an Adaptive Autosar node like what we did for the FARACON demo
- note: VSS data base could be merged into the VSS feeder
|
|
|
9 | - todo select and implement VSS data storage (e.g. VISS, Geotab W3C PoC implementation)
|
|
|
10 | VSS data server component - todo APP implement authentication to access the data server (eg JWT), e.g. json Web token
- relates to Vehicle Signal Authentication
- description TBD
- definition of done TBD
|
|
|
11 | - todo APP implement access for in-vehicle data, (e.g. App manifest permissions layer concept)
|
|
|
12 | - todo APP implement request/response serialization
- Gunnar: this relates to a communication protocol (so-called binary protocol)
|
|
|
13 | - todo resolve requested data for the APP from the VSS data structure
|
|
|
14 | - todo change/write data values for requested data leaves
|
|
|
15 | - todo handle the subscription for APPs
|
|
|
16 | - todo write a generator which will handle permissions in the data server
|
|
|
17 | Framework Layer / Authentication Service - todo request APP permissions from package manager
- description TBD
- definition of done TBD
|
|
|
18 | - todo generate access token for the APP including the APP permissions
|
|
|
19 | Application Layer |
|
|
20 | - todo Implement the APP permissions based on permissions defined/proposed in VSS layers
- description TBD
- definition of done TBD
|
|
|
21 | - todo implement access token request
|
|
|
22 | - todo APP implement request/response serialization for the client
|
|
|
23 | - todo implement the selected use cases
|
|
|