ffffproject_removed_merged (1)_pagenumber (1)

IT’S MY PARKING
SYSTEM
A project submitted in partial fulfilment of
requirements for degree of
BACHELOR OF COMPUTER APPLICATION
(CLOUD COMPUTING & CYBERSECURITY)
BY
Sushant Mishra
Roll No: 2166008093
Session: 2021-2024
Under the Supervision of
Dr. Tarun Vashishth
Associate Professor
School of Computer Science & Applications
IIMT UNIVERSITY
‘O’ Pocket, Ganga Nagar Colony,
Mawana Road, Meerut (U.P.), India
1
DECLARATION BY THE CANDIDATE
The Research work embodied in this project entitled

“IT’S MY PARKING SYSTEM” has been carried
out at the “School of Computer Science &
Applications, IIMT University, Meerut, U.P.” The
extent of information derived from the existing
literature has been indicated in the body of the
project at appropriate places along with the source
of information. The work is original and has not
been submitted in part or for nay degree or diploma
of this or any other University.
Date: 10/05/2024 Sushant Mishra

Place: Meerut Roll No: 2166008093
2
CERTIFICATE BY THE SUPERVISOR
This is to certify that the project report entitled

“IT’S MY PARKING SYSTEM” submitted by
Sushant Mishra in partial fulfilment of
requirements for degree of Bachelor of Computer
Application at the “School of Computer Science
& Applications, IIMT University, Meerut, U.P.”
is a record of the candidate own work carried out by
him under my supervision. The matter embodied in
this project is original and has not submitted for the
award of any other degree.
Dr. Tarun Vashishth

Associate Professor
IIMT University Meerut
Dr. Suraj Malik Mrs. Rachna Chaudhary

Dean HOD
IIMT University Meerut IIMT University Meerut
3
ACKNOWLEDGEMENT
I am greatly thankful to Dr. Suraj Malik, Dean School of
Computer Science & Applications IIMT University.
Meerut, U.P. India for providing necessary infrastructure
to carry out my project work at the university. I am
express my sincere thanks and gratitude to Ms. Rachna
Chaudhary, Head School of Computer Science &
Applications IIMT University. Meerut, U.P. India for
her moral support. valuable guidance and
encouragement during the various stages of my work.
I am feeling oblige in taking the opportunity to sincerely
thanks to Dr. Tarun Vashishth, Associate Professor
School of Computer Science & Applications IIMT
University. Meerut, U.P. India for his valuable guidance,
valuable advice and whole heartedly co-operation. His
sincerity, thoroughness, timely help, and constructive
criticism has been a constant source of inspiration for me.
I would also like to acknowledge my parents and friends
for the whole hearted moral support and unending
encouragement they provided me during my project
work.
Date: 10/05/2024 Sushant Mishra

Place: Meerut Roll No: 2166008093
4
ABSTRACT
The project entitled “ItsMyParking” is about providing all the parking facilities to a vehicle
user. One of the important concerns, which is to be taken in accounting is the problem of parking
vehicles. Although, there is space for parking the vehicle but so much time is squandered in
finding that exact parking slot resulting in more fuel intake and not also environment friendly.
ItsMyParking has been developed to override the problems prevailing in practicing the manual
system. Every vehicle owner has faced challenges to overcome and managing the information of
Parking, Car, Parking Slot, Parking Fees, Parking Area. We designed this exclusive parking
management system which can be adapted to organize all the details in one place and also make
proper use of available parking space. This web application is developed to eliminate and, in
some cases, reduce the hardships faced by this existing system. This is developed to provide a
user-friendly experience to the user. No formal knowledge is needed for the user to use this
system. This project is designed to assist in strategic planning, and will help you ensure that your
organization is equipped with the right level of information and details for your future goals.
One of the main differentiators in our project from the other parking providing and parking
management systems is that we let the people register their available space as a parking slot. This
would considerably decrease the parking problem and provide a care free experience to the user.
5
TABLE OF CONTENTS
CHAPTER 1: INTRODUCTION .......................................................................................12
1.1 Project Background....................................................................................... 13
1.2 Problem Statement ........................................................................................ 14
1.3 Objectives ..................................................................................................... 14
1.4 Scope............................................................................................................ 14
1.5 Project Planning ............................................................................................ 15
1.6 Expected Result ............................................................................................ 16
1.7 Motivation Of Work...................................................................................... 16
CHAPTER 2: LITERATURE REVIEW............................................................................. 18
2.1 Parking System Technologies........................................................................ 19
2.2 User Experience And Convenience ............................................................... 19
2.3 Efficient Space Utilization ............................................................................ 19
2.4 Challenges And Limitations ................................................................... 19 - 20
2.5 Case Studies And Implementation Example .................................................. 20

CHAPTER 3 PROPOSED SYSTEM ................................................................................ 21
3.1 Proposed System.......................................................................................... 22

3.2 Modules ....................................................................................................... 23
3.2.1 Registration Module ................................................................................ 24
3.2.2 Space Searching Module......................................................................... 24
3.2.3 Booking Module .................................................................................... 25
3.2.4 Payment Module.................................................................................... 25
3.2.5 Query Module ........................................................................................ 25
6
3.2.6 Previous Bookings Module ..................................................................... 25
3.2.7 About Us Module ................................................................................... 25
3.2.8 Rating Module ........................................................................................ 26
3.3 Requirements Analysis................................................................................. 26
3.3.1 Hardware Requirements.......................................................................... 26
3.3.2 Software Requirements ........................................................................... 26
3.3.2.1 Technologies And Editors Used In This Project ............................... 27
CHAPTER 4 DESIGN AND PLANNING ........................................................................ 28
4.1 Software Development Life Cycle Model..................................................... 29
4.1.1 Waterfall Model ..................................................................................... 29
4.2 Use Case Diagram ................................................................................. 32 - 33
4.3 Entity Relationship Diagram ........................................................................ 33
4.3.1 Entities .................................................................................................... 33
4.3.2 Relationships ........................................................................................... 34
4.3.3 Attributes................................................................................................. 34
4.4 DFD ............................................................................................................ 36
4.4.1 Zero-Level DFD ...................................................................................... 36

4.4.2 First-Level DFD ..................................................................................... 37
4.4.2.1 Main Entities And Output Of First Level DFD ....................................... 38

4.4.3 Second-Level DFD .................................................................................. 39
4.4.3.1 Low Level Functionalities Of Online Car Parking System ............... 39
4.4 Flow Chart ............................................................................................. 40 - 41
CHAPTER 5 SURVEY OF TECHNOLOGIES ................................................................. 42
5.1 Html ............................................................................................................ 43
5.2 Cascading Style Sheet .................................................................................. 43
7
5.3 Javascript ..................................................................................................... 43
5.4 Rest Api....................................................................................................... 43
5.5 Django ......................................................................................................... 44
5.6 Heroku......................................................................................................... 44
CHAPTER 6 CODING ..................................................................................................... 45
6.1 Html file ................................................................................................ 46 - 57
6.2 Css file ................................................................................................... 57 - 63
6.3 JavaScript file ........................................................................................ 63 - 64
6.4 Backend File .......................................................................................... 65 - 68
CHAPTER 7 TESTING .....................................................................................................69
7.1 Unit Testing ................................................................................................. 70
7.1.1 Benefits ............................................................................................. 70 - 71
7.2 Integration Testing ................................................................................. 71 - 72
7.2.1.1 Big Bang Approach .......................................................................... 72
7.2.1.2 Top-Down And Bottom-Up Approach........................................ 72 - 73
7.3 Software Verification And Validation .................................................... 73 - 74
7.4 Black-Box Testing ....................................................................................... 74

7.5 White-Box Testing ....................................................................................... 75
7.5.1 Levels .................................................................................................... 75

7.6 System Testing .............................................................................................76
CHAPTER 8 IMPLEMENTATIONS AND RESULTS ..................................................... 77
8.1 Homepage.................................................................................................... 78
8.2 Registration Page ......................................................................................... 79
8.3 Login Page ............................................................................................. 79 - 80
8.4 Payment Gateway Interface .......................................................................... 80
8
8.5 Login Page For Admin ................................................................................. 81
8.6 Space Register Homepage............................................................................ 82
8.7 Space Registration Form .............................................................................. 83
8.8 Contact Us Interface .....................................................................................83
8.9 About Us Page ............................................................................................ 84
CHAPTER 9 CONCLUSION AND FUTURE WORKS ................................................... 85
9.1 Conclusion ................................................................................................... 86
9.2 Various Project Constraint And Limitation................................................... 87
9.2.1 Technical Limitations ............................................................................ 87
9.2.2 User Adoption And Behavior ........................................................... 87 - 88
9.2.3 Privacy And Security Concerns.............................................................. 88
9.2.4 Scalability And System Performance ..................................................... 88
9.2.5 Financial Constraints........................................................................ 88 - 89
9.3 Various Future Works ............................................................................ 89 - 91
9.4 Summary ............................................................................................... 91 - 92
REFERENCES AND BIBLIOGRAPHY........................................................................... 93
References ............................................................................................................ 94
9
LIST OF FIGURES
Figure 3.1: Proposed System ............................................................................................. 23
Figure 4.1: Waterfall Model .............................................................................................. 30
Figure 4.2: Use Case Diagram ........................................................................................... 31
Figure 4.3: Entity Relationship Diagram............................................................................ 35
Figure 4.4: Zero Level DFD .............................................................................................. 36
Figure 4.5: First Level DFD .............................................................................................. 38
Figure 4.6: Second Level DFD .......................................................................................... 39
Figure 4.7: Flow Chart ...................................................................................................... 41
Figure 8.1 Homepage viewed by all users (Admin and User) ............................................. 78
Figure 8.2: Registration Page ............................................................................................ 79
Figure 8.3 Login Page ....................................................................................................... 79
Figure 8.4: Payment Gateway Interface ............................................................................. 80
Figure 8.5: Login page for admin ....................................................................................... 81
Figure 8.6 Space Register HomePage ................................................................................ 82
Figure 8.7 Space Registration Form ................................................................................... 83
Figure 8.9: About Us Section ............................................................................................ 84
10
LIST OF ABBREVIATIONS
S.No. ABBREVIATIONS FULL FORM
1. API Application Programming Interface
2. ORM Object Relational Mapping
3. UPI Unified Payments Interface
4. GPS Geographical Positioning System
5. App. Application
6. MVT Model-View-Template
7. DSF Django Software Foundation
8. PaaS Platform as a Service
11
CHAPTER 1
INTRODUCTION
12
1.1 PROJECT BACKGROUND
The recent growth in economy and due to the availability of low price cars in the market.
Every average middle-class individual can afford a car, which is good thing, however the
consequences of heavy traffic jams, pollution, less availability of roads and spot to drive the
motor car. Not finding a parking space for you sometimes is indeed a critical issue. Over the
years, the demand for parking has increased, and the traditional parking methods have
become outdated and inefficient. The task of finding a parking spot has also become a
challenging work. Sometimes the space is not even available to park the vehicle.
Over the years, the demand for parking has increased, and the traditional parking
methods are becoming less and less efficient. This has led to the development of advanced
parking systems that leverages technology to provide smart and innovative solutions to the
parking industry. A parking system can be viewed as a solution to the challenges associated
with limited parking spaces, especially in urban areas. The parking system projects are
aimed at developing an efficient parking system that can improve the overall parking
experience for customers.
An important appointment might be missed, Time will be wasted and more money will
be spent. Criticism and inconvenience are more likely to happen. This has led to the
development of significant strategies for deploying a parking systems that leverages
technology to provide smart and innovative solutions to the parking industry. So, a way to
perform parking management is an important solution. It has many practical advantages. It
can arrange the passage of vehicles inside the parking area in addition to avoiding
contention. It can reduce the suffering of sick and disabled people looking for a parking
space. It is a good denote to such part of the society. It is like providing them with the smile
and hope that helps them to overcome their disability.
1.2 PROBLEM STATEMENT

