Home

Software Requirements Specification

1. Functional Requirements

    1.1 The software should choose a path to avoid obstacles using the sensors of the car. - Automation

    1.2 The software should be able to connect to SMCE. - Interface - Connection

    1.3 The car shall be able to be controlled via the mobile app. - Connection

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

    1.5 The car should be able to be controlled via a discord bot. - Connection

    1.6 The car shall provide the ability to speed up for a limited time during a race. - Automation

    1.7 The car shall be able to park automatically when prompted in software. - Automation

    1.8 The car shall automatically drive to a location specified via the mobile app. - Automation (Scrapped)

    1.9 The car’s speed will be adjusted according to the slope it’s driving on. - Automation (Scrapped

    1.10 The software should be able to navigate the car to a specified target position. Automation

    1.11 The software should provide an AI that races against the user. - Automation

    1.12 The software shall show a visual confirmation of the car’s condition. - Interface 

    1.13 The software shall have different levels of racing-skills to choose from - Interface 

    1.14 The software shall provide an option to toggle music on/off - Interface 

    1.15 The software shall show the path a user has driven with a trail behind the car - Interface

    1.16 The software shall showcase the object detection to the user - Interface 

    1.17 The System shall provide feedback if the position is impossible to reach in a specified amount of time. - Automation

    1.18 The system shall have a database to store user data such as race times - Connection

    1.19 The system shall have a joystick as an alternative to using keyboard to control smart-car - Interface
    
    1.20 The system shall have an integrated camera feed so the user can control the car directly in the web application. - Interface

    1.21 The system shall provide a map alternative to the racing that can utilize music, sounds and a health-bar. - Interface 

    1.22 The system shall showcase all cars on a mini-map on the race map. - Interface 

2. Non-Functional Requirements

    2.1 The software should be intuitive for the user. - Interface

    2.2 The software should be visually appealing. -Interface

    2.3 The software shall have an ease of connection with SMCE. - Connection

    2.4 The software shall provide an intuitive way of controlling the car, for example by showing paths and speed differences. -Automation

    2.5 The software shall showcase some form of location identification. - Automation

    2.6 The software shall help users with obstacle avoidance. - Automation

    2.7 The software shall store user data efficiently in a database. - Connection

3. Constraints

    3.1 The software is limited to the SMCE emulator.

    3.2 Limited to JavaScript web-application

    3.3 Only use the sensors that are provided by the customer. (Dimitris)

Features

Automation

Goals

• Obstacle avoidance
• Speed control
• Gyroscope control
• Location identification
• Goal identification
• Path to goal

Functional Requirements

    1.1 The software should choose a path to avoid obstacles using the sensors of the car. 

    1.6 The car shall provide the ability to speed up for a limited time during a race.

    1.7 The car shall be able to park automatically when prompted in software. 

    1.8 The car shall automatically drive to a location specified via the mobile app. (Scrapped)

    1.9 The car’s speed will be adjusted according to the slope it’s driving on. (Scrapped)

    1.10 The software should be able to navigate the car to a specified target position. 

    1.11 The software should provide an AI that races against the user. 

    1.17 The System shall provide feedback if the position is impossible to reach in a specified amount of time.

Non-Functional Requirements

    2.4 The software shall provide an intuitive way of controlling the car, for example by showing paths and speed differences. -Automation

    2.5 The software shall showcase some form of location identification. - Automation

    2.6 The software shall help users with obstacle avoidance. - Automation

Interface

Goals

• User interface
• Controllers
• Camera

Functional Requirements

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

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

    1.13 The software shall have different levels of racing-skills to choose from

    1.14 The software shall provide an option to toggle music on/off

    1.15 The software shall show the path a user has driven with a trail behind the car 

    1.16 The software shall showcase the object detection to the user

    1.19 The system shall have a joystick as an alternative to using keyboard to control smart-car

    1.20 The system shall have an integrated camera feed so the user can control the car directly in the web application.

    1.21 The system shall provide a map alternative to the racing that can utilize music, sounds and a health-bar. - Interface 

    1.22 The system shall showcase all cars on a mini-map on the race map. - Interface 

Non-Functional Requirements

    2.1 The software should be intuitive for the user. 

    2.2 The software should be visually appealing. 

Connection

Goals

• Network
• Database

Functional Requirements

    1.2 The software should be able to connect to SMCE. - Interface - Connection

    1.3 The car shall be able to be controlled via the mobile app. - Connection

    1.5 The car should be able to be controlled via a discord bot. - Connection

    1.18 The system shall have a database to store user data such as race times - Connection

Non-Functional Requirements

    2.3 The software shall have an ease of connection with SMCE. - Connection

    2.7 The software shall store user data efficiently in a database. - Connection