Home

Purpose and Scope

EasyPark aims to help people find an available parking lot around the “Cittadella Politecnica” without entering each parking in the campus and check the spot availability. The system can be only used by those who are authorized to enter the campus parkings and possess a smartphone with the EasyPark app installed and the internet connection. While approaching the Politecnico, the user receives automatically notifications on the campus parking lots status. Additionally, when the user enters one of the parkings, he receives personalized greetings and quick directions to the first vacant space.

Glossary

• AREA: A part of the campus which includes buildings, parkings and offices.
• CAMPUS: The grounds and buildings of the “Cittadella Politecnica”.
• DIRECTIONS: Simple instructions or guidance useful to locate a vacant spot.
• SENSORS: A mechanical device that receives a signal or stimulus and responds to it.
• "FIND MY CAR": A system function accessible from a smart device which guides the user back to his car.
• PARKING AREA or PARKING LOT: A delimited area in the campus that contains several parking spaces. Its main entrance is a gate with an automatic barrier.
• PARKING GATE: The main entrance of a parking area where is placed an automatic barrier.
• PARKING SCREEN: A screen placed at the entrance of a parking lot.
• PARKING SPACE: An individual marked area in a parking lot where the user can park his car.
• POLITECNICO AREA: The area delimited by the circle having as center the center of the campus and radius equals to 1,5 km.
• TO APPROACH THE POLITECNICO: To reach by car a distance lower than 1,5 km from the center of the campus.

(Politecnico Area)

Actors

People who can directly interact with the system are those allowed to enter parkings around campus by having an identification device provided by the Politecnico and placed in their car: staff members, teachers, and researchers with a permanent contract seeking for parking spot.

Functional Requirements

Functional Area	Description
1	User login, registration and logout
2	Free spaces identification
3	Smartphone recognition
4	Notifications sent by the system to user smartphone
5	Recognition at parking entrance
6	Greetings and indications
7	Interface for setting user preferences
8	Extra function available in EasyPark

• FR 1.1: Registration
-Description: The user must be able to create an account choosing a personal username and password.
-Priority: 3
• FR 1.2: Session
-Description: The user must be able to login and logout whenever he wants, without losing his previous settings.
-Priority: 2
• FR 2.1: Free spots detection
-Description: The system must know at every moment which are the free spots and which is their position in every single parking lot using the ambient sensors placed in each parking lot.
-Priority: 3
• FR 3.1: Campus Proximity
-Description: The system should be able to recognize when the user is approaching the Politecnico area.
-Priority: 1
• FR 4.1: Starting Advise
-Description: The user must be able to accept or ignore informations about parking availability when he can be tracked by the system.
-Priority: 2
• FR 4.2: List
-Description: Once the user accepts the starting notification, the system must be able to send to the user the list of the availability of all parking lots around the campus.
-Priority: 1
• FR 5.1: Parking Proximity
-Description: When the user arrives to the parking gate, the system must be able to recognize him by his number plate.
-Priority: 2
• FR 6.1: Welcoming
-Description: The system displays on the screen placed at the entrance of the parking lot, a personalized welcome after the number plate recognition.
-Priority: 2
• FR 6.2: Assistant
-Description: The system provides simple directions to the closest vacant parking space on the smartphone and on the parking screen.
-Priority: 3
• FR 7.1: Customized Settings
-Description: The user must be able to set up a specific area in the campus of his preference and always change it.
-Priority: 6
• FR 8.1: "FindMyCar" function
-Description: When the user parks his car, the system saves automatically the latitude and longitude of his position. Then, once the user decides to leave the campus, he can open the app and the system gives him directions to reach his car, using the coordinates saved earlier.
-Priority: 10 (We won't develop FR with priority >5 during this course)

Non-Functional Requirements

• NFR 1: Language
-Description: The language of the system is English
-Area: Usability

• NFR 2: System Working Condition
-Description: The user can only use the system when his smartphone is turned on, has Internet connection and GPS capability.
-Area: Usability

• NFR 3: User Interface
-Description: The user interface must be compatible with Android 4.0 or higher.
-Area: Portability

• NFR 4: Screen Resolution
-Description: The system interface is “responsive” and adapts to screen resolution from 480x800 to 1920x1080.
-Area: Portability

• NFR 5: GPS Restraint
-Description:The user terminal must be able to interact with the GPS system. Without this interaction EasyPark cannot receive all the data needed and it cannot provide to the user information and notifications.
-Area: Interoperability
• NFR 6: Sensors restraint
-Description: The central system must be able to interact at any time with the ambient sensors located in each parking lot. Without this interaction EasyPark cannot elaborates information about the status of the campus parkings.
-Area: Interoperability

• NFR 7: System’s response time
-Description: The system must be able to provide fast notifications to the user as soon as he approaches the “Cittadella Politecnica” and/or a specific parking lot.
-Area: Efficiency

• NFR 8: Frequency
-Description: The system must update the parkings status everytime a user enters or exits a parking lot.
-Area: Efficiency

• NFR 9: Reaction to ambient sensors errors
-Description: If the sensors aren’t working or aren’t able to send data to the central system, it can’t work.
-Area: Reliability
• NFR 10: Reaction to GPS errors
-Description: If the system can't interact with the GPS system, it doesn’t work.
-Area: Reliability

• NFR 11: Reaction to identification error
-Description: If the system can’t identify a user when he is entering a parking lot, it will be unable to provide him further indications.
-Area: Reliability

• NFR 12: Organizational Requirements
-Description: All the software are available on GitHub.
-Area: Implementation

• NFR 13: Organizational Requirements
-Description: The softwares are mostly written in Python with Sql for the databases and Java for the mobile application.
-Area: Implementation