Develop a parking system whose main task would be to provide a parking space to vehicle
drivers in the nearby area of their preferred location. The selection of the parking area,
booking of the time slot, and payment, all will be done on our web application using the
person’s mobile number. The user can also check any previous bookings made with the
same mobile number. The people who have adequate space available for parking can
register it on our web application which can then be verified and listed on our web
13
application in order to solve the problem of not having enough parking space.
1.3 OBJECTIVES
 To utilize the free available space of the owner.
 To make a parking space available for the user.
 To design a user-friendly web application that would help in creating a better user
experience for the user without having a prior knowledge.
 To enable drivers to locate and reserve a parking place online through accessing it on
our web platform.
1.4 SCOPE
The purpose of this project is to locate space for a user to park their car. This would make
the parking process easier. The problem of contention on streets will reduce. People can
also save their vehicle from getting towed. The people who have space available for them
for vehicle parking can also utilize their space. This would solve the space problem for
parking. The user does not have to get into the trouble of paying extra or an unfair amount
as it will have all the fair pricing listed according to the time period they book the slot for. It
would create a convenient experience for the user and would make them hook to our
services. It can later include a subscription based model where the user can get special
bonuses with our premium. This would also impact the user as they will get premium
services at an affordable rate. The people who have adequate space available for parking
can register it on our web application which can then be verified and listed on our web
application in order to solve the problem of not having enough parking space. This can also
be beneficial for the land owner because a big chunk of the revenue generated by booking
the parking space will be provided to them. The user can also check any previous bookings
made with the same mobile number. The people who have adequate space available for
parking can register it on our web application which can then be verified and listed on our
web application in order to solve the problem of not having enough parking space. This will
lead to the benefit of both the parties which are the normal user who is looking for a place
to park their vehicle and the owner who has the free space available.
14
1.5 PROJECT PLANNING
With the help of this below given Gantt Chart it can be analyzed that the working of this
project is distributed over time for 7 weeks. The first five days were taken into the project
initialization where brainstorming was done about how to approach the project. Then started
the project planning. Here it has accumulated the details about the requirements and the
tools needed to execute this project. After that the project execution started which includes
all the coding and developing steps. After that performance of the project was evaluated
where it was tested. Finally the projecct reached the closure where it was finalized and
made improvements in the performance of the project.
Gantt Chart
1-Apr 11-Apr Du2r1a-tAiporn 1-May 11-May 21-May
Project Initialization
Project Planning
Tasks
Project Execution
Project Performance and Control
Project Closure
Figure 1.1 : Gantt Chart
15
1.6 EXPECTED RESULT
The expected result from this project is a more efficient and convenient parking experience
for both providers and users. With this system in place, individuals who have available
parking spaces can easily list and manage them through a user-friendly platform. This
would lead to increased utilization of existing parking resources and potentially reduce the
need for constructing additional parking structures.
For users seeking parking spaces, the system would provide a comprehensive database
of registered parking slots, enabling them to find and reserve parking in advance. This
would minimize the time spent searching for parking and reduce traffic congestion caused
by vehicles circling around in search of an available spot. Moreover, the system could offer
features such as automated payment, navigation to the reserved spot, and real-time updates
on parking availability, enhancing the overall user experience.
Ultimately, the expected result of this project is a more efficient use of parking
resources, reduced congestion, improved traffic flow, and enhanced convenience for both
parking providers and users. The system has the potential to transform the parking
landscape, making it more organized, accessible, and sustainable.
1.7 MOTIVATION OF WORK

Developing a parking management system presents an array of motivating factors. Firstly,
such a system aims to address the growing challenges faced by urban areas regarding
parking space utilization. With increasing population densities and limited parking
infrastructure, the need for an efficient and intelligent solution becomes crucial. The
motivation lies in creating a system that optimizes parking space allocation, reduces
congestion, and enhances overall user experience. By implementing a parking management
system, cities can achieve improved traffic flow, reduced carbon emissions, and enhanced
safety for both pedestrians and drivers.
Secondly, the motivation for working on a parking management project stems from the
potential for significant societal impact. A well-designed system has the power to
revolutionize the way people access and utilize parking spaces. By leveraging technologies
such as sensors, data analytics, and mobile applications, the project can enable real-time
parking availability updates, seamless payment methods, and efficient parking enforcement.
This not only streamlines the parking process for individuals but also contributes to the
16
larger goal of building smarter and more sustainable cities. The positive impact on urban
mobility, environmental conservation, and overall quality of life makes the work on a
parking management system project highly motivating and fulfilling.
17
CHAPTER 2
LITERATURE REVIEW
18
In recent years, parking congestion has become a prevalent issue in urban areas, leading to
increased demand for innovative parking solutions. User-configurable parking systems, which
enable users to set their own parking slots, have emerged as a promising approach to address
this challenge. This literature review aims to explore the existing knowledge, research, and
developments related to user-configurable parking systems.
2.1 PARKING SYSTEM TECHNOLOGIES

Several technologies have been employed in parking systems, including sensors, mobile
applications, and IoT devices. Smart parking sensors can detect the availability of parking
spaces, while mobile applications provide real-time information to users. IoT devices, such as
smart parking meters, enable users to configure and reserve their parking slots remotely.
2.2 USER EXPERIENCE AND CONVENIENCE

User-configurable parking systems offer enhanced user experience and convenience. By
allowing users to reserve their own parking slots, these systems eliminate the need for time-
consuming searches and reduce the frustration associated with finding an available space.
Studies have shown that such systems can significantly improve user satisfaction and reduce
parking-related stress.
2.3 EFFICIENT SPACE UTILIZATION

User-configurable parking systems can optimize the utilization of parking spaces. Through
real-time data collection and analysis, these systems can provide valuable insights into parking
patterns and usage. This information can be utilized to efficiently allocate parking resources,
reduce idle time, and maximize the utilization of available spaces.
2.4 CHALLENGES AND LIMITATIONS

Despite their benefits, user-configurable parking systems face certain challenges and
limitations. One major concern is the potential for abuse or misuse of the system, where users
19
may reserve parking slots without actually using them, leading to wasted resources.
Additionally, there may be technical limitations, such as connectivity issues or compatibility
problems with existing infrastructure. Addressing these challenges requires careful planning,
robust security measures, and effective system maintenance.
2.5 CASE STUDIES AND IMPLEMENTATION EXAMPLE

Numerous case studies and implementation examples showcase the effectiveness of user-
configurable parking systems. For instance, projects in smart cities like Barcelona, San
Francisco, and Singapore have successfully implemented user-configurable parking systems,
leading to improved parking management, reduced traffic congestion, and enhanced user
experience. These real-world examples highlight the feasibility and positive outcomes of
implementing such systems.
In conclusion, user-configurable parking systems hold great potential in addressing parking

congestion and improving the overall parking experience. They offer benefits such as enhanced
user convenience, efficient space utilization, and data-driven decision-making. However,
challenges related to system abuse, technical limitations, and security need to be carefully
addressed. Future research should focus on refining the implementation processes, evaluating
system performance, and further exploring the integration of emerging technologies to optimize
user-configurable parking systems.
20
CHAPTER 3
PROPOSED SYSTEM
21
3.1 PROPOSED SYSTEM
A parking management system is an essential tool for managing the parking needs of a modern
city. In today's world, where population and vehicle ownership are constantly increasing,
parking management systems can provide a seamless and efficient solution to the parking
problems faced by people. The proposed system aims to provide an easy-to-use and accessible
platform for both vehicle owners and parking space owners.
The proposed parking management system will allow vehicle owners to search for
available parking slots in their vicinity and book them through the platform. It will also allow
parking space owners to register their spaces as available parking slots on the platform. In
addition, the system will include a payment system, which will allow vehicle owners to pay for
the parking slot they have booked through the platform.
The system will have a user-friendly interface, which will allow vehicle owners to search
for available parking slots in their vicinity. They will be able to filter their search based on
various criteria, such as location, price, availability, and distance. Once they find a suitable
parking slot, they can book it through the platform, and the payment will be deducted from
their registered payment method.
Similarly, parking space owners can register their parking slots on the platform by
providing necessary details such as location, price, and availability. They will be able to
manage their parking slots and update their availability through the platform. The platform will
also provide parking space owners with an overview of their earnings and usage statistics.
The payment system integrated into the platform will ensure that the payment process is
secure and seamless for both vehicle owners and parking space owners. The payment system
will allow vehicle owners to add their preferred payment method, such as credit or debit cards,
PayPal, or other payment gateways. The payment system will automatically deduct the
payment from the vehicle owner's account once the parking slot is booked.
In addition to the payment system, the platform will also include a slot booking system,
which will ensure that the parking slots are allocated to the vehicle owners who have booked
them. The slot booking system will prevent double booking and ensure that the parking slots
are available for the booked period. The system will also send reminders and notifications to
both vehicle owners and parking space owners about the booking details and payment status.
22
The proposed parking management system will have many advantages for both vehicle
owners and parking space owners. For vehicle owners, it will provide an easy-to-use platform
for finding available parking slots, booking them, and making payments. It will also ensure that
the parking slots are allocated to the vehicle owners who have booked them, preventing double
booking and reducing frustration.
For parking space owners, the platform will provide a hassle-free way of managing their
parking slots, updating their availability, and monitoring their earnings. It will also allow them
to reach a wider audience and increase their revenue by registering their parking slots on the
platform.
In conclusion, the proposed parking management system will provide an efficient and
effective solution to the parking problems faced by vehicle owners in modern cities. It will
provide a user-friendly platform for finding and booking parking slots, a secure payment
system for making payments, and a slot booking system to ensure that parking slots are
allocated to the vehicle owners who have booked them. The system will benefit both vehicle
owners and parking space owners by providing a seamless and efficient parking management
solution.
Figure 3.1: Proposed System
23
1- User Searches for available space through web application.
2- Web application sends request to book the parking slot.
3- Response comes from parking slot to web application.
4- User gets confirmation of booking.
5- Owner registers parking space through web application.
6- Parking slot is created.
7- After verification, the parking slot is registered.
3.2 MODULES
This project has been partitioned to do this whole task into different smaller modules as
indicated by their working and utilization of these as per the following:
3.2.1 REGISTRATION MODULE
The initial step for utilizing this service is the enlistment structure where the client will request
a login or information exchange. This module will include the registration criteria for two
kinds of client. The primary client for our project is the one who needs a parking space. This
can implement an email based registration so that the whole process of booking the parking
would become easier. The secondary client for our project is the one who wants to register their
space for vehicle parking. Here we would require all the proper information about the client
and the space they are providing.
3.2.2 SPACE SEARCHING MODULE
After the user completed the registration they will be forwarded to a new page where they will
search for a nearby available place to park their vehicle. Here it will use the user’s location to
display the available spaces in the nearby area. The customer can select one and then head for
the booking system.
24
3.2.3 BOOKING MODULE
In this module the customer will be provided with booking options. This module will include
selection of the time slot for their parking. This module is quite important as it would show the
vehicle driver which slots for a particular space are available. The parking schedule at a single
place can have a certain gap in between two consecutive slots that would make it easier to
manage the parking process.
3.2.4 PAYMENT MODULE
In payment module the customer can pay the fare according to the time of the booking slot. To
add more value for the user we can also provide some offers or plans in this module. This can
be done by allotting coupon codes. The payment can be done through any common method like
UPI, net banking or credit/debit cards.
3.2.5 QUERY MODULE
In this module the customer can drop a query to the admin of the website in case they face any
difficulty or problem while using the website. The customers can contact through the Email
address, helpline numbers, and by other means.
3.2.6 PREVIOUS BOOKINGS MODULE
This module can be accessed by a user only after logging into their account. This module will
provide all the bookings that were previously done on the basis of their phone number. This
module will include the booking id, date and time slot.
3.2.7 ABOUT US MODULE
In this module the user will get to know about the working, agenda as well as the manner in
which it works so that it can easily build the trust. Apart from that, this module will be
delivering the information regarding the website which will play a very important role to
engage the audience.
25
3.2.8 RATING MODULE
This is the module which would allow the users to give ratings to our services. This is an
optional module where the customer can choose to rate our services or not. The customers will
be capable of providing ratings out of 5 and then provide a remark on that. If the customer
faces any difficulties they can simply provide rating at our rating module and it can then be
considered while self-evaluation and improving services sessions are held.
3.3 REQUIREMENTS ANALYSIS

The requirement analysis includes two main requirements which are hardware requirements
and software requirements.
3.3.1 HARDWARE REQUIREMENTS
This project will be a web based web application, so the user doesn’t need to install any extra
software hardware requirements to operate this website at the user side Usage of CPU, RAM,
and storage space can vary significantly based on user behavior. These hardware
recommendations are based on traditional deployments and may grow or shrink depending on
how active your users are:
 Processor : Pentium 4
 RAM : 512 Mb or above
 Input Device : Keyboard and Mouse
 Output Device : Monitor or PC, Mobile Screen
3.3.2 SOFTWARE REQUIREMENTS
Minimum software requirement to operate this website at the user side. The most common set
of requirements defined by any operating system or software application is the physical
computer resources, also known as hardware are:
 Operating System: Windows10 or Higher Versions

 Browser: Opera GX, Google Chrome, IE 10.0 or late
26
3.3.2.1 TECHNOLOGIES AND EDITORS USED IN THIS PROJECT
 Database: SQLite
 IDE: Visual Studio(1.74 version)
 Documentation Tool: WPS office
 Front End: HTML, CSS, JavaScript, REST API
 Back End: Django(4.0) , JSON
 Domain Provider: GoDaddy
 Hosting Server: Heroku
Based on this chapter, the methodology used for the project has been elaborated. The system
requirements that will be used for this project also have been stated. Methodology used for
system is acrucial part to ensure that the system start off at a great pace. It is important in order
to fulfill the user’s requirement and activities timeline. It helps us in categorizing the main
functions and features of the project and how to deal with complex problems in a step by step
process.
27
CHAPTER 4
DESIGN AND
PLANNING
28
4.1 SOFTWARE DEVELOPMENT LIFE CYCLE MODEL
Software Development Life Cycle (SDLC) is a process used by the software industry to design,
develop and test high quality software. The SDLC aims to produce a high-quality software that
meets or exceeds customer expectations, reaches completion within times and cost estimates.
SDLC is a process followed for a software project, within a software organization. It consists of
a detailed plan describing how to develop, maintain, replace and alter or enhance specific
software. The life cycle defines a methodology for improving the quality of software and the
overall development process.
4.1.1 WATERFALL MODEL
The waterfall Model illustrates the software development process in a linear sequential flow.
This means that any phase in the development process begins only if the previous phase is
complete. In this waterfall model, the phases do not overlap. Waterfall approach was first
SDLC Model to be used widely in Software Engineering to ensure success of the project. In
"The Waterfall" approach, the whole process of software development is divided into separate
phases. In this Waterfall model, typically, the outcome of one phase acts as the input for the
next phase sequentially. The advantages of waterfall development are that it allows for
departmentalization and control. A schedule can be set with deadlines for each stage of
development and a product can proceed through the development process model phases one by
one. Development moves from concept, through design, implementation, testing, installation,
troubleshooting, and ends up at operation and maintenance. Each phase of development
proceeds in strict order. The waterfall model was selected as the SDLC model due to the
following reasons:
• Requirements were very well documented, clear and fixed.
• Technology was adequately understood.
• Simple and easy to understand and use.
• There were no ambiguous requirements.
• Easy to manage due to the rigidity of the model. Each phase has specific deliverables and a
review process.
29
• Clearly defined stages.
• Well understood milestones. Easy to arrange tasks.
Figure 4.1: Waterfall Model

The waterfall model is very simple to understand and use. In a waterfall model, each phase
must be completed before the next phase can begin and there is no overlapping in the phases.
The Waterfall model is the earliest SDLC approach that was used for software
development. The waterfall Model illustrates the software development process in a linear
sequential flow. This means that any phase in the development process begins only if the
previous phase is complete. In this waterfall model, the phases do not overlap.
Due to the quality of waterfall model to being a step by step process through which we can
focus on the project in a step by step manner. This will also lead to a simple and efficient
approach to the development of this project.
30
4.2 USE CASE DIAGRAM
Figure 4.2: Use Case Diagram

A user case diagram is a type of UML (Unified Modeling Language) diagram that shows the
actors involved in a system, the actions they perform, and the system's responses to those
actions. In the context of a parking management system that allows users to register their
available parking spaces, the user case diagram would depict the different users and their
interactions with the system.
There are three main actors in the parking management system: the user, the parking space
31
owner, and the administrator. The user is the person who wants to find and reserve a parking
space, the parking space owner is the person who wants to register their available parking
spaces, and the administrator is the person who manages the system and handles any issues that
arise.
The user can perform several actions on the system, including searching for available
parking spaces, selecting a parking space, making a reservation, and canceling a reservation.
The parking space owner can perform actions such as registering a parking space, updating the
availability of a parking space, and deleting a parking space. The administrator can perform
actions such as managing user accounts, managing parking space listings, and resolving
disputes between users.
To illustrate these interactions, we can create a user case diagram that includes the actors,
their actions, and the system's responses. The diagram would include two entities, one
representing the user and parking space owner, and other representing the administrator. Each
oval would have a list of actions the actor can perform, represented by rectangular boxes. The
actions would be connected to the entity by lines to indicate which actor is performing the
action.
For example, the user would have actions such as "Search for available parking spaces,"
"Select a parking space," "Make a reservation," and "Cancel a reservation." The parking space
owner would have actions such as "Register a parking space," "Update availability," and
"Delete a parking space." The administrator would have actions such as "Manage user
accounts," "Manage parking space listings," and "Resolve disputes."
Overall, the user case diagram provides a visual representation of the interactions between
the different actors and the system. It helps to clarify the system's functionality and provides a
starting point for further development and refinement. By identifying the different actors and
their actions, we can ensure that the system meets the needs of all users and provides a
seamless experience for everyone involved.
4.3 ENTITY RELATIONSHIP DIAGRAM

An entity-relationship diagram (ERD) is a visual representation of the entities, attributes, and
32
relationships involved in a system. In the case of a parking management system, an ERD can
help to identify the entities involved, their attributes, and how they relate to one another. The
following is a detailed explanation of the ERD for the proposed parking management system.
4.3.1 ENTITIES
1. User: The User entity represents a person who interacts with the parking management
system. The User entity has the following attributes: User ID, Name, Email and Password.
2. Parking Space: The Parking Space entity represents a physical parking slot that is available
for booking. The Parking Space entity has the following attributes: Space ID, Name, Location,
Price, Availability, and Owner ID.
3. Booking: The Booking entity represents a parking slot that has been booked by a user. The
Booking entity has the following attributes: Booking ID, User ID, Space ID, Start Time, and
End Time.
4. Admin: The Admin entity represents the administrator that will manage this system. It will
have attributes, AdminID, Email and Password. The admin can view the list of all the parking
slots that are available and that are booked, the car related details and the new parking spaces
added.
5. Account: The account holds all the details about the user. The main distinction that the
account holds is whether the account holder is a normal user or a parking place owner. This
Entity will include the AccountID, and user details like name, phone number, etc.
6. Payment: The payment entity holds all the records of the payment that is done by the user
for booking the parking slot for their vehicle. It includes the PaymentID as the primary key and
UserID as a foreign key. It also includes the BookingID and some car details.
7. Car Parked: It includes all the details about the vehicles which are currently parked and all
the parking slots that are reserved for parking. This system is updated in real-time and is
managed by the admin.
8. Parking Slot: This entity represents the slot that is booked by the user for their vehicle.It
includes attributes like the UserID, ParkingSpaceID, and Location.
33
4.3.2 RELATIONSHIPS
 A User can book many Parking Spaces, but a Parking Space can be booked by many Users.
This is a many-to-many relationship between User and Parking Space entities, represented
by the Booking entity.
 A User can have many Payment Methods, but a Payment Method can be associated with
only one User. This is a one-to-many relationship between User and Payment Method
entities.
 A Parking Space can have only one Owner, but an Owner can own many Parking Spaces.
This is a one-to-many relationship between Parking Space and User entities, where the User
entity acts as the Owner.
4.3.3 ATTRIBUTES
1. User ID: A unique identifier for each User entity in the system.
2. Name: The name of the user.
3. Email: The email address of the user, used for communication and account verification.
4. Password: The password associated with the user's account, used for authentication and
security.
5. Payment Method: The payment method associated with the user's account, such as credit or
debit card, PayPal, or other payment gateways.
6. Space ID: A unique identifier for each Parking Space entity in the system.
7. Name: The name of the parking space.
8. Location: The location of the parking space, such as an address or GPS coordinates.
9. Price: The price of the parking space per hour or per day.
10. Availability: The availability status of the parking space, such as available or unavailable.
11. Owner ID: The User ID of the owner of the parking space.
12. Booking ID: A unique identifier for each Booking entity in the system.
13. Start Time: The starting time of the booked slot.
34
14. End Time: The ending time of the booked slot.
15. PhoneNumber: This attribute will contain the phone number of the user.
The above entities, relationships, and attributes form the basis of the proposed parking
management system's ERD. The ERD can be used as a reference for developing the system's
database schema, which will enable the system to store, retrieve, and manipulate data
efficiently. The ERD will also help to ensure data integrity, consistency, and accuracy, which
are critical for the success of the system.
Figure 4.3: Entity Relationship Diagram
35
4.4 DFD
This section includes the data flow diagrams which are necessary to define and understand this
project.
4.4.1 ZERO-LEVEL DFD
Figure 4.4: Zero Level DFD

This is the Zero level Data Flow Diagram of ItsMyParking system, where we have elaborated
the high level process of vehicle parking. It is a basic overview of the whole system, how the
processes are being organized and modelled. A zero level data flow diagram (DFD) is the
highest level of abstraction in the process modeling of a system. It provides an overview of the
entire system, showing the inputs, processes, and outputs at a high level. In this case, we will be
creating a zero level DFD for a parking management system that allows users to register their
available parking spaces.
At the highest level, we begin by assuming that this parking management system has two
main inputs: user information and available parking space information. User information can
36
include data such as name, contact information, and payment details. Available parking space
information can include data such as location, size, and availability.
The processes in the system include user registration, parking space registration, and
parking reservation. The user registration process allows users to create an account and enter
their personal information. The parking space registration process allows users to register their
available parking spaces, including location and other details. The parking reservation process
allows users to search for and reserve available parking spaces.
The outputs of the system include user profiles, parking space listings, and reservation
confirmations. User profiles contain information about the user, including their personal
information and parking history. Parking space listings show available parking spaces in a
particular location, along with their details. Reservation confirmations provide users with
information about their reserved parking space, including the location and payment details.
Overall, the zero level DFD for the parking management system that allows users to
register their available parking spaces is a simple but effective way to visualize the inputs,
processes, and outputs of the system. By breaking down the system into its component parts,
we can better understand how the system works and identify potential areas for improvement.
4.4.2 FIRST-LEVEL DFD
First Level Data Flow Diagram(1st Level DFD) Of Online Car Parking System : First Level
DFD (1st Level) of Online Car Parking System shows how the system is divided into sub-
systems (processes), each of which deals with one or more of the data flows to or from an
external agent, and which together provide all of the functionality of the Online Car Parking
System system as a whole. It also identifies internal data stores of Car Number, Car Owner,
Parking Fees, Parking Slots, Parking Space that must be present in order for the Car Parking
system to do its job, and shows the flow of data between the various parts of Car, Parking
Space, Car Owner, Car Number, Parking Fees of the system. DFD Level 1 provides a more
detailed breakout of pieces of the 1st level DFD. You will highlight the main functionalities of
Car Parking.
37
Figure 4.5: First Level DFD
4.4.2.1 MAIN ENTITIES AND OUTPUT OF FIRST LEVEL DFD (1ST LEVEL DFD)
 Processing Car records and generate report of all Car
 Processing Parking records and generate report of all Parking
 Processing Parking Space records and generate report of all Parking Space
 Processing Parking Slots records and generate report of all Parking Slots
 Processing Parking Fees records and generate report of all Parking Fees
 Processing Car Owner records and generate report of all Car Owner
 Processing Car Number records and generate report of all Car Number
38
4.4.3 SECOND-LEVEL DFD
Figure 4.6: Second Level DFD

DFD Level 2 then goes one step deeper into parts of Level 1 of Car Parking. It may require
more functionalities of Car Parking to reach the necessary level of detail about the Car Parking
functioning. First Level DFD (1st Level) of Online Car Parking System shows how the system
is divided into subsystems (processes). The 2nd Level DFD contains more details of Car
Number, Car Owner, Parking Fees, Parking Slots, Parking Space, Parking, Car.
4.4.3.1 LOW LEVEL FUNCTIONALITIES OF ONLINE CAR PARKING SYSTEM
 Admin logins to the system and manage all the functionalities of Online Car Parking
39
System Admin can add, edit, delete and view the records of Car, Parking Space, Parking
Fees, Car Number
 Admin can manage all the details of Parking, Parking Slots, Car Owner
 Admin can also generate reports of Car, Parking, Parking Space, Parking Slots, Parking
Fees, Car Owner
 Admin can search the details of Parking, Parking Fees, Car Owner
 Admin can apply different level of filters on report of Car, Parking Slots, Parking Fees
 Admin can tracks the detailed information of Parking, Parking Space, Parking Slots,
Parking Fees
4.4 FLOW CHART

Firstly, the user opens the web application. If it’s a new user then the user will register
otherwise they will login into the account. If the login id and password matches the user is
granted access otherwise a message of invalid id or password is displayed. After that the web
application tracks the location of the user through GPS. The web application shows the nearby
available parking slots. The user can search for a particular slot in the area and the website will
show its availability status. The available slots will be colored green otherwise red. If the slot is
available for parking then the user is allowed to book it, otherwise for the reserved ones the
user won’t be able to book it. After selection of the parking space, the user selects the time slot
for the parking space booking. The booking process is then complete. The user then pays for
the booking through an online transaction method like UPI, net banking, etc. If the payment is
not successful, a message is sent to the user on the email or the mobile number. After
successful payment, the timer starts at the start of the booking time slot. User can then park the
vehicle on the parking space. If the timer exceeds then the user cannot park their vehicle. The
parking is then shown available for the next booking. The user can also search for particular
parking spaces which has the same process of booking with the web application and then same
payment methods are applied. If the user leaves before the end of the time slot then no refund is
provided to the user. The user can then leave a review on our rating page which is an optional
step.
40
Figure 4.7: Flow Chart
41
CHAPTER 5
SURVEY OF
TECHNOLOGIES
42
In this project, different kinds of advances will be going to utilize some of them are web
technology, and some of them are customizing dialects likewise, data sets, and a local server
for hosting at default IP address 127.0.0.1:8000. All the technologies which are going to be
used in this project are mentioned below.
5.1 HTML
It is known as Hyper Text Mark-up Language. It describes the structure of the web page. It
provides information in the document by denoting certain text as links, heading, paragraph, list
and so on. It is written in the form of tags, surrounded by angle brackets.
5.2 CASCADING STYLE SHEET

CSS, an initialize of Cascading Style Sheet, is a simple designing language for the web page. It
is used to make the process of making the web page presentable in a simplified manner. The
functionalities provided by CSS are one can control the text colour, font style, layout and size
of columns, display variations for different devices and screen size, space between paragraphs,
layout, designs, colour and background images.
5.3 JAVASCRIPT
It is a text-based programming language which is utilized for both client side and server side. It
allows making interactive web pages. It helps in making static HTML web pages into dynamic
and interactive one.
5.4 REST API

A REST API is a way for two computer systems to communicate using the HTTP technologies
found in the web browsers and servers. Sharing data between two or more systems has always
been a fundamental requirement of software development. One of the key advantages of REST
APIs is that they provide a great deal of flexibility. Data is not tied to resources or methods, so
REST can handle multiple types of calls, return different data formats and even change
43
structurally with the correct implementation of hypermedia.
5.5 DJANGO
Django is a free and open-source, Python-based web framework that follows the model - view -
template(MVT) architectural pattern. Another is maintained by the Django Software
Foundation (DSF),an independent organization established in the US as a non-profit
organization. The framework emphasizes reusability and "pliability" of components, less code,
low coupling, rapid development, and the principle of don't repeat yourself. Python is used
throughout, even for settings, files, and data models.
5.6 HEROKU
Heroku is a platform as a service (PaaS) that enables developers to build, run, and operate
applications entirely in the cloud. It is multi-platform and is supported through many operating
systems such as Windows, Mac-OS, and linux.
44
CHAPTER 6
CODING
45
6.1 HTML FILE
<!DOCTYPE html>
{% load static %}
<html lang="en" style="scroll-behavior: smooth">
<head>
<meta charset="UTF-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="viewport" content="width=\, initial-scale=1.0" />
<link rel="icon" href="{% static 'image/icon.png' %}" />
<title>About Us</title>
<link rel="stylesheet" href="{% static 'css/style.css' %}" />
<link rel="stylesheet" href="{% static 'css/responsive.css' %}" />
<link rel="stylesheet" href="{% static 'css/about.css' %}" />
<link
rel="stylesheet"
href="https://unpkg.com/swiper/swiper-bundle.min.css"
/>
<link
rel="stylesheet"
href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.4.0/css/all.min.css"
/>
</head>
<body>
<div class="container">
{% include "header.html" %}
<div class="section">
<div class="about-heading">
<h1>ABOUT US</h1>
</div>
<div class="content-about">
<p>We are a team of 3 people with an ambition to change the world. This project is
currently being submitted as a pre-requisite to our Bachelor's degree. We prepared this web
application in order to server the people and provide then a better experience in dealing with
problems related to parking and its management. We are also planning to launch this product
into the marking in order to really make a change in the society. We have dedicated ourselves
into this project. Hope you will enjoy the conveniences it provides. If you face any
46
inconveniences then feel free to contact us through the Contact Us page and we will surely take
action about it. If you have a suggestion then also you can send your ideas through the Contact
Us page.</p>
</div>
<div class="wave">
</div>
</div>
{% include "footer.html" %}
</div>
<script src="{% static 'js/script.js' %}"></script>
<script src="{% static 'js/script.js' %}"></script>
<script
src="https://kit.fontawesome.com/782de0499d.js"
crossorigin="anonymous"
></script>
<script src="https://unpkg.com/swiper/swiper-bundle.min.js"></script>
</body>
</html>
//Contact.html
<!DOCTYPE html>
<html lang="en" style="scroll-behavior: smooth; height: 100%;">
<head>
<link rel="icon" href="/assets/img/icon.png" />
<title>itsmyparking</title>
<link rel="stylesheet" href="/assets/css/style.css" />
<link rel="stylesheet" href="/assets/css/responsive.css" />
<link rel="stylesheet" href="/assets/css/contact.css">
<link
rel="stylesheet"
/>
<link
rel="stylesheet"
47
/>
</head>
<body>
<nav class="navbar">
<a href="/index.html" class="logo">Its<span class="red">My</span>Parking</a>
<ul>
<li><a href="index.html" class="bottom_bar">Home</a></li>
<li><a href="about.html" class="bottom_bar">About</a></li>
<li>
<div class="dropdown">
<button class="drop_btn">
Services
<i class="fa-solid fa-caret-down" style="color: #e1fffd"></i>
</button>
</li>
<li><a href="/contact.html" class="bottom_bar">Contacts</a></li>
</ul>
<div class="log_btn" id="register-system">

<button class="register_btn" id="logButton"><a href="login.html">Log In</a></button>
<button class="register_btn" id="signButton"><a href="register.html">Sign
Up</a></button>
<i class="fa-solid fa-circle-user" id="user-icon"></i>
</div>
<i class="fa-solid fa-bars" id="menu_icon"></i>
</nav>
</html>
// Dashboard.html
<!DOCTYPE html>
{% load static %}
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
48

<link href='https://unpkg.com/boxicons@2.0.9/css/boxicons.min.css' rel='stylesheet'>

<link rel="stylesheet" href="{% static 'css/dashbord.css' %}">
<title>{{user.email}}</title>
</head>
<body>
<section id="sidebar">
<a href="#" class="brand">
<span class="text" style="padding: 10%;">wellcome !

