website report

Page 4 of 33

Problem Description The issue with current infotainment systems available in the market is that those systems

usually come from third party companies, which mostly means that they are not well designed

with good user experience in mind, but rather designed just to fill a hole in the market for those

who do not have a built-in infotainment system in their cars. Good infotainment systems are

usually first party, which means they come built in the car itself, which is strictly limited to

expensive cars. The purpose of this system is to provide a third-party infotainment system that is

designed with the idea of implementing good user experience for the users.

User Requirements The target users of our system will be car drivers. Since the target is too big, we will try to

design a one size fit all solution by adopting the best practices and standards from the existing

systems in the market as well as design considerations learnt from the course. The user (car driver)

is capable of driving a car, therefore we will assume that his/her senses and capabilities are good

enough to deal with such systems. Users who are non-drivers (passengers for example) are not

considered as a main target for the system.

Page 5 of 33

Driver

Vision

✓ Driver is assumed to have good vision, but the following will be considered:

✗ Interface is not close to eyes, therefore big screen size, big icons and large text will be used.

✗ Asking user for inputs will be minimal since driving environment is not suitable for inputs.

✗ Adaptive brightness and light/dark modes will be considered to accommodate day and night times (light interface during day and dark interface at night).

Audio

✓ Should have good hearing capabilities, but the following will be considered:

✗ The system should not play loud or unexpected sounds so that it does not shock the driver. Gradual (ascending) and quiet tones will be considered.

✗ Repeated and unnecessary warning sounds should be kept at a minimum to avoid frustration.

Haptic

✓ Should have good touch capabilities, but the following will be considered:

✗ The user may interact with the system either by touch or by using the rotating dial. When the user interacts with the system by either way, the system will make a sound to indicate that the user touch or input is being received.

✗ Big icons and buttons are very important especially when the user is driving, because the user’s touch accuracy when driving is less.

Mental

✓ Good mental state, but the following will be considered: ✗ The driver’s focus will differ based on whether he/she is driving or

parked, therefore advanced and complex features will be disabled when driving since they require more attention.

✗ Virtual Assistant can listen to the user’s commands and read incoming notifications. This is very useful since the driver’s attention will be on the road.

Page 6 of 33

Emotion al

✓ The driver can have many moods, but the assumption is that he is calm and in a neutral mood, but some common scenarios may occur:

✗ System warning lights or messages may put the user in fear and panic. The system should present these messages in a comfortable and calming manner to avoid panicking.

✗ Asking the user for many inputs while driving may cause anger and frustration, therefore inputs will be reduced while driving.

The UI Environment

The system will be used inside the car, where the user may be in two main situations;

driving or parked. This environment is assumed to be quiet and clean, and the driver will have to

be clean as well to properly interact with the interface. Best practices, standards and design

considerations learnt from the course will be implemented to accommodate such environment. The

day and night cycles are considered because the driver may use the system at different times, where

the system must adapt if it is in bright daylight or dark night.

Task Analysis This section discusses the flow of events for each task that the user can do. Because the

system contains lots of features (i.e. lots of tasks), we limited the tasks therefore it does not reflect

the whole system. Another assumption we considered is that the system will be loaded and the

starting point for each task is the home screen of the system. Lastly, tasks were summarized to

their simplest form, which means advanced or optional steps are ignored. The main tasks that the

user needs in infotainment systems are: making phone calls, playing music, navigate to a

destination using maps, and view information such as date and time.

Page 7 of 33

Figure 1: Task Flow Diagram for the Task of Making a Phone Call

As shown in in figure 1, the task starts by the user selecting the phone icon from the home

screen. After that, the system checks if the user’s phone is connected or not so that he/she can

continue the task. Then, the user should choose the call recipient by selecting from recent calls,

from favorites list, from contacts lists, or by entering the recipient number manually. After

selection, the system shows that the call is being initiated. When the recipient answers the call, the

call status screen shows up, otherwise the user is taken back to choosing a recipient again.

Page 8 of 33

Figure 2: Task Flow Diagram for the Task of Playing Music

Figure 2 shows that the task starts by the user selecting the music icon from the home

screen. After that, the user should choose the input source to play music from. The available

sources are Bluetooth, USB, AUX or Radio. When the user selects the input source, he/she must

press the play button so that the music starts playing.

Page 9 of 33

Figure 3: Task Flow Diagram for the Task of Maps Navigation

As illustrated in figure 3, the user should first select the maps icon from the home screen

where then he is prompted to choose the destination. The destination can be chosen using many

methods. The methods are either by searching, choosing from saved places, choosing from recent

list, or choosing from categories list. After the destination is chosen, the system shows the map

and navigation screen.

Page 10 of 33

Figure 4: Task Flow Diagram for the Task of Viewing Information

Figure 4 shows the task of viewing information. Viewing information in this diagram

means information like date and time. The task starts with the user selecting the information icon

from the home screen, where date and time information are shown as soon as it is selected.

Figure 5: Task Flow Diagram for the Task of Viewing Information using Voice Control

Page 11 of 33

The task illustrated in figure 4 can be done in another way (as well as all other previously

mentioned tasks). This can be accomplished via voice recognition, where figure 5 shows that the

user starts by pressing the microphone button on the steering wheel, then the voice assistant starts

talking, indicating that it is there to listen. After that, the user uses their voice to input a command

to the voice assistant (“what’s the date today” in figure 5). If the voice assistant successfully

recognizes the command, the task is executed, otherwise it will ask the user to say the command

again. This can be used for all the tasks, where the user can say things like “Call Ali” or “Navigate

to the nearest petrol station”.

Paper Prototype

This section shows the created paper prototype for the proposed system. The paper

prototype helps the software creator to imagine the software being developed before the actual

development starts. It also helps us manage the final user’s expectations because the expected

outcome is shown to the final user at a very early stage. The created prototype only covers the

simple navigation through the proposed system.

As illustrated in the following figures, the navigation starts with the loading screen, then a

warning is shown to the user indicating that the system should not be used in inappropriate

conditions. After that, the home screen loads where it shows the available functions in the system

such as navigation, phone, music, settings, and information. Selecting any of the icons takes the

user to the corresponding screen. In this report, the user is assumed to go through the system as

follows: