| 1 | Work Breakdown Structure for the External Data Server Proof-Of-Concept - EA block-diagram, look at ExternalDataServerPoC-lookatslide#7
- After addition of a description of work and definition of done to each TODO, these TODOs will be entered into Jira.
| Owner | Comment |
| 2 | VSS feeder component
Unable to render Jira issues macro, execution error.
| Stefan Wysocki | See vss-feeder repository |
| 3 | - todo create a layer concept for the Franca to VSS leaf mapping (model transformation)
-
Unable to render Jira issues macro, execution error.
|
|
|
| 4 | - todo design and implement franca service (SomeIP)
-
Unable to render Jira issues macro, execution error.
|
|
|
| 5 | - todo implement feeder as PoC
|
|
|
| 6 | - todo check signal to service translation in Adaptive Autosar
- in-progress in CCS project:
Unable to render Jira issues macro, execution error.
|
|
|
| 7 | - todo create PoC Someip simulation component to playback agreed use cases
-
Unable to render Jira issues macro, execution error.
- 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
|
|
|
| 8 | - Select and implement feeder input API → how feeder writes data into the "shared database"
-
Unable to render Jira issues macro, execution error.
- Either it is writing directly into the database (shared with the VSS data server component) or writing into an API provided by the VSS data server.
|
|
|
| 9 | VSS data server component
Unable to render Jira issues macro, execution error.
|
|
|
| 10 | - Implement the connection between the access protocol (GraphQL) and the fetching/writing of data into the database.
-
Unable to render Jira issues macro, execution error.
done duplicate of
Unable to render Jira issues macro, execution error.
|
|
|
| 11 | - APP implement request/response serialization (look at Application Layer)
- Gunnar: this is probably defined by the communication protocol (defined by GraphQL)
|
|
|
| 12 | Define GraphQL schema - what does it look like?
Unable to render Jira issues macro, execution error.
| Alex. | See vss-graphql repository |
| 13 | - todo resolve requested data for the APP from the VSS data structure
-
Unable to render Jira issues macro, execution error.
- ==> This means: Implement the resolvers function in GraphQL
Depends on choosing the database implementation first.
|
|
|
| 14 | - todo change/write data values for requested data leaves
-
Unable to render Jira issues macro, execution error.
- ==> Same as implementation of 14, but for writing.
- This means: Implement Mutation functions in GraphQL
|
|
|
| 15 | - todo handle the subscription for APPs
-
Unable to render Jira issues macro, execution error.
- => Implement Subscriptions (according to GraphQL)
|
|
|
| 16 | - APP implement authentication to access the data server (eg JWT), e.g. json Web token
-
Unable to render Jira issues macro, execution error.
- todo implement the permissions handling in the data server
-
Unable to render Jira issues macro, execution error.
|
|
|
| 17 | Define the "signal groups" that make up each permission and give each permission a name.
Unable to render Jira issues macro, execution error.
- Example permission group created by Alexander (in .md file), similar to the layers discussion. Alexander found it easiest to do Signal→Group mapping
(this fits the VSS layer principle exactly.) but also to have the opposite view (Group→ Signals) generated by tooling (for human readability) - vss.permission.xxx (as proposed in VSS layers) was a nice convention, but let's confirm that we are aligned with Google standards on permission names.
|
|
|
| 18 | - todo finalize permissions layer concept (independent work item)
-
Unable to render Jira issues macro, execution error.
- description TBD
- definition of done TBD
|
|
|
| 19 | Framework Layer / Authentication Service
Unable to render Jira issues macro, execution error.
| | Will update the description and DoD for this component |
| 20 | - todo request APP permissions from package manager
-
Unable to render Jira issues macro, execution error.
- description TBD
- definition of done TBD
| |
|
| 21 | - todo generate access token for the APP including the APP permissions
-
Unable to render Jira issues macro, execution error.
| | Implementation of the module deployed on the platform. Buildable by Android buildystem (Android.bp) |
| 22 | Application Layer
Unable to render Jira issues macro, execution error.
- Implement EV charging status App in Android, with a graphical UI
- Implement Position/speed/make/model/ any other info, as received from driving simulator (could be simple UI, maybe text).
|
|
|
| 23 | TODO: Define what signals we can get from simulator, and try the simulator (Tieto)
Unable to render Jira issues macro, execution error.
| Tieto? |
|
| 24 | - Implement the APP permissions based on permissions defined/proposed in VSS layers
-
Unable to render Jira issues macro, execution error.
- description TBD
- definition of done TBD
|
|
|
| 25 | - Implement authentication as required by the concept including access token request, etc.
-
Unable to render Jira issues macro, execution error.
| | Will be provided as a part of "Authentication Service" to showcase the exposed API |
| 26 | - APP implement request/response serialization for the client
-
Unable to render Jira issues macro, execution error.
- Gunnar: this is probably defined by the communication protocol (defined by GraphQL)
|
|
|
| 27 | - todo agree on PoC use cases for the implementation
-
Unable to render Jira issues macro, execution error.
|
|
|
| 28 | - implement the selected use cases
-
Unable to render Jira issues macro, execution error.
|
|
|
