The project requirements were divided into three categories: functional requirements, non-functional requirements and anti-requirements. In the interests of better understanding, it was decided to use different tables for each category. However, they all follow the following formatting pattern in relation to the requirement identifier:

<module><type_requirement><id>

In which: 
- type_requirement: R = Functional, NFR = Non-Functional, AR = Anti-Requirement;
- module: W = Water, C = Camera, A = Audio, L = Laser, BL = Ball Launcher, SD = Snack Dispenser,
App = Mobile Aplication, PS = Power Supply, EL = Eletronics, GS = General Structure, CO = Communication;
-id: [dd]: 1-indexed two-digit incrementing number that identifies a requirement in the most specific sub-type

Example:
"WFR01": #1 functional requirement related to water

The functional requirements are divided as follows:

• Type: Functional or Non-Functional, Module (App, Camera, Laser, Audio, Snacks Dispenser, Communication, Ball Launcher, Water, Power Supply);
• Identifier: FR<id>;
• Description;
• Category: Software, Hardware, Mechanics;
• Status: Not started, In Progress and Completed;
• Optional requeriments;
• If it is an option to be discarded if a member of the group quits;
• If it is an option to be discarded if two members of the group drop out.

Requirements

The anti-requirements represent what the project will not accomplish and are divided as follows:

• Identifier: AR<id>;
• Description;
• Module: App, Camera, Laser, Audio, Snacks Dispenser, Ball Launcher, Water, Power Supply, Mechanical.

Anti-Requirements