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 where roles and their dependencies are explained.

The focus is on the data which was already sent to the cloud. 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.

Car owner/driver

KeyRequirementComments
1.1

As a car owner, I want to control who accesses my vehicle’s data

so that I can protect my privacy


1.2

As a car owner I want to modify the access rights to

the collected data

give access to third parties
1.3As a car owner I want to request deletion of all or partial dataGDPR
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 driver, I want to see a detailed log of how my data is being used

so that I can ensure my consent is respected.


1.7

As a car owner, I want to manage data sharing preferences for multiple vehicles

so that I can customize settings for each.


1.8

As a driver, I want to receive alerts about vehicle maintenance issues

so that I can address them proactively.


General user

Key

RequirementComments
2.1

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 


2.2

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.
2.3As a user I want to onboard the system.

This is for all users, the onboarding

will differ, based on the role

Car manufacturers/OEM's

Key

RequirementComments
3.1As a car manufacturer I want to onboard a new data source.

F.e. a new cloud storage,

a new model ...

3.2

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

3.3

As a car manufacturer I need to add tags to datasets if required

to group them and thus enable for bulk operations


3.4

As a car manufacturer I want to measure usage of the services to enable

billing of pay per use base


3.5

As a car manufacturer I need to store the collected data and link it

to the creating user.

This includes f.e. service providers,

authorities, and car owners

3.6

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.


3.7

As an OEM, I want to package vehicle data into purchasable datasets so that I can monetize it securely


3.8

As an OEM, I want to enable third-party service providers to access specific data points via APIs so that I can sell data per usage.


3.9

As an OEM, I need to manage access permissions for third parties so that I can ensure compliance with regulations.


3.10

As an OEM, I want to track revenue generated from data sales so that I can assess the profitability of my data-sharing program.


3.11

As an OEM, I want to ensure that sensitive vehicle data remains secure so that I can protect my customers and maintain trust.


3.12

As a car manufacturer, I want to onboard a new vehicle model series to the ecosystem by defining its capabilities (e.g., sensors, data types) so that service providers can leverage its full potential.


3.13

As a car manufacturer, I want to upload metadata for a new vehicle model (e.g., supported data points, hardware specifications) so that developers can create services tailored to it.


3.14

As a car manufacturer, I want to configure data access rules for a new vehicle model series so that I can control which data points are shared with third parties.


3.15

As a car manufacturer, I want to announce the availability of new vehicle features to developers and service providers so that they can start building compatible services.


Fleet manager

KeyRequirementComments
4.1

As a fleet manager, I want to monitor the performance of all vehicles

in my fleet so that I can optimize operations and reduce costs.


4.2

As a fleet manager, I want to schedule predictive maintenance for my vehicles

so that I can minimize downtime.


4.3

As a fleet manager, I want to access real-time location data for my vehicles

so that I can track them efficiently.


4.4

As a fleet manager, I want to generate performance and cost-efficiency reports

so that I can present actionable insights to stakeholders.


4.5

As a fleet manager, I want to receive alerts about potential mechanical issues

so that I can address them before they become critical


Service developers

KeyRequirementComments
5.1

As a service developer, I want to access anonymized historical datasets so that I can build and test my applications.


5.2

As a service developer, I want to use sandbox environments to prototype new services so that I can ensure compatibility with the ecosystem.


5.3

As a service developer, I want to subscribe to live vehicle data streams so that I can offer real-time services like navigation or predictive maintenance.


5.4

As a service developer, I want to access comprehensive API documentation so that I can integrate ecosystem data seamlessly.


5.5

As a service developer, I want to monetize my applications within the ecosystem so that I can generate revenue for my innovations.


5.6As a service developer, I want to receive insights into user feedback and data usage so that I can improve my services.
5.7As a service developer, I want to onboard a new service into the ecosystem by registering it with clear descriptions and required data sources so that I can make it discoverable by users and providers.
5.8As a service developer, I want to define the SLAs for my service (e.g., latency, availability) so that I can establish clear expectations for users.
5.9 As a service developer, I want to integrate a payment model (e.g., subscriptions or pay-per-use) during service onboarding so that I can monetize my offering.
5.10As a service developer, I want to test my new service in a sandbox environment so that I can ensure compatibility and functionality before launch.
5.11As a service developer, I want to create custom queries to extract specific subsets of data from large datasets so that I can process only what is relevant to my application.
5.12As a service developer, I want to access datasets in different formats (e.g., JSON, CSV) so that I can integrate them into my workflows easily.
5.13As a service developer, I want to use a built-in analytics tool to process and summarize datasets so that I can quickly derive actionable insights.
5.14As a service developer, I want to collaborate with OEMs during the onboarding of a new service so that I can ensure compatibility with their vehicles.
5.15As a service developer, I want to test my service with simulated or synthetic datasets so that I can validate its performance before accessing real data.

Regulators

KeyRequirementComments

As a regulator, I want to audit data-sharing activities

so that I can ensure compliance with legislation.



As a regulator, I want to access anonymized and aggregated data

so that I can analyze trends for policymaking.



As a regulator, I want to receive alerts for non-compliance incidents

so that I can take timely action.



As a regulator, I want to monitor emissions and traffic patterns

so that I can develop policies for sustainable transportation.


  • No labels