Parking Lot System Design
Department Of Information Technology
Abstract—This term paper is made to provides a better system design as well as better object oriented design using the various ideas and techniques for different types of vehicles and using optimization wherever needed. The paper also depicts the usecases and class diagrams for the Parking system. At the end of the paper there will be an entirely unique approach which will be proposed which can be applied in real world parking systems. (Abstract)
Keywords—scalability, Load balancing, Consistent Hashing, Monoliths, Microservices.(key words)
Recently there has been a great boom in the selling of different types of vehicles in the market. The main reason for this boom is the increasing population of the world and also due to the urbanization and industrialization the space is keeping on decreasing and therefore there should be a proper and organized way of doing things like: parking the vehicles. The transport vehicles cannot be parked anywhere randomly without any monitoring, rulea and at any place and that’s why the paper proposes the solutions so as to upto what extent can the system design be made for the parking of vehicles at a specific place in a specific area so that the problem of parking of vehicles can be reduced to a minimum level. There have been many designs that have recently been come up with, for the proper planning of the parking system but yet there is always a flaw or to be precise there is always some optimizations that can be done in the design itself or some new design with a lot more automation can be deep dived into and a new approach can be taken and can be applied to provide benefits to most of the people. The paper discusses the System design of a parking lot keeping in mind the parameters like: Scalability, Efficiency, Complexity, etc. The following sections will define the usecases, classes and an overall object oriented design of the software for the parking system of the vehicles taking some assumptions about the problem statement.
There are some specifications that can be added to the system design to make it complex but not too complex so that it becomes difficult and costly to build the system in real scenario:
A. Number of levels:
• The parking lot should have the number of different floors or levels for vehicles parking.
B. Entrances and Exits:
• Here an assumption has been made for the parking lot as a large amount of space that should be used for the vehicles and because of this assumption we cannot have only one entrance or exit for the vehicles, as the area that we are talking about is very large.
• Therefore to save the time of the customers and also saving the traffic or possibilities of accidents that can occur for a single entry and exit points of the parking lot, there should be multiple entrances and exit points in the system.
C. Parking Tickets:
• The customers should have many options as far as payment of the parking tickets are concerned like: cash or credit card.
• Further, the customers can pay their tickets at the exit point or to the employee present at the exit or entry of the parking lot.
• The customers should also be having flexibility to pay their parking tickets at the customer information panel and if the said amount is payed by the customer then there should be no amount paid at the exit point.
• There should be a restriction on the number of vehicles in the parking lot. If in case the number of vehicles reach to the maximum count then there should be a message displayed at the entry point of the parking lot that it is full or the message can also be displayed on the Led screens showing the vacant places of parking.
E. Parking Spots:
• There should be the flexibility and particular spots for parking different types of vehicles like: Motorbikes, Cars, trucks and buses.
F. Availability Panel:
• The most important part of this system which is the display panel showing the number of the parking spaces for the different types of vehicles.
• There should be the specific amount of the fees taken from the customers of specific vehicles.
• Each floor of the parking lot should have these panels showing the amount of money for the parking ticket and also the spaces where the vehicles can be parked.
• Different amount of the fees should be charged according to the amount of time the car was in the parking lot. For example 5$ for the first hour and then 3$ for the next 2 hours and 1$ for the rest of the time per hour can be charged for the car.
III. UML REPRESENTATIONS
After the requirements of the systems being established, there is a clear picture of the problem statement with us and therefore now we can proceed towards the identification of the usecases and drawing the various types of diagrams such as: Usecase diagrams, Class diagrams, Activity diagrams.
A. Usecase Diagram
Following are some main actors of our parking lot system design:
• Admin: This usecase is the person who will look after every management activities related to our software like: adding and modifying the parking slots, modifying the price of the parking tickets and also modifying the floors information along with the number of entrances and exit points of the system.
• Customers: The customers usecase will be responsible for demanding the tickets and paying for the parking.
• Parking Enforcement Officer: The parking enforcement officers can have all the functions that a customer has and can also take the money for providing tickets to customers.
• System: Used for displaying the information on the LED panels and also used for removing and adding the parking space for a vehicle.
Following are some of the important usecases for the parking lot system.
a) Add/Remove/Edit parking floor: For adding, removing or modifying the number of the parking floors. Each floor can have the information about the number of parking slots vacant.
b) Add/Remove a parking enforcement officer: For adding, removing and modifying the information about the parking enforcement officers.
c) Take ticket: For providing the customers with the parking ticket..
d) Scan ticket:For scanning the ticket and charging it according to the type of the vehicle and the time duration for which the vehicle was inside the parking lot..
e) Credit card payment: For the payment of the parking ticket by means of the credit cards.
f) Cash payment: For the payment of the parking ticket by means of the Cash.
g) Modify the parking ticket rates: For modifying the parking rates according to the current trends in the markets.
h) Add/Remove/Edit parking spot: A real time system for showing the number of spots where the vehicle can be parked according to the check-ins and checouts of the vehicle.
Fig. 1. Usecase diagram for the Parking Lot System .