JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project |
We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies. |
To recall the context diagram
The focus is here on the data sent to cloud already. There are functions to be developed in the context of the car,
but they are not covered here. Rather they get collected and may be implemented by the OEM's on their will.
Car owners and drivers have similar interests and thus, car owner = driver for most of the requirements.
Requirements purely derived from data privacy are not mentioned explicitly but assumed.
Key | Requirement | Comments |
---|---|---|
1.1 | As a car owner I want to access the data collected with my car | |
1.2 | As a car owner I want to modify the access rights to the collected data | give access to third parties |
1.3 | As a car owner I want to request deletion of all or partial data | GDPR |
1.4 | As a car owner I want to access the record of changes that I made to manage my data | i.e. when did I allow the access to the data for xyz |
1.5 | As a car owner I want to know for which purposes my collected data is used | |
1.6 | As a user I want to have easy to understand user interfaces to allow me to comprehend the content and the way of how it is presented | |
1.7 | As a user I don't want to create another login, I would like to use existing identification methods with the possibility of integration in other ecosystems | A government issued id f.e. |
1.8 | As a car manufacturer I need to store the collected data and link it to the creating user. | |
1.9 | As a car manufacturer I need to prepare on bulk operations on data so that I can perform actvities on large datasets wrt. user, purpose, consumer and so on. | |
1.10 | As a car manufacturer I need to provide infrastructure to allow third parties access to the collected data of individual car owners. | This includes f.e. service providers, authorities, and car owners |
1.11 | As a car manufacturer I may want to provide user interfaces to allow the car driver to alter settings from the car. | |
1.12 | As a car manufacturer I want to keep the cost low for the additionally required functionality. | |
1.13 | As a car manufacturer I don't want an adverse effect on my promised SLA | |
1.14 | As a car manufacturer I don't want the overall security to be affected. | |
1.15 | As a user I want to onboard the system. | This is for all users, the onboarding will differ, based on the role 1.7 to be considered too |
1.16 | As a car manufacturer I want to onboard a new data source. | F.e. a new cloud storage, a new model ... |
1.17 | As a car manufacturer I want to manage access rights easily, grouped by data sources, access rights, consumers ... | This is required for bulk operations on data sets |
1.18 | As a car manufacturer I want to add tags to datasets if required to group them and thus enable for bulk operations | |
1.19 | ||