Automotive Case Study

This folder can be used for the automive case study. We could use it to track our progress, as well as upload the code for our apps.

Here is the road map that we have.

Deadline

Dec 12 Workshop

Understand what makes them different We want the apps to find these and research them.
- Read android automotive documentation Nov 6
- Identify what sensors or actuators we can have access through Android Automotive OS doc Nov 7
- Read through Audio Attributes Nov 7
- Identify product specific sensors (sensors that are only available for one vehicle and not for others) Nov 8

Create one app on these products (that could have) different behaviour on these products.
- Start with a messaging app template Nov 10
- Start with a media service app template Nov 10
- Learn how to display a text or an image on the screen Nov 10
- Play a music file through the media service Nov 10

Access a feature (e.g. sensor) that only one product has.
- Detirmine product specific sensors identified previously to be used in the media service app Nov 14

Can these emulators be used with a car simulator such as CARLA? Nov 11
- Set up a meeting with Huaken Nov 7
- Receive back answer from Huaken Nov 10
- If CARLA or another simulator can be used, ask team if this is useful for our project Nov 11
A car doesn't have a sensor. An app uses that sensor. What happens? Can the app still be installed? Does the app crash? Does the system crash?
Kirill adds his examplar Nov 12
- Document the transitive error, and how it crashes Nov 24

Here is a scenario that must hold. There is a beep from a sensor or a drive assist that is critically important.

This sensor uses the same resource (the speakers) as a lower priority app such as spotify.

How can we ensure that an update to the product line does ensures this? What do we need to test, verify, model, analyse to ensure it?

We use this case study to find an examplar to better see the problem and identify by example its solution.