Home

Welcome to the group-15 wiki!

Functional and Non-Functional Requirments

Basic movements:

Functional requirements:

• The car should be able to make it back and forth.
• The car should be able to move left and right.
• The car should be able to be controlled with voice commands.

Non-Functional requirements:

• The car should respond in less than 2 seconds.

Application:

Functional requirements:

• The system should allow authorized users.
• The system should allow the user to use the car remotely.
• The application should provide users with options of how they want to control the car (Voice command, Controller)
• The camera should provide feed from the emulator to application.
• The application should have a fully working API integrated to send and receive commands to the car.
• The car should be able to connect with applications via MQTT so the user is able to control the car.
• The application should contain a help feature where the user knows what commands they can use.

Non-Functional requirements:

• The application should be easy to use.
• The application should be safe for all users.
• The application should be in English.

Avoiding obstacles:

Functional requirements:

• The car should be able to detect and avoid obstacles in the current direction.
• The car should be able to choose another direction after avoiding obstacles.

Non-functional requirements:

• The car should be able to avoid obstacles by using sensors to detect obstacles.
• The car should be able to avoid obstacles from a reasonable distance.

Accounts:

Functional requirements:

• The system should ask for the username and password in order to be able to use the application.
• The application should have a registration feature that registers users using firebase.

Non-functional requirements:

• The application should be easy to use.
• The application should be safe to use for all type of users.