{{user.first_name}}</span>
</a>
<ul class="side-menu top">
<li class="active">
<a href="#">
<i class='bx bxs-dashboard' ></i>
<span class="text">Dashboard</span>
</a>
</li>
<li>
<a href="#">
<i class='bx bxs-shopping-bag-alt' ></i>
<span class="text">My Store</span>
</a>
</li>
<li>
<a href="#">
<i class='bx bxs-doughnut-chart' ></i>
<span class="text">Analytics</span>
</a>
</li>
<li>
<a href="#">
<i class='bx bxs-message-dots' ></i>
<span class="text">Message</span>
49
</a>
</li>
<li>
<a href="#">
<i class='bx bxs-group' ></i>
<span class="text">Team</span>
</a>
</li>
</ul>
<ul class="side-menu">
<li>
<a href="#">
<i class='bx bxs-cog' ></i>
<span class="text">Settings</span>
</a>
</li>
<li>
<a href="{% url 'userlogout' %}" class="logout">
<i class='bx bxs-log-out-circle' ></i>
<span class="text">Logout</span>
</a>
</li>
</ul>
<input type="checkbox" id="switch-mode" hidden>

<label for="switch-mode" class="switch-mode"></label>
<a href="#" class="notification">
<i class='bx bxs-bell' ></i>
<span class="num">8</span>
</a>
<a href="#" class="profile">
<img src="{% static 'image/people.png' %}">
</a>
</nav>
<main>
<div class="head-title">
50
<div class="left">
<h1>Dashboard</h1>
<ul class="breadcrumb">
<li>
<a href="#">Dashboard</a>
</li>
<li><i class='bx bx-chevron-right' ></i></li>
<li>
<a class="active" href="#">Home</a>
</li>
</ul>
</div>
<a href="#" class="btn-download">
<i class='bx bxs-cloud-download' ></i>
<span class="text">Download PDF</span>
</a>
</div>
<ul class="box-info">
<li>
<i class='bx bxs-calendar-check' ></i>
<span class="text">
<h3>1020</h3>
<p>New Order</p>
</span>
</li>
<li>
<i class='bx bxs-group' ></i>
<span class="text">
<h3>2834</h3>
<p>Visitors</p>
</span>
</li>
<li>
<i class='bx bxs-dollar-circle' ></i>
<span class="text">
51
<h3>$2543</h3>
<p>Total Sales</p>
</span>
</li>
</ul>
</body>
</html>
// Login.html
<!DOCTYPE html>
<html lang="en" style="scroll-behavior: smooth; height: 100%">
<head>
<link rel="stylesheet" href="/assets/css/location-register.css" />
<link
rel="stylesheet"
/>
<link
rel="stylesheet"
/>
</head>
<body>
<a href="/index.html" class="logo"
>Its<span class="red">My</span>Parking</a
>
<ul>
52
<li>
<div class="dropdown">
<button class="drop_btn">
Services
<i class="fa-solid fa-caret-down" style="color: #e1fffd"></i>
</button>
<div class="drop_point">
<a href="#"
><i
class="fa-solid fa-square-parking"
style="color: #e1fffd"
></i>
Find your parking</a
>
<a href="#"
><i class="fa-solid fa-house" style="color: #e1fffd"></i>
Register your free space</a
>
</div>
</div>
</li>
<li><a href="/contact.html" class="bottom_bar">Contacts</a></li>
</ul>
<p class="copyright">©2023 ItsMyParking | All rights Reserved.</p>

<p class="designer">Designed by:- <a href="#">ADTech</a></p>
</div>
</div>
</div>
</footer>
</div>
<script src="assets/js/script.js"></script>
<script src="/assets/js/swiper.js"></script>
53
<script
></script>
</body>
</html>
//Register.html
<!DOCTYPE html>
<html lang="en" style="scroll-behavior: smooth; height: 100%">
<head>
<link rel="stylesheet" href="/assets/css/location-register.css">
<link
rel="stylesheet"
/>
<link
rel="stylesheet"
/>
</head>
<body>
<a href="/index.html" class="logo"
>
<ul>
54
<div class="container-loc">
<div class="register-location">
<h1>Want to earn from your Free Space!</h1>
<button class="list-btn">List Your Parking Space</button></a>
</div>
<div class="register-location second-panel">
<div class="imgBox">
<img class="money" src="/assets/img/money.jpg" alt="">
<img class="car" src="/assets/img/homepage-header-image-2.e8b2a31.jpg" alt="">
<img class="house" src="/assets/img/house.jpg" alt="">
</div>
</div>
</div>
<div class="section-1">
<div class="how-it-works">
<h1><i class="fa-solid fa-hashtag"></i> How it works</h1>
<p>Steps to book your slot efficiently</p>
<div class="steps">
<div class="all-steps">
<div class="face face1">
<div class="content_how_it_works">
<h2>Step One</h2>
<a href="#">Read More</a>
</div>
</div>
<h2>01</h2>
</div>
</div>
<div class="all-steps">
<div class="content_how_it_works">
<h2>Step Two</h2>
<a href="#">Read More</a>
55
<h2>05</h2>
</div>
</div>
</div>
</div>
</div>
<footer>
<div class="footer">
<div class="row">
<div class="col">
<a href="/index.html" class="logo logo_footer"
>
<p>
Find the perfect parking solution for your needs and save time
and money. Join our network of parking providers today.
</p>
</div>
<div class="col">
<h3>Office</h3>
<p>itpl road</p>
<p>rampuri,muzaffarangar</p>
<p>Uttar pradesh , PIN 251001, India</p>
<p class="email-id">ItsMyParkingoutlook.com</p>
<h3>+91 - 8791409391</h3>
</div>
<div class="col">
<h3>Links</h3>
<ul class="link_footer">
<li><a href="#">Home</a></li>
<li><a href="#">Services</a></li>
<li><a href="#">About</a></li>
<li><a href="#">contact</a></li>
</ul>
</div>
<div class="col">
56
<h3>Search Parking In Your City</h3>
<form action="">
<div class="centered">
<div class="search">
<input
type="text"
name="search"
placeholder="Enter Your City Name... "
/>
<button>
<label for="search">search</label>
<i class="fa-solid fa-magnifying-glass search-icon"></i>
</button>
</div>
</div>
</form>
<p class="copyright">©2023 ItsMyParking | All rights Reserved.</p>
<p class="designer">Designed by:- <a href="#">ADTech</a></p>
</div>
</div>
</div>
</footer>
</div>
<script src="assets/js/script.js"></script>
<script
></script>
</body>
</html>
6.2 CSS FILE

@import "../css/style.css";
.section{
57
display: flex;
justify-content: center;
align-items: center;
text-align: center;
flex-direction: column;
color: #e1fffd;
}
.about-heading{
display: flex;
width: 100%;
background: url("../image/wave.png");
background-repeat: no-repeat;
background-size: cover;
/* background-position: center; */
background-position:top;
padding: 100px;
}
.about-heading h1{
margin-top: 100px;
font-size: 5em;
font-weight: 900;
word-spacing: 30px;
}
.register_btn{
display: none;
}
.section-contact {
position: relative;
width: 100%;
display: flex;
58
min-height: 90.8vh;
background: linear-gradient(
to right,
rgba(5, 28, 31, 0.6),
rgba(5, 28, 31, 0.8),
rgba(5, 29, 31, 1),
rgba(5, 28, 31, 1),
rgba(5, 28, 31, 0.8),
rgba(5, 28, 31, 0.6)
),
url("../image/img_car.jpg");
background-position: center;
}
.contact-container {
position: relative;
min-width: 1100px;
min-height: 550px;
display: flex;
z-index: 99;
}
.contact-container .contact-info h2 {
color: #e1fffd;
font-size: 24px;
font-weight: 500;
}
.contact-container .contact-info ul.info {

position: relative;
margin: 20px 0;
}
.contact-container .contact-info ul.info li {
position: relative;
list-style: none;
display: flex;
59
margin: 20px 0;
cursor: pointer;
align-items: flex-start;
}
.contact-container .contact-info ul.info li span:nth-child(1) {

width: 30px;
min-width: 30px;
}
.contact-container .contact-info ul.info li span:nth-child(1) img {

max-width: 100%;
filter: invert(1);
}
.contact-container .contact-info ul.info li span:nth-child(2) {

color: #e1fffd;
margin-left: 10px;
font-weight: 300;
}
.social_icon {
position: relative;
display: flex;
}
.social_icon li {
list-style: none;
}
.contact-container .contact-form .formBox {
position: relative;
display: flex;
justify-content: space-between;
flex-wrap: wrap;
padding-top: 30px;
}
60
.contact-container .contact-form .formBox .inputBox {
position: relative;
margin-bottom: 35px;
}
.contact-container .contact-form .formBox .inputBox.w50 {

width: 47%;
}
.contact-container .contact-form .formBox .inputBox.w100 {
width: 100%;
}
.contact-container .contact-form .formBox .inputBox input,

.contact-container .contact-form .formBox .inputBox textarea {
width: 100%;
resize: none;
padding: 5px 0;
font-size: 18px;
font-weight: 300;
color: #051d1f;
border: none;
outline: none;
border-bottom: 1px solid #051d1f;
}
.contact-container .contact-form .formBox .inputBox textarea {

height: 120px;
}
.contact-container .contact-form .formBox .inputBox span {

position: absolute;
left: 0;
padding: 5px 0;
pointer-events: none;
font-size: 18px;
61
font-weight: 300;
transition: 0.3s;
}
/* now make it responsive */
@media (max-width: 1200px) {
.contact-container {
width: 90%;
min-width: auto;
margin: 20px 0;
box-shadow: 0 20px 50px rgba(0, 0, 0, 0.3);
}
Register.css
@import "style.css";
.section-sign{
width: 100%;
height: 90.5vh;
display: flex;
background: linear-gradient(to right,rgba(5, 28, 31,1),rgba(5, 28, 31,0.9), rgba(5, 29,
31,0.4),rgba(5, 28, 31,0.4 ),rgba(5, 28, 31,0.9), rgba(5, 28, 31,1)), url("../image/img_car.jpg");
background-position: center;
color: #e1fffd;
}
.login-register{
font-size: .9em;
text-align: center;
font-weight: 500;
margin: 25px 0 10px;
}
.login-register p a{
62
color: #40f6ea;
text-decoration: none;
font-weight: 600;
}
.login-register p a:hover{
text-decoration: underline;
}
.login-register{
font-size: .9em;
text-align: center;
font-weight: 500;
margin: 25px 0 10px;
}
.login-register p a{
color: #40f6ea;
text-decoration: none;
font-weight: 600;
}
.login-register p a:hover{
text-decoration: underline;
}
6.3 JAVASCRIPT FILE

const allSideMenu = document.querySelectorAll('#sidebar .side-menu.top li a');
allSideMenu.forEach(item=> {
const li = item.parentElement;
item.addEventListener('click', function () {
allSideMenu.forEach(i=> {
i.parentElement.classList.remove('active');
})
li.classList.add('active');
63
})
});
// TOGGLE SIDEBAR
const menuBar = document.querySelector('#content nav .bx.bx-menu');
const sidebar = document.getElementById('sidebar');
menuBar.addEventListener('click', function () {
sidebar.classList.toggle('hide');
})
const searchButton = document.querySelector('#content nav form .form-input button');
const searchButtonIcon = document.querySelector('#content nav form .form-input button .bx');
const searchForm = document.querySelector('#content nav form');
if(window.innerWidth < 768) {
sidebar.classList.add('hide');
} else if(window.innerWidth > 576) {
searchButtonIcon.classList.replace('bx-x', 'bx-search');
searchForm.classList.remove('show');
}
window.addEventListener('resize', function () {
if(this.innerWidth > 576) {
searchButtonIcon.classList.replace('bx-x', 'bx-search');
searchForm.classList.remove('show');
}
})
const switchMode = document.getElementById('switch-mode');
switchMode.addEventListener('change', function () {
if(this.checked) {
document.body.classList.add('dark');
} else {
document.body.classList.remove('dark');
}
})
64
6.4 BACKEND FILE
from django.shortcuts import render , HttpResponse ,HttpResponseRedirect
from django.contrib.auth.models import User
from django.contrib.auth import login ,logout , authenticate
from .models import register_table
from django.contrib.auth.decorators import login_required
def indexpage(request):
return render(request ,'index.html')
def aboutpage(request):
return render(request,'about.html')
@login_required(login_url='login')
def locationregister(request):
return render(request,'location-register.html')
def contact(request):
return render(request,'contact.html')
def userlogin(request):
if request.method=='POST':
uname=request.POST['name']
pass1=request.POST['password']
user=authenticate(username=uname,password=pass1)
# return HttpResponse(user)
if user:
login(request,user)
if user.is_superuser:
return HttpResponseRedirect('/admin')
else:
return render(request,'location-register.html')
else:
return render(request,'login.html',{'status':'username or password is worng !!'})
65
return render(request,'login.html')
def register(request):
uname=request.POST['username']
email=request.POST['email']
pass1=request.POST['pass1']
pass2=request.POST['pass2']
checkbox = request.POST.get('checkbox1', False) == 'on'
usr =User.objects.create_user(uname,email,pass1)
usr.first_name=uname
usr.save()
reg=register_table(user=usr , pass2=pass2)
reg.save()
return render(request,'register.html',{'status':"{}, your account created successfully!!
".format(uname)})
return render(request,'register.html')
def register_space(request):
context = {}
check = register_table.objects.filter(user id=request.user.id)
if len(check)>0:
data = register_table.objects.get(user id=request.user.id)
context["data"]=data
state=request.POST['state']
city=request.POST['city']
line1=request.POST['line1']
line2=request.POST['line2']
data.state = state
data.city = city
data. address_line = line1
data.save()
66
return render(request,'location-form.html')
def find(request):
return render(request,'find.html')
def dashbord(request):
context = {}
if len(check)>0:
return render(request,'dashbord.html')
@login_required()
def userlogout(request):
logout(request)
return HttpResponseRedirect('/')
def edit_profile(request):
context = {}
if len(check)>0:
if request.method=="POST":
fn = request.POST["fname"]
ln = request.POST["lname"]
em = request.POST["email"]
con = request.POST["contact"]
age = request.POST["age"]
ct = request.POST["city"]
gen = request.POST["gender"]
loc_lon=request.POST["longitude"]
loc_lat=request.POST["latitude"]
st=request.POST["state"]
67
add=request.POST["address"]
avl_slt=request.POST["slote"]
usr = User.objects.get(id=request.user.id)
usr.first_name = fn
usr.last_name = ln
usr.email = em
usr.save()
data.contact_number = con
data.age = age
data.city = ct
data.gender = gen
data.location_latitude=loc_lat
data.location_longitude=loc_lon
data.state=st
data.address_line=add
data.available_slote=avl_slt
if "image" in request.FILES:
img = request.FILES["image"]
data.profile_pic = img
data.save()
context["status"] = "Changes Saved Successfully"

return render(request,"edit_profile.html",context)
def locationform(request):
return render(request,'location-form.html')
68
CHAPTER 7
TESTING
69
The testing phase plays a crucial role in the development and deployment of this parking
management systems. This literature review aims to provide a comprehensive examination of
the testing phase in parking management systems. It explores various aspects of testing,
including testing objectives, methodologies, challenges, and best practices. By understanding
the testing phase's significance and implementing effective testing strategies, developers and
stakeholders can ensure the successful implementation and operation of parking this system.
Software testing is the process of evaluating and verifying that a software product or
application does what it is supposed to do. The benefits of testing include preventing bugs,
reducing development costs and improving performance.
7.1 UNIT TESTING

Unit testing is a software development process in which the smallest testable parts of an
application, called units, are individually and independently scrutinized for proper operation.
This testing methodology is done during the development process by the software developers
and sometimes QA staff. In computer programming, unit testing is a software testing method
by which individual units of source code, sets of one or more computer program modules
together with associated control data, usage procedures, and operating procedures, are tested to
determine whether they are fit for use. Intuitively, one can view a unit as the smallest testable
part of an application. In procedural programming, a unit could be an entire module, but it is
more commonly an individual function or procedure. In object-oriented programming, a unit is
often an entire interface, such as a class, but could be an individual method. Unit tests are short
code fragments created by programmers or occasionally by white box testers during the
development process. It forms the basis for component testing. Ideally, each test case is
independent from the others. Substitutes such as method stubs, mock objects, fakes, and test
harnesses can be used to assist testing a module in isolation. Unit tests are typically written and
run by software developers to ensure that code meets its design and behaves as intended.
7.1.1 BENEFITS
The goal of unit testing is to isolate each part of the program and show that the individual parts
70
are correct. A unit test provides a strict, written contract that the piece of code must satisfy. As
a result, it affords several benefits.
 Find problems early: Unit testing finds problems early in the development cycle. In test-
driven development (TDD), which is frequently used in both extreme programming and
scrum, unit tests are created before the code itself is written. When the tests pass, that code
is considered complete. The same unit tests are run against that function frequently as the
larger code base is developed either as the code is changed or via an automated process
with the build. If the unit tests fail, it is considered to be a bug either in the changed code or
26 the tests themselves. The unit tests then allow the location of the fault or failure to be
easily traced. Since the unit tests alert the development team of the problem before handing
the code off to testers or clients, it is still early in the development process.
 Facilitates Change: Unit testing allows the programmer to refactor code or upgrade system
libraries at a later date, and make sure the module still works correctly (e.g., in regression
testing). The procedure is to write test cases for all functions and methods so that whenever
a change causes a fault, it can be quickly identified. Unit tests detect changes which may
break a design contract.
 Simplifies Integration: Unit testing may reduce uncertainty in the units themselves and
can be used in a bottom-up testing style approach. By testing the parts of a program first
and then testing the sum of its parts, integration testing becomes much easier.
 Documentation: Unit testing provides a sort of living documentation of the system.

Developers looking to learn what functionality is provided by a unit, and how to use it, can
look at the unit tests to gain a basic understanding of the unit's interface (API). Unit test
cases embody characteristics that are critical to the success of the unit. These characteristics
can indicate appropriate/inappropriate use of a unit as well as negative behaviors that are to
be trapped by the unit.
7.2 INTEGRATION TESTING

Integration testing (sometimes called integration and testing, abbreviated I&T) is the phase in
software testing in which individual software modules are combined and tested as a group. It
71
occurs after unit testing and before validation testing. Integration testing takes as its input
modules that have been unit tested, groups them in larger aggregates, applies tests defined in an
integration test plan to those aggregates, and delivers as its output the integrated system ready
for system testing.
7.2.1.1 BIG BANG APPROACH
In the big-bang approach, most of the developed modules are coupled together to form a
complete software system or major part of the system and then used for integration testing. This
method is very effective for saving time in the integration testing process. However, if the test
cases and their results are not recorded properly, the entire integration process will be more
complicated and may prevent the testing team from achieving the goal of integration testing. A
type of big-bang integration testing is called "usage model testing" which can be used in both
software and hardware integration testing. The basis behind this type of integration testing is to
run user-like workloads in integrated user-like environments. In doing the testing in this
manner, the environment is proofed, while the individual components are proofed indirectly
through their use. Usage Model testing takes an optimistic approach to testing, because it
expects to have few problems with the individual components. The strategy relies heavily on
the component developers to do the isolated unit testing for their product. The goal of the
strategy is to avoid redoing the testing done by the developers, and instead flesh-out problems
caused by the interaction of the components in the environment.
7.2.1.2 TOP-DOWN AND BOTTOM-UP APPROACH
Testing is an approach to integrated testing where the lowest level components are tested first,
then used to facilitate the testing of higher-level components. The process is repeated until the
component at the top of the hierarchy is tested. All the bottom or low-level 28 modules,
procedures or functions are integrated and then tested. After the integration testing of lower-
level integrated modules, the next level of modules will be formed and can be used for
integration testing. This approach is helpful only when all or most of the modules of the same
development level are ready. This method also helps to determine the levels of software
72
developed and makes it easier to report testing progress in the form of a percentage. Topdown
testing is an approach to integrated testing where the top integrated modules are tested and the
branch of the module is tested step by step until the end of the related module. Sandwich testing
is an approach to combine top-down testing with bottom-up testing.
7.3 SOFTWARE VERIFICATION AND VALIDATION

In software project management, software testing, and software engineering, verification and
validation (V&V) is the process of checking that a software system meets specifications and
requirements so that it fulfills its intended purpose. It may also be referred to as software
quality control. It is normally the responsibility of software testers as part of the software
development lifecycle. In simple terms, software verification is: "Assuming we should build X,
does our software achieve its goals without any bugs or gaps?" On the other hand, software
validation is: "Was X what we should have built? Does X meet the high-level requirements?"
In software project management, software testing, and software engineering, verification and
validation (V&V) is the process of checking that a software system meets specifications and
that it fulfils its intended purpose. It may also be referred to as software quality control. It is
normally the responsibility of software testers as part of the software development lifecycle.
Validation checks that the product design satisfies or fits the intended use (highlevel checking),
i.e., the software meets the user requirements. This is done through dynamic testing and other
forms of review. Verification and validation are not the same thing, although they are often
confused. Boehm succinctly expressed the difference between
 Validation: Are we building the right product?
 Verification: Are we building the product, right?
According to the Capability Maturity Model (CMMI-SW v1.1) Software Verification: The
process of evaluating software to determine whether the products of a given development phase
satisfy the conditions imposed at the start of that phase.
Software Validation: The process of evaluating software during or at the end of the
development process to determine whether it satisfies specified requirements. In other words,
software verification is ensuring that the product has been built according to the requirements
73
and design specifications, while software validation ensures that the product meets the user's
needs, and that the specifications were correct in the first place. Software verification ensures
that "you built it right". Software validation ensures that "you built the right thing". Software
validation confirms that the product, as provided, will fulfil its intended use. From Testing
Perspective.
• Fault – wrong or missing function in the code.
• Failure – the manifestation of a fault during execution.
• Malfunction – according to its specification the system does not meet its specified
functionality. Both verification and validation are related to the concepts of quality and of
software quality assurance. By themselves, verification and validation do not guarantee
software quality; planning, traceability, configuration management and other aspects of
software engineering are required. Within the modelling and simulation (M&S) community, the
definitions of verification, validation and accreditation are similar. M&S Verification is the
process of determining that a computer model, simulation, or federation of models and
simulations implementations and their associated data accurately represent the developer's
conceptual description and specifications.
• M&S Validation – This is the process of determining the degree to which a model,
simulation, or federation of models and simulations, and their associated data are accurate
representations of the real world from the perspective of the intended use(s).
7.4 BLACK-BOX TESTING

Black-box testing is a method of software testing that examines the functionality of an
application without peering into its internal structures or workings. This method of test can be
applied virtually to every level of software testing: unit, integration, system and acceptance. It
typically comprises most if not all higher-level testing, but can also dominate unit testing as
well. 7.4.1 Test Procedures
Specific knowledge of the application's code/internal structure and programming

knowledge in general is not required. The tester is aware of what the software is supposed to do
but is not aware of how it does it. For instance, the tester is aware that a particular input returns
74
a certain, invariable output but is not aware of how the software produces the output in the first
place.
7.5 WHITE-BOX TESTING

White-box testing (also known as clear box testing, glass box testing, transparent box testing,
and structural testing) is a method of testing software that tests internal structures or workings
of an application, as opposed to its functionality (i.e., black-box testing). In whitebox testing an
internal perspective of the system, as well as programming skills, are used to design test cases.
The tester chooses inputs to exercise paths through the code and determine the appropriate
outputs. This is analogous to testing nodes in a circuit, e.g., in-circuit testing (ICT). White-box
testing can be applied at the unit, integration and system levels of the software testing 31
process. Although traditional testers tended to think of white-box testing as being done at the
unit level, it is used for integration and system testing more frequently today. It can test paths
within a unit, paths between units during integration, and between subsystems during a system–
level test. Though this method of test design can uncover many errors or problems, it has the
potential to miss unimplemented parts of the specification or missing requirements.
7.5.1 LEVELS
The levels in white box testing includes the following:
 Unit Testing: White-box testing is done during unit testing to ensure that the code is
working as intended, before any integration happens with previously tested code. Whitebox
testing during unit testing catches any defects early on and aids in any defects that happen
later on after the code is integrated with the rest of the application and therefore prevents
any type of errors later on.
 Integration Testing: White-box testing at this level are written to test the interactions of
each interface with each other. The Unit level testing made sure that each code was tested
and working accordingly in an isolated environment and integration examines the
correctness of the behaviour in an open environment through the use of white-box testing
for any interactions of interfaces that are known to the programmer.
75
 Regression Testing: White-box testing during regression testing is the use of recycled
white-box test cases at the unit and integration testing levels.
7.6 SYSTEM TESTING

System testing of software or hardware is testing conducted on a complete, integrated system to
evaluate the system's compliance with its specified requirements. System testing falls within
the scope of black-box testing, and as such, should require no knowledge of the inner design of
the code or logic. As a rule, system testing takes, as its input, all of the "integrated" software
components that have passed integration testing and also the software system itself integrated
with any applicable hardware system(s). The purpose of integration testing is to detect any
inconsistencies between the software units that are integrated together (called assemblages) or
between any of the assemblages and the hardware. System testing is a more limited type of
testing; it seeks to detect defects both within the "inter-assemblages" and also within the system
as a whole. System testing is performed on the entire system in the context of a Functional
Requirement Specification(s) (FRS) and/or a System Requirement Specification (SRS). System
testing tests not only the design, but also the behaviour and even the believed expectations of
the customer. It is also intended to test up to and beyond the bounds defined in the
software/hardware requirements specification(s).
76
CHAPTER 8
IMPLEMENTATIONS
AND RESULTS
77
This chapter includes the description and implementation results of the project. Here it has
included all the screenshots from this project. The upcoming sections will go over them one by
one and explain them briefly.
8.1 HOMEPAGE
Figure 8.1 Homepage viewed by all users (Admin and User)
In figure 8.1, it has homepage that can also be called as the landing page of our website where
the user will first land into. In this page it has the standard option for the users. As the user can
have two operations to log into our website. Firstly if they want to book a parking slot, they
will click on the “Get Parking Slot” button. If the user wants to register their space as a parking
slot the can click on the “Register Your Parking Space” button. For both the actions the user
will be taken to the relevant pages. We have also provided the “Home”, ”About”, “Services”,
and “Contact Us” buttons to make it convenient for the user to access our web application.
78
8.2 REGISTRATION PAGE
Figure 8.2: Registration Page

Figure 8.2 shows the interface of the registration page where the user will fill all the
necessary details. These details will be then saved into the database in order to remember
the user. At the time of registration, the username and password as set as the primary key
for the user to login.
8.3 LOGIN PAGE
Figure 8.3 Login Page
79
Figure 8.3 shows the Login Page interface through which the user will login into their account
using the email id and password. The email and password filled by the user are matched in the
database and if matched successfully the user is granted the permission to enter their account.
8.4 PAYMENT GATEWAY INTERFACE
Figure 8.4: Payment Gateway Interface

Figure 8.4 displays the Razorpay Payment Gateway Interface where the user will be directed
after completing the whole process of booking. The user can pay using any method like UPI,
net banking, and even from debit or credit card. This page was made through the website of
Razorpay through which an access was later gain to make this payment gateway interface.
80
8.5 LOGIN PAGE FOR ADMIN
Figure 8.5: Login page for admin
Figure 8.5 shows the login page for the admin. At first the admin is needed to create an
account to grant them permission to access the backend. Their admin_name and
password are would be used for login. The Admin would be controlling the database and
backend using Django as it provides a built-in page for the admin’s login and accessing details.
Django provides this utility with some basic tools so that the developers doesn’t need to work
separately on it. Django also has a database attached with it. Through this administration page
of Django we can do our testing quite easily. Django also provides us the independence to use
any other database with it. We just need to configure it.
81
8.6 SPACE REGISTER HOMEPAGE
Figure 8.6 Space Register HomePage

This is the homepage for registering the parking space by the user. It includes details about the
steps through which user can apply to register their parking space. The user needs to hover on
the steps and then each step would provide an explanation about how to proceed.
82
8.7 SPACE REGISTRATION FORM
Figure 8.7 Space Registration Form

This is the main page for registering the parking space by the user. Here the user needs to fill some
basic details which are mostly based on address and some details regarding the space. After user
fills this detail form and submits it, within 7 working days one of our executives can visit the area,
confirm the details and approve it.
8.8 CONTACT US INTERFACE
Figure 9.8: Contact Us Interface
83
In figure 9.8 we have displayed the contact us section which would be helpful in taking any
feedback and suggestions from the users and providing better services to them and it would
also help us in deciding some critical choices in the upcoming future regarding this website.
8.9 ABOUT US PAGE
Figure 8.9: About Us Section
Figure 8.9 shows us the “About Us” section where we have provided a little description about
us and about this project. Here we have also discussed about the
features of this project and have also appreciated our users. We have also shared if a user has
any complaints or suggestion they can feel free to drop it to us using the Contact Us page.
84
CHAPTER 9
CONCLUSION
AND FUTURE
WORKS
85
9.1 CONCLUSION
”ItsMyParking” has been a comprehensive endeavor aimed at addressing the challenges
and inefficiencies associated with parking in urban areas. Throughout the project, various
aspects have been considered, including user convenience, efficient space utilization, and
the utilization of emerging technologies.
The implementation of user-configurable parking systems has shown promising results

in improving the overall parking experience. By allowing users to set their own parking
slots, these systems have significantly reduced the time-consuming and frustrating search
for available spaces. This enhanced user convenience has resulted in higher user satisfaction
and reduced parking-related stress.
Efficient space utilization has been a key focus of the project. Through real-time data
collection and analysis, the parking management system has provided valuable insights into
parking patterns and usage. This information has been leveraged to optimize parking
resources, reduce idle time, and maximize the utilization of available spaces. The system's
data-driven approach has contributed to improved parking management and has the
potential to further alleviate parking congestion in urban areas.
The project has not been without its challenges and limitations. Addressing concerns
related to system abuse and misuse has required careful planning, robust security measures,
and effective system maintenance. Technical limitations, such as connectivity issues and
compatibility problems with existing infrastructure, have also needed to be overcome.
However, through diligent efforts, these challenges have been addressed, and valuable
lessons have been learned for future implementations.
Case studies and implementation examples have highlighted the feasibility and positive
outcomes of user-configurable parking systems. Successful implementations in smart cities
like Barcelona, San Francisco, and Singapore have demonstrated the significant impact of
these systems on parking management, traffic congestion reduction, and enhanced user
experiences. The integration of user feedback and continuous improvements in system
usability have been instrumental in achieving these positive outcomes.
In conclusion, the parking management system project has showcased the potential of
user-configurable parking systems in revolutionizing the parking experience. By prioritizing
user convenience, optimizing space utilization, and addressing challenges through effective
testing and implementation strategies, the project has laid the foundation for efficient and
86
user-centric parking management systems. Future research and development in this field
should focus on refining implementation processes, evaluating system performance, and
exploring the integration of emerging technologies to further enhance the effectiveness and
impact of parking management systems.
9.2 VARIOUS PROJECT CONSTRAINT AND LIMITATION

The various project constraints and limitations of parking management system allowing
users to register their parking slot:
9.2.1 TECHNICAL LIMITATIONS
The technical limitations of this project are the following:
 Existing Infrastructure: The parking management system may face constraints in

integrating with the existing infrastructure, such as parking meters, payment systems, or
access control mechanisms. Compatibility issues and technical dependencies may
require additional efforts and modifications to ensure seamless integration.
 Connectivity: Reliable and stable connectivity is crucial for the system to function
effectively. However, limitations in network coverage or connectivity in certain areas
may impact the system's availability and real-time updates.
 Hardware and Sensor Limitations: The availability and deployment of smart parking
sensors or devices may pose limitations, especially in retrofitting existing parking
spaces. The cost, maintenance, and scalability of sensor deployment could impact the
system's coverage and accuracy.
9.2.2 USER ADOPTION AND BEHAVIOR
The various observed user adoption and behavior includes the following:
 User Engagement: Encouraging users to actively register their parking slots and adopt
the system can be a challenge. Convincing users to change their existing parking habits
and rely on the new system may require effective marketing strategies and user
education initiatives.
87
 User Compliance: There may be instances where users register parking slots but fail to
adhere to their reservation or misuse the system, leading to inefficient use of parking
resources. Ensuring user compliance and addressing misuse requires clear policies,
enforcement measures, and user accountability mechanisms.
9.2.3 PRIVACY AND SECURITY CONCERNS
The privacy and security concerns related to this project are:
 Data Privacy: Collecting and storing user data, including personal information,
location data, and payment details, raises privacy concerns. Ensuring compliance with
data protection regulations and implementing robust security measures to protect user
information is essential.
 Cybersecurity: The parking management system, being connected to the internet and
potentially integrated with other systems, may be vulnerable to cyber threats, including
data breaches, unauthorized access, or system manipulation. Implementing stringent
security protocols, encryption mechanisms, and regular security audits are crucial to
mitigate these risks.
9.2.4 SCALABILITY AND SYSTEM PERFORMANCE
The various points to improve scalability and system performance includes the following:
 Handling High User Demand: The system's performance and responsiveness under
high user demand, particularly during peak hours or events, may pose challenges.
Ensuring scalability, load balancing, and effective resource management are critical to
maintaining system performance during peak periods.
 Real-Time Updates: Providing accurate and real-time updates regarding parking

availability, slot reservations, and cancellations is vital for user satisfaction. The system
must be capable of handling and updating data in real-time to avoid discrepancies or
confusion among users.
9.2.5 FINANCIAL CONSTRAINTS
The financial constraints related to this project are the following:
88
 Budgetary Limitations: The availability of financial resources for the project may
impose constraints on the system's development, deployment, and maintenance.
Prioritizing features and functionalities within the given budget may be necessary,
potentially impacting the scope and timeline of the project.
 Cost Implications for Users: Introducing a user-configurable parking system may

involve additional costs for users, such as registration fees, reservation charges, or
transaction fees. Balancing the cost implications with user benefits and ensuring
affordability for all user segments can be challenging.
It is important to consider and address these constraints and limitations during the
planning, design, and implementation phases of the parking management system project. By
anticipating and mitigating these challenges, stakeholders can develop a more robust and
successful system that caters to user needs while overcoming technical, behavioral, privacy,
scalability, and financial obstacles.
9.3 VARIOUS FUTURE WORKS

The various future works for parking management system allowing users to register their
parking slot are the following:
 Integration Of Emerging Technologies: Explore the integration of emerging

technologies such as artificial intelligence (AI), machine learning, and computer vision
to enhance the accuracy and efficiency of parking management systems. AI algorithms
can analyze real-time data to predict parking availability, optimize parking resource
allocation, and provide personalized parking recommendations to users.
 Improved User Experience: Focus on enhancing the user experience by

implementing features like user feedback mechanisms, seamless payment integration,
and user-friendly mobile applications. Incorporate user suggestions and preferences to
tailor the system to their needs, ensuring a smooth and convenient parking experience.
 Advanced Reservation System: Develop an advanced reservation system that

allows users to reserve parking slots well in advance. Implement features such as
flexible reservation timings, cancellation options, and reminder notifications to improve
user convenience and reduce instances of no-shows or unused reservations.
 Smart Parking Guidance: Utilize real-time data and IoT technologies to provide smart
89
parking guidance to users. Implement dynamic signage and mobile applications that
guide users to available parking spaces in real-time, reducing the time spent searching
for a parking spot and optimizing traffic flow within parking facilities.
 Sustainable Parking Solutions: Integrate sustainability initiatives within parking

management systems. Incorporate features such as electric vehicle (EV) charging station
availability and incentives for using eco-friendly vehicles. Implement smart pricing
strategies to encourage carpooling and incentivize users to choose alternative
transportation methods.
 Collaborative Parking Networks: Foster collaborations between parking management

systems and other stakeholders, including local businesses, municipalities, and
transportation authorities. Implement a unified parking network that enables seamless
parking access and information sharing across different parking facilities, improving
overall efficiency and convenience for users.
 Data-Driven Decision Making: Leverage the wealth of data collected through parking
management systems to gain valuable insights. Utilize data analytics and predictive
modeling to optimize parking resource allocation, predict parking demand, and plan
future infrastructure development.
 Expansion to Smart Cities: Extend the implementation of user-configurable parking

systems to a larger scale, integrating them into smart city initiatives. Collaborate with
urban planners, transportation departments, and technology providers to create a
comprehensive parking ecosystem that aligns with the broader vision of a smart and
sustainable city.
 Continuous Monitoring and Maintenance: Implement a robust monitoring and

maintenance system to ensure the parking management system operates smoothly over
time. Regularly update software components, perform system checks, and address any
technical issues or security vulnerabilities that may arise.
 User Education and Awareness: Conduct awareness campaigns and user education
programs to familiarize the public with the benefits and functionality of the parking
management system. Increase user adoption and compliance by highlighting the
advantages of using the system and addressing any concerns or misconceptions.
By pursuing these future works, the parking management system can continue to
90
evolve and adapt to changing user needs and technological advancements. This will result
in more efficient parking operations, enhanced user experiences, and improved urban
mobility overall.
9.4 SUMMARY
The implementation of a parking management system that allows users to register their
parking slots has shown significant potential in improving the parking experience and
addressing urban parking challenges. This summary highlights the key areas of focus for
future development and improvement.
Firstly, integrating emerging technologies such as AI, machine learning, and computer
vision can enhance the accuracy and efficiency of parking management systems. By
analyzing real-time data and predicting parking availability, these technologies can optimize
resource allocation and provide personalized recommendations to users.
Improving the user experience is a crucial aspect of future work. Incorporating user
feedback mechanisms, seamless payment integration, and user-friendly mobile applications
can enhance convenience and satisfaction. Additionally, an advanced reservation system
with flexible options and reminder notifications can further streamline the user experience.
Smart parking guidance, enabled by real-time data and IoT technologies, can direct
users to available parking spaces and optimize traffic flow. Sustainability initiatives, such as
EV charging station availability and incentives for eco-friendly vehicles, should also be
integrated into parking management systems.
Collaborations with local businesses, municipalities, and transportation authorities can

create a unified parking network, improving overall efficiency and convenience for users.
Data-driven decision making, enabled by data analytics and predictive modeling, can
optimize parking resource allocation and inform future infrastructure development.
Expanding the implementation of user-configurable parking systems to smart cities

aligns with broader urban planning initiatives. Continuous monitoring and maintenance,
along with user education programs, are vital for the long-term success of the system.
In conclusion, future work for parking management systems focuses on integrating

emerging technologies, improving the user experience, implementing smart parking
guidance, incorporating sustainability initiatives, fostering collaborations, utilizing data-
91
driven decision making, expanding to smart cities, ensuring system maintenance, and
conducting user education programs. By pursuing these areas of development, parking
management systems can continue to evolve and provide efficient and user-centric solutions
for urban parking challenge.
92
REFERENCES AND
BIBLIOGRAPHY
93
REFERENCES
[1] https://www.quora.com/What-is-a-parking-management-system
[2] https://www.youtube.com/watch?v=WNwm9j9Cb7M
[3] https://www.geeksforgeeks.org/design-parking-lot-using-object-oriented-principles/
[4] https://www.wohrparking.in/stack-car-parking-system-india-parklift-413.html
[5] https://www.w3schools.com/js/
[6] www.udemy.com – The Complete Web Development bootcamp 2022 by “Angela Yu”
[7] www.udemy.com – Build Ecommerce website [JavaScript, Node & MongoDB].
[8] https://www.freecodecamp.org/news/parking-lot-challenge-solved-in-javascript/
[9] https://www.mongodb.com/docs/
[10] https://www.tutorialspoint.com/mongodb/index.htm
[11] https://developer.mozilla.org/en-US/docs/Learn/Server-side/ExpressNodejs/Introduction/
[12] https://www.npmjs.com/package/express
[13] https://devdocs.io/express/
[14] https://reactjs.org/docs/faq-ajax.html
[15] https://rapidapi.com/blog/how-to-use-an-api-with-react/
[16] https://www.geeksforgeeks.org/how-to-fetch-data-from-an-api-in-reactjs/
[17] https://wayleadr.com/blog/parking-management-system/
[18] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference
[19] https://developer.mozilla.org/en-US/docs/Web/API
[20] https://getbootstrap.com/docs/5.1/getting-started/introduction/
[21] https://expressjs.com/en/4x/api.html
[22] https://docs.npmjs.com
94

ffffproject_removed_merged (1)_pagenumber (1)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ffffproject_removed_merged (1)_pagenumber (1)

Uploaded by

Copyright:

Available Formats

IT’S MY PARKING

The Research work embodied in this project entitled

Date: 10/05/2024 Sushant Mishra

This is to certify that the project report entitled

Dr. Tarun Vashishth

Dr. Suraj Malik Mrs. Rachna Chaudhary

Date: 10/05/2024 Sushant Mishra

1.1 Project Background....................................................................................... 13

1.2 Problem Statement ........................................................................................ 14

1.3 Objectives ..................................................................................................... 14

1.5 Project Planning ............................................................................................ 15

1.6 Expected Result ............................................................................................ 16

1.7 Motivation Of Work...................................................................................... 16

CHAPTER 2: LITERATURE REVIEW............................................................................. 18

2.1 Parking System Technologies........................................................................ 19

2.2 User Experience And Convenience ............................................................... 19

2.3 Efficient Space Utilization ............................................................................ 19

2.4 Challenges And Limitations ................................................................... 19 - 20

2.5 Case Studies And Implementation Example .................................................. 20

3.1 Proposed System.......................................................................................... 22

3.2.1 Registration Module ................................................................................ 24

3.2.2 Space Searching Module......................................................................... 24

3.2.3 Booking Module .................................................................................... 25

3.2.4 Payment Module.................................................................................... 25

3.2.5 Query Module ........................................................................................ 25

3.2.7 About Us Module ................................................................................... 25

3.2.8 Rating Module ........................................................................................ 26

3.3 Requirements Analysis................................................................................. 26

3.3.1 Hardware Requirements.......................................................................... 26

3.3.2 Software Requirements ........................................................................... 26

3.3.2.1 Technologies And Editors Used In This Project ............................... 27

CHAPTER 4 DESIGN AND PLANNING ........................................................................ 28

4.1 Software Development Life Cycle Model..................................................... 29

4.1.1 Waterfall Model ..................................................................................... 29

4.2 Use Case Diagram ................................................................................. 32 - 33

4.3 Entity Relationship Diagram ........................................................................ 33

4.3.1 Entities .................................................................................................... 33

4.3.2 Relationships ........................................................................................... 34

4.4 DFD ............................................................................................................ 36

4.4.1 Zero-Level DFD ...................................................................................... 36

4.4.2.1 Main Entities And Output Of First Level DFD ....................................... 38

4.4.3.1 Low Level Functionalities Of Online Car Parking System ............... 39

4.4 Flow Chart ............................................................................................. 40 - 41

CHAPTER 5 SURVEY OF TECHNOLOGIES ................................................................. 42

5.1 Html ............................................................................................................ 43

5.2 Cascading Style Sheet .................................................................................. 43

5.4 Rest Api....................................................................................................... 43

5.5 Django ......................................................................................................... 44

CHAPTER 6 CODING ..................................................................................................... 45

6.1 Html file ................................................................................................ 46 - 57

6.2 Css file ................................................................................................... 57 - 63

6.3 JavaScript file ........................................................................................ 63 - 64

6.4 Backend File .......................................................................................... 65 - 68

CHAPTER 7 TESTING .....................................................................................................69

7.1 Unit Testing ................................................................................................. 70

7.1.1 Benefits ............................................................................................. 70 - 71

7.2 Integration Testing ................................................................................. 71 - 72

7.2.1.1 Big Bang Approach .......................................................................... 72

7.2.1.2 Top-Down And Bottom-Up Approach........................................ 72 - 73

7.3 Software Verification And Validation .................................................... 73 - 74

7.4 Black-Box Testing ....................................................................................... 74

7.5.1 Levels .................................................................................................... 75

CHAPTER 8 IMPLEMENTATIONS AND RESULTS ..................................................... 77

8.2 Registration Page ......................................................................................... 79