Interface

Goals

• User interface
• Controllers
• Interaction

Functional Requirements

    1.2 The software will have a connection button to connect to SMCE.

    1.4 The software shall offer the choice to control the car with a keyboard when on PC.

    1.7 The software shall have a button to click to automatically park the car.

    1.3 The software shall show a visual confirmation of the car’s condition.

Non-Functional Requirements

    2.1 The software should be intuitive for the user.

    2.2 The software should be visually appealing.

User Stories linked to Interface Milestone

    1.1 As a user, I want to have the choice to listen to music while using the car to provide a sense of integration and realism to the simulation.. Issue: #3

    2.1 As a user, I want to be able to use a simple remote control to control the car, so that I don’t have to spend a lot of time figuring out how to use it. Issue: #4

    2.2 As a user, I want to see the condition of my car through a ‘health bar’ on the screen. Issue: #5

    2.3 As a user, I want to be able to log my credentials so that my times will be saved to the database.

    3.3 As a user I want to visually see the object detection so that I can avoid these objects. Issue: #58 - Out of Scope

    7.1 As a user I want to be able to see the emulator feed from my application to be able to control the car properly Issue: #13

Out of scope

    7.2 As a user I want to display the path my car has driven in the environment. Issue: #59

    7.3 As a user I don't want to waste my time trying to go places that I can't reach within a realistic timeframe. Therefore the system should provide feedback if the position is impossible to reach in a specified amount of time. Issue: #18