Anti Requirements

AR01 - The parking lot layout must not have any parking spots in diagonals, curves or anything different from the common rectangle layout

AR02 - The client must use the old ticket system if they and their car are not registered in the app or if they don’t want to

AR03 - The car must have a plate following brazilian pattern

AR04 - The parking lot must have its whole area WiFi covered

AR05 - The parking lot floor must be flat and even

AR06 - The whole system must be in a smaller scale for the team to be able to test everything in time

AR07 - The parking lot has to be indoors

AR08 - The gate system will be a simulation, not a real physical structure

Robot

Functional Requirements

RFR01 - The robot must move itself to a parking spot when it receives a signal from this spot that has newly been occupied.

RFR02 - The robot must only move itself following the marked lines on the ground

RFR03 - The robot must stop and wait when an object is obstructing its path

RFR04 - The robot must, when encountering an intersection, decide whether to go straight or take a turn

RFR05 - The robot must, in case of taking a turn, turn 90º to the right or left at an intersection according to the path to be taken

RFR06 - The robot must store a mapping of the parking lot as a graph and its current position.

RFR07 - The robot must iterate its position on the graph after passing through each parking spot marker

RFR08 - The robot must stop when it reaches the desired graph node, and rotate 90º to the right or left in order to face the car as indicated by the graph element.