GREEN UNIVERSITY OF BANGLADESH

Garage Tracking And Parking Application

Submitted by
Md.Touhidul Islam
191002314
Mufizul Islam
191002086
Md. Habibur Rahman
182002117

A project submitted to the Department of Computer Science and Engineering

in partial fulfillment of the requirements for the degree of
B.Sc. in Computer Science

Supervised by
Dr.Md.Mostafijur Rahman
Associate Professor
Department of Computer Science And Engineering

Department of Computer Science And Engineering

Green University of Bangladesh
220/D Begum Rokeya Sarani, Dhaka-1207
March,2023
Declaration
We hereby declare that this project is based on the results found by ourselves.
Materials of work found by other researchers are mentioned by reference. This
project, neither in whole nor in part, has been previously submitted for any degree.
In conclusion, I declare that this project report is an authentic representation of
my work, and I am solely responsible for the content and findings presented in this
report.

Student’s Full Name & Signature:

Md. Touhidul Islam Mufizul Islam

191002314 191002086

Md. Habibur Rahman

182002117

i
Approval
The project titled “Garage Tracking And Parking Application”

submitted by
1. Md. Touhidul Islam (191002314)
2. Mufizul Islam (191002086)
3. Md. Habibur Rahman (182002117)
Of Fall, 2022 has been accepted as satisfactory in partial fulfillment of the require-
ment for the degree of B.Sc. in Computer Science on March 23, 2023.

Approval Committee:

Supervisor:
(Member)

DR. MD. MOSTAFIJUR RAHMAN

Associate Professor
Department of CSE
Green University

Program Coordinator:
(Member)

MR. MD. JAHIDUL ISLAM

Assistant Professor
Department of CSE
Green University

Head of Department:
(Chair)

PROF. DR. MD. SAIFUL AZAD

Chairman and Professor
Department of CSE
Green University

ii
Certificate
This project titled ”GARAGE TRACKING AND PARKING APPLICATION” has
been prepared and submitted by Md. TOUHIDUL ISLAM, MUFIZUL ISLAM
and Md.Habibur Rahman to the department of Computer Science and Engineering,
Green University of Bangladesh, has been accepted as satisfactory for the partial
fulfillment of the requirement for the degree of Bachelor of Science in Computer
Science and Engineering approved as its style and contents. The presentation has
been held on 18 Mar 2023.

Examining Committee:

MR. MD. JAHIDUL ISLAM Mr. Md. ATIK AHAMED

Assistant Professor Lecturer

MR. TANOY DEBNATH Ms. SOBHANA JAHAN

Lecturer Lecturer

iii
ABSTRACT
This project report presents the development of a garage tracking and parking ap-
plication. The application aims to provide a streamlined, efficient, and user-friendly
solution for garage owners and drivers to manage parking operations. The applica-

tion features several modules, including a parking management module, a vehicle

tracking module, a payment processing module, and a reporting module. The park-
ing management module allows garage owners to manage parking spaces, monitor
availability, and assign parking spots to vehicles. The vehicle tracking module en-
ables drivers to find available parking spots, track their vehicle location, and receive
real-time notifications. The payment processing module allows drivers to pay for
parking using various payment methods, and the reporting module generates cus-
tomized reports for garage owners to analyze parking trends and optimize parking
operations. We used the Dart language to develop this system Flutter platform

for building mobile apps it. We also used the Firebase Database for the backend
and the Firebase Realtime Database for data store. We also use Google Maps API
to display the place location. Users need to install this Android application and
register here. Once the registration is complete, users will be able to use all of the
services in our system.

iv
Acknowledgement
First and foremost, we express our heartfelt gratitude to Almighty Allah for his won-
derful blessings, which have makes us to successfully finish the final year project.
We are really grateful and express our gratitude to DR. Md. Mostafijur Rahman
Associate Professor, Department of CSE, Green University of Bangladesh, Dhaka.
Our supervisor has thor- ough understanding and a deep interest in the subject
of project management, which he had use to complete this project successfully.
His never-ending patience, intellectual direction, constant encouragement, constant
and energetic supervision, criticism, good suggestions, and reading many drafts
and editing them at every level allowed this project to be successfully completed.
Also gratitude to the other faculty members and staff of the Green University of
Bangladesh’s CSE department. We would like to express our gratitude to all of our
Green University of Bangladesh classmates who participated in this discussion as
part of their academic work. Finally, we must acknowledge with due respect the
constant support and Blessings of our parents.

v
Table of Contents

Declaration i

Approval ii

Certificate iii

Abstract iv

Acknowledgment v

Table of Contents vi

List of Figures viii

List of Tables 1

1 Introduction 2
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.1 Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1.2 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1.3 Project Questions . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1.4 Contributions of project . . . . . . . . . . . . . . . . . . . . . 5
1.1.5 Project Outline . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 Literature Review 7
2.1 Problem Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1.1 Related Works . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1.2 Limitations of the Existing Projects . . . . . . . . . . . . . . . 9
2.1.3 Proposed Solutions . . . . . . . . . . . . . . . . . . . . . . . . 10
2.1.4 Compression with Existing And Proposed System . . . . . . . 11
2.1.5 Review Compression . . . . . . . . . . . . . . . . . . . . . . . 11
2.1.6 Mobile Application Review . . . . . . . . . . . . . . . . . . . . 12
2.1.7 A Review of XML . . . . . . . . . . . . . . . . . . . . . . . . 12
2.1.8 A Review of Firebase Database . . . . . . . . . . . . . . . . . 12
2.1.9 Firebase Authentication . . . . . . . . . . . . . . . . . . . . . 13
2.1.10 Firebase Real-Time Database . . . . . . . . . . . . . . . . . . 13
2.1.11 Firebase Cloud Storage . . . . . . . . . . . . . . . . . . . . . . 13

vi
3 The Design Methods and Procedures 14
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1.1 User Requirements . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1.2 Tools and Techniques . . . . . . . . . . . . . . . . . . . . . . . 15
3.1.3 Agile Methodology for Garage Tracking And Parking Appli-
cation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1.4 The Advantages of Agile Methodology . . . . . . . . . . . . . 15
3.1.5 System Requirement Specification . . . . . . . . . . . . . . . . 16
3.1.6 Requirements Analysis . . . . . . . . . . . . . . . . . . . . . . 16
3.1.7 System Specifications . . . . . . . . . . . . . . . . . . . . . . . 17
3.1.8 Agile Methodology for Garage Tracking And Parking Appli-
cation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.1.9 Garage Tracking and Parking Application Requirement Spec-
ifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1.10 Functional System Requirement . . . . . . . . . . . . . . . . . 20
3.1.11 Product Features . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1.12 Garage Owner has access to the following features: . . . . . . 20
3.1.13 Operating Environment . . . . . . . . . . . . . . . . . . . . . 21
3.1.14 Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.1.15 Process Model . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.1.16 System Design . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.1.17 System Flowchart: . . . . . . . . . . . . . . . . . . . . . . . . 24
3.1.18 Admin Control Flowchart . . . . . . . . . . . . . . . . . . . . 25
3.1.19 Data Flow Diagram And Work Flow Diagram . . . . . . . . . 26
3.1.20 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . 28
3.1.21 Entity Relation Diagram (ER): . . . . . . . . . . . . . . . . . 30
3.1.22 Class Diagram: . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.1.23 Sequence Diagram: . . . . . . . . . . . . . . . . . . . . . . . . 33
3.1.24 Gantt Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.1.25 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4 Analysis of design and Specification 38

4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.1.1 User Interface Design . . . . . . . . . . . . . . . . . . . . . . . 38

5 Implementation System Testing 39

5.1 Thoughts behind the Prediction Model . . . . . . . . . . . . . . . . . 39
5.2 Aims and Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.3 History of T20 Cricket . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.4 Game Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

6 Conclusion Future Work 43

6.1 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.1.1 Limitation of the Project . . . . . . . . . . . . . . . . . . . . . 43
6.1.2 Future Works . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

vii
List of Figures

3.1 Agile Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.2 User Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.3 Admin Control Flowchart . . . . . . . . . . . . . . . . . . . . . . . . 26
3.4 Data Flow Diagram-Level 0 . . . . . . . . . . . . . . . . . . . . . . . 27
3.5 Data Flow Diagram-Level 1 . . . . . . . . . . . . . . . . . . . . . . . 27
3.6 Use case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.7 ER Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.8 Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.9 Sequence Diagram-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.10 Sequence Diagram-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.11 Gantt chart of the time estimation of this project . . . . . . . . . . . 36

viii
List of Tables

1
Chapter 1

Introduction

1.1 Introduction
In urban areas, parking has become a major challenge for both garage
owners and drivers. The lack of available parking spots, inefficient
parking management, and difficulties in payment processing can lead
to frustrated drivers, lost revenue for garage owners, and traffic con-
gestion. To address these challenges, we developed a garage tracking
and parking application that provides an integrated solution for garage
owners and drivers.

The Garage Tracking and Parking Application is a web-based appli-

cation that allows garage owners to manage parking operations and
drivers to find and pay for parking. The application features several
modules, including a parking management module, a vehicle tracking
module, a payment processing module, and a reporting module. The
parking management module enables garage owners to manage park-
ing spaces, monitor availability, and assign parking spots to vehicles.
The vehicle tracking module allows drivers to find available parking
spots, track their vehicle location, and receive real-time notifications.
The payment processing module allows drivers to pay for parking us-
ing various payment methods, and the reporting module generates
customized reports for garage owners to analyze parking trends and
optimize parking operations.

The development of the Garage Tracking and Parking Application

was based on the Agile software development methodology, with it-
erative cycles of design, development, testing, and deployment. The
project team utilized various technologies, including Node.js, React,
MongoDB, and Firebase, to develop a scalable, secure, and reliable

2
application.

The aim of this project report is to present the development process

and outcomes of the Garage Tracking and Parking Application. The
report will describe the design, development, testing, and deployment
of the application, and will present the results of user testing and
feedback. The report will also discuss the implications and potential
impact of the Garage Tracking and Parking Application for garage
owners, drivers, and urban transportation.

Overall, the Garage Tracking and Parking Application has the poten-
tial to revolutionize parking operations and provide a more efficient
and convenient solution for garage owners and drivers.

The number of motor vehicles on the roads in cities is ever-increasing,

while parking spaces are becoming increasingly rare. Drivers often
waste a lot of time looking for a parking spot. Vehicles parking is
becoming a big problem in Bangladesh at present. Vehicle parking is
becoming a big problem in Bangladesh at present. Due to insufficient
available areas.Although there are garages in the nearby of shopping
complexes, playgrounds. Inshallah our system will solve the vehicle
parking problem in Dhaka.

1.1.1 Motivations
• Optimized Parking
• Reduced traffic
• Increased Safety
• Enhanced User Experience
• Decreased Management Cost

1.1.2 Objectives
• To track nearby parking garage
• Aims to ensure safe parking

3
 • Parking garage Adaptive Re-use
• Online Tracking system
• To make parking lots more efficient.Aims to ensure safe parking
• Reduce chances of theft significantly
• Reduce the time taken for check-in and check-out of vehicles
• Display the available parking spaces in a particular parking lot
• Display the necessary info and the current status of the parking
lot

1.1.3 Project Questions

The following research questions guided the development and evalua-
tion of the Garage Tracking and Parking Application:
1. What are the key features and functionalities required for a garage
tracking and parking application?
2. What are the user requirements and preferences for a garage
tracking and parking application?
3. How can the Agile software development methodology be applied
to the development of a garage tracking and parking application?
4. What are the performance and usability metrics for evaluating
the Garage Tracking and Parking Application?
5. How can the Garage Tracking and Parking Application improve
parking operations for garage owners and drivers?
6. What are the potential implications and impact of the Garage
Tracking and Parking Application on urban transportation and
parking management?
The research questions aimed to provide a comprehensive understand-
ing of the development process and outcomes of the Garage Tracking
and Parking Application, and to assess its feasibility, usefulness, and
potential impact. The questions also guided the selection of appro-
priate research methods and techniques, such as surveys, interviews,
usability testing, and performance analysis. The results of the research

4
will inform the future development and optimization of the applica-
tion, and provide insights for improving parking operations and urban
transportation.

1.1.4 Contributions of project

The Garage Tracking and Parking Application makes several contri-
butions to the field of parking management and urban transportation.
The key contributions of the project are as follows:
1. Streamlined Parking Management: The application provides a
streamlined and efficient solution for garage owners to manage
parking operations. The parking management module allows
garage owners to monitor parking availability, assign parking
spots, and track vehicle locations in real time, leading to more
efficient use of parking spaces and increased revenue for garage
owners.
2. Convenient Vehicle Tracking: The vehicle tracking module of the
application provides drivers with a convenient way to find avail-
able parking spots, track their vehicle location, and receive real-
time notifications. This feature reduces the time and effort re-
quired for drivers to locate and park their vehicles, leading to
reduced traffic congestion and improved urban transportation.
3. Secure and Scalable Technology: The development of the applica-
tion using secure and scalable technologies such as Node.js, React,
MongoDB, and Firebase ensures that the application is reliable,
efficient, and can handle a large volume of users and data. This
contribution ensures that the application can be used in a vari-
ety of settings, from small parking garages to large commercial
parking lots.
4. Customizable Reporting: The reporting module of the applica-
tion allows garage owners to generate customized reports to an-
alyze parking trends and optimize parking operations. This con-
tribution provides garage owners with valuable insights into the
usage of their parking spaces and allows them to make data-driven
decisions.
Overall, the Garage Tracking and Parking Application makes signif-
icant contributions to the field of parking management and urban

5
transportation. The application provides a user-friendly and efficient
solution for parking operations, and its future development and op-
timization could lead to new features and applications that improve
parking management and urban transportation.

1.1.5 Project Outline

• Chapter 2: Literature Review In this chapter, we have described
the literature review, project gap, and proposed solution of our
developing system.
• Chapter 3: Requirements Analysis and System Specifications In
this chapter, we show requirements analysis, system specifica-
tions, project features, operating environment, and methodology.
• Chapter 4: System Design In this chapter, we have described
different kinds of Unified Modeling Language (UML) diagrams.
• Chapter 5: Design specification In this chapter, we have shared
our design and specification.
• Chapter 6: Conclusion In this chapter, we introduced the purpose
of our work and major results, limitations of the project and
practical implications. Also, we shared our future plan for this
project.

6
Chapter 2

Literature Review

2.1 Problem Domain

The management of parking spaces has been a persistent problem in
urban areas. With the growth of the global population, more and
more people are moving to urban areas, leading to increased demand
for parking spaces. In many cities, parking spaces are limited, lead-
ing to parking congestion, high parking fees, and difficulty in locating
available parking spots. The problem is further compounded by ineffi-
cient parking management systems that result in underutilized parking
spaces, which, in turn, leads to lost revenue for garage owners.

The current parking management systems are outdated and lack the
necessary features to cater to the modern needs of garage owners and
drivers. The traditional methods of paper-based systems or manually
tracking vehicles have proven to be inefficient and unreliable. These
methods can lead to errors, inaccurate tracking of parking spots, and
a lack of real-time updates on parking availability.

The garage tracking and parking application aims to address these

challenges by providing a digital solution for parking management.
The application enables garage owners to manage parking operations
effectively and efficiently while providing drivers with real-time up-
dates on parking availability and vehicle tracking.

Overall, the problem domain of parking management presents several

challenges that need to be addressed to improve the quality of park-
ing operations and reduce traffic congestion. The Garage Tracking
and Parking Application provides a solution to address these chal-

7
lenges and could contribute to more efficient and effective parking
management in urban areas.

2.1.1 Related Works

The development of the Garage Tracking and Parking Application
builds on previous research and related works in the field of park-
ing management and urban transportation. The following is a brief
overview of some of the related works that informed the development
of the application:
1. Smart Parking Systems: Smart parking systems use advanced
technologies, such as sensors and internet of things (IoT) devices,
to monitor parking availability and guide drivers to available
parking spots. These systems have been shown to reduce traf-
fic congestion and improve the efficiency of parking operations.
The Garage Tracking and Parking Application takes advantage
of similar technologies to provide drivers with real-time updates
on parking availability.
2. Parking Apps: There are several parking apps available in the
market that allow drivers to locate and reserve parking spots.
These apps often lack the functionality to manage parking oper-
ations for garage owners. The Garage Tracking and Parking Ap-
plication provides a comprehensive solution that caters to both
garage owners and drivers.
3. Agile Software Development: Agile software development is an
iterative and flexible approach to software development that pri-
oritizes collaboration and customer satisfaction. The develop-
ment of the Garage Tracking and Parking Application followed
the agile methodology, which ensured that the application met
the needs and preferences of garage owners and drivers.
4. Performance Metrics: There are several performance metrics that
are commonly used to evaluate the efficiency and effectiveness of
parking management systems, such as parking occupancy rate,
turnover rate, and revenue per space. The Garage Tracking and
Parking Application takes into account these metrics to provide
garage owners with valuable insights into their parking operations
and optimize parking usage.

8
The related works informed the design and development of the Garage
Tracking and Parking Application and provided a framework for eval-
uating its performance and impact. The application builds on the
strengths of existing solutions while addressing their limitations to
provide a comprehensive and efficient solution for parking manage-
ment and urban transportation.

2.1.2 Limitations of the Existing Projects

Garage tracking and parking applications have become popular in
Bangladesh in recent years, and while they can be helpful for many
people, there are also some limitations to existing projects. Here are
some possible limitations:
1. Cost: Some garage tracking and parking applications require ex-
pensive hardware and infrastructure, such as sensors, cameras,
and network connections, which can be costly for both the de-
velopers and the users. This cost can limit the adoption of the
application, especially for those who do not have the resources to
invest in expensive hardware.
2. Security: Another limitation of existing garage tracking and
parking applications is their security. These applications collect
and store sensitive data, such as the location and movement of
the vehicle and the personal information of the user, which can
be vulnerable to cyber-attacks and privacy breaches.
3. User adoption: Finally, one of the major limitations of garage
tracking and parking applications is user adoption. Some users
may be reluctant to use the application due to concerns about
privacy, complexity, or inconvenience. In some cases, the appli-
cation may not offer enough benefits to users to justify the time
and effort required to use it.
4. Limited coverage: Many garage tracking and parking applica-
tions are designed for specific areas, such as cities or parking lots,
and may not cover all locations. This limitation can make the
application less useful for those who travel frequently or park in
different locations.

9
2.1.3 Proposed Solutions
The purpose of this project is to develop a mobile application that
allows users to easily find parking spots in garages and track their
vehicle location in real time. The application will help users save time
and reduce stress by providing them with real-time information about
garage occupancy and available parking spots.

Proposed Solution
The proposed solution is a mobile application that will be available
for iOS and Android devices. The application will use a combination
of sensors, cameras, and machine learning algorithms to track garage
occupancy and available parking spots. The application will also use
GPS and cellular networks to track the location of the user’s vehicle
in real-time.

The application will have the following features:

• Garage Tracking
Real-time information about garage occupancy and available park-
ing spots. Location-based search for garages near the user’s cur-
rent location. Garage reviews and ratings from other users.
• Parking Tracking
Real-time location tracking of the user’s vehicle.Parking history
and time tracking.Notifications for when the user’s parking time
is about to expire.
• Methodology
The development of the garage tracking and parking application
will be done in several phases. The first phase will involve the
development of the user interface and basic functionality. This
will include the ability to search for garages and view garage oc-
cupancy, as well as the ability to track the user’s vehicle location.

The second phase will involve the integration of sensors and cam-
eras into the application. This will enable the application to pro-
vide real-time information about garage occupancy and available
parking spots.
The third phase will involve the development of machine learning

10
 algorithms that can accurately predict garage occupancy based
on historical data and real-time sensor information.
The final phase will involve the development of additional features
such as parking history and time tracking, as well as notifications
for when the user’s parking time is about to expire.

Conclusion
In conclusion, the garage tracking and parking application will
be a useful tool for drivers who are looking for parking spots in
garages. The application will provide real-time information about
garage occupancy and available parking spots, as well as track
the user’s vehicle location in real-time. With the development
of machine learning algorithms, the application will be able to
accurately predict garage occupancy based on historical data and
real-time sensor information.

2.1.4 Compression with Existing And Proposed System

In the above section of Related Work And Limitations of Existing
Projects, we have al- ready discussed the existing system and their
problems. Now in our project, we attempted to fix the problems of
the previous system and to develop some new ideas in our system. In
earlier systems, we’ve noticed that there was no greater or effective
function than simply supplying location information about our city.
Now the point is what’s new in our system? In addition to just location
information in our system, we’ve tried to come up with some useful
functions, such as a parking option, add garage spot option, easy
google map option, parking time schedule and user feedback option.
These users will be able to get the most out of our system’s parking
and garage-related features in a short amount of time without relying
on any other sources. All of the features of our system are described
in depth in Chapter 4.

2.1.5 Review Compression

The differences between our systems and prior systems are shown in
Table 2.1. There are many more such systems, not all of which can be
shown in the table. We have tried to show as much as possible why
our system is better than the previous ones.

11
2.1.6 Mobile Application Review
In recent years, mobile applications have expanded significantly. Ac-
cording to market research firm Gartner, 102 billion apps were down-
loaded in 2013, up 44.4 percent from the previous year’s 18 billion
dollar. According to the Analysis Report, the app industry in the Eu-
ropean Union earns more than C10 billion in revenue each year. The
first mo- bile application on the worldwide network supplied general-
purpose information and information services, such as email, calendar,
stock market, listings, and weather information. However, the need for
mobile applications, as well as the ability to produce them, has spread
to other areas, such as mobile games, factory automation, GPS, and
so on. The expansion in the number and variety of applications has
spawned a plethora of new fields. Many services, such as detecting
location and internet banking, monitor- ing, purchasing tickets, and
even mobile medical services, increasingly rely on mobile application
technology [6]. The quality of mobile applications for commercial or
per- sonal usage, in particular, is important to all stakeholders since
failures can have major effects, such as damage to a company’s brand
or financial loss. Other programs require a reasonable level of quality
to persuade users to utilize them [7]

2.1.7 A Review of XML

A review of XML-compliant user interface description languages is
produced that compares a significant selection of various languages ad-
dressing different goals, such as multi-platform user interfaces, device
independence, content delivery, and user interfaces virtually defined.
There has been a long history and tradition to attempt to capture the
essence of user interfaces at various levels of abstraction for different
purposes.

2.1.8 A Review of Firebase Database

Firebase is fantastic if you want to create something out of nothing
in a flash, making it great for rapid prototyping [10]. Firebase can be
your go-to solution if you have a broad idea of what you want to do
and require a fully configured backend to connect to. Because it’s a
Google product, it’s fully integrated with the rest of the company’s
ecosystem. This applies to all Google Drive products, particularly

12
Google Sheets.

2.1.9 Firebase Authentication

Firebase Authentication promises to make creating secure authenti-
cation systems sim- ple while also enhancing end-user sign-in and on-
boarding. It offers an end-to-end identity solution that includes email
and password accounts, phone authentication, and Google, Twitter,
Facebook, and GitHub login, among other things.

2.1.10 Firebase Real-Time Database

The Firebase Realtime Database is a database that is hosted in the
cloud. Data is saved in JSON format and synchronized in real time
across all connected clients. When any- one use Apple, Android, and
JavaScript SDKs to create cross-platform apps, all of their clients share
a single Realtime Database instance and are automatically updated
with the most recent data.

2.1.11 Firebase Cloud Storage

App developers who need to store and serve user-generated material,
like images or videos, can use Cloud Storage for Firebase. Cloud
Storage for Firebase is a Google- scaled object storage service that
is powerful, easy, and cost-effective. Regardless of network condition,
the Firebase SDKs for Cloud Storage give Google security to file up-
loads and downloads for your Firebase apps.

Summary
Our website is a like a first aid which meets all necessity to the stu-
dents. It can be so convenient to get the user updated about their
study and programming related infotion. In our website, we will serve
better facilities for the students. This website can share any informa-
tion in quick time. That is time saving. Our website provide more
informa- tion about the university and other knowledge. Through this
website any students can participate various events.

13
Chapter 3

The Design Methods and

Procedures

3.1 Introduction
In this chapter, we proposed our project’s system architecture. The
system architecture is described in detail in each section. We’ve in-
cluded our system’s Design Methods and Procedures. Provided step-
by-step diagrams so that a developer and other professionals can ex-
amine the system’s mechanism.

The garage tracking and parking application is a mobile application

designed to help users find available parking spots in garages and track
the location of their parked vehicles in real time. In order to build a
successful application, a thorough analysis of the requirements and
system specifications must be conducted.

3.1.1 User Requirements

The purpose of the garage tracking and parking application is to pro-
vide users with a convenient and efficient way to find parking spots
in garages and track the location of their parked vehicles in real time.
In order to build an application that meets the needs of the users, a
thorough analysis of the user requirements must be conducted.

14
 Figure 3.1: Agile Model

3.1.2 Tools and Techniques

3.1.3 Agile Methodology for Garage Tracking And Parking
Application
Agile software development is a collection of iterative software devel-
opment approaches in which requirements and solutions are generated
through cooperation between self-organizing cross-functional teams
[11]. Agile approaches break down a project into smaller, more man-
ageable chunks. These designs have gone through numerous stages of
development. We chose Agile for our project because it allows teams
to quickly adjust to new needs without- sacrificing release dates. Agile
also helps to eliminate technical challenges, boost customer happiness,
and produce a higher-quality product. We use the agile technique as
well as the SDLC model to create our project. Which is followed by
the steps depicted in Figure 3.1.

3.1.4 The Advantages of Agile Methodology

Agile Methodology enables teams to manage work more efficiently and
effectively, resulting in a higher-quality product delivered on time and
on budget. Agile is more than just change adaptation. Because of
the following benefits, the evolutionary agile methodology has been

15
chosen:
• It’s simple and easy to use.
• Flexible for developers to develop any system.
• This model is a highly realistic software development technique.
• Using this method encourages teamwork through collaboration
and cross-training.
• Suitable for implementation needs that are either constant or
changing.
• It reduces the amount of time spent on development in general.

3.1.5 System Requirement Specification

A system requirements specification is a document that explains what
the software will accomplish and how it will work. It also outlines the
functionality that the product must have in order to meet the needs
of all types of users.

3.1.6 Requirements Analysis

The requirements analysis phase of the project will involve identifying
and analyzing the functional and non-functional requirements of the
application. Functional requirements are features and functions that
the application must perform, while non-functional requirements are
constraints that the application must adhere to in order to be success-
ful. Some examples of functional requirements for the garage tracking
and parking application include:

• The ability to search for garages near the user’s current location
• Real-time information about garage occupancy and available park-
ing spots
• Real-time location tracking of the user’s vehicle
• Notifications for when the user’s parking time is about to expire

Some examples of non-functional requirements for the garage

tracking and parking application include:

16
 • The application must be user-friendly and intuitive

The application must be compatible with both iOS and Android

devices
• The application must have a fast response time for real-time up-
dates
• The application must be secure and protect user data

3.1.7 System Specifications

The system specifications phase of the project will involve outlining
the hardware and software requirements for the application. Some of
the key system specifications for the garage tracking and parking ap-
plication include:

• Mobile device compatibility: The application must be compatible

with both iOS and Android devices.
• Sensor integration: The application must integrate with sen-
sors and cameras in order to provide real-time information about
garage occupancy and available parking spots.
• Machine learning algorithms: The application must use machine
learning algorithms to accurately predict garage occupancy based
on historical data and real-time sensor information.
• Database management: The application must store user data and
parking history in a secure and efficient database.
• Network connectivity: The application must be able to connect
to cellular networks and GPS in order to provide real-time loca-
tion tracking.

Conclusion
The requirements analysis and system specifications phase of the
project is crucial for building a successful garage tracking and
parking application. By identifying and analyzing the functional

17
 and non-functional requirements, as well as outlining the hard-
ware and software specifications, the development team can en-
sure that the application meets the needs of the users and func-
tions properly on various devices and networks.

3.1.8 Agile Methodology for Garage Tracking And Parking

Application
Agile software development is a collection of iterative software devel-
opment approaches in which requirements and solutions are generated
through cooperation between self-organizing cross-functional teams
[11]. Agile approaches break down a project into smaller, more man-
ageable chunks. These designs have gone through numerous stages of
development. We chose Agile for our project because it allows teams
to quickly adjust to new needs with- out sacrificing release dates. Agile
also helps to eliminate technical challenges, boost customer happiness,
and produce a higher-quality product. We use the agile technique as
well as the SDLC model to create our project. Which is followed by
the steps depicted in Figure 3.1.

User Groups
The garage tracking and parking application is designed to meet the
needs of several user groups, including:
• Drivers who are looking for available parking spots in garages
• Drivers who have parked their vehicle in a garage and want to
track its location
• Garage owners and operators who want to provide real-time in-
formation about garage occupancy and available parking spots to
drivers

18
Driver User Requirements

Drivers who are using the garage tracking and parking application
have the following requirements:
• Ability to search for garages near their current location
• Real-time information about garage occupancy and available park-
ing spots
• Ability to filter search results based on location, availability, price,
and other criteria
• Real-time location tracking of their parked vehicle
• Notifications for when their parking time is about to expire
• In-app payment options for parking fees.
Garage Owner/Operator User Requirements

Garage owners and operators who are using the garage tracking and
parking application have the following requirements:
• Ability to provide real-time information about garage occupancy
and available parking spots
• Ability to manage parking fees and payment options through the
application
• Access to data and analytics about garage occupancy and usage
patterns
• Ability to communicate with drivers through the application,
such as sending notifications about garage closures or mainte-
nance issues.
Conclusion
In conclusion, the garage tracking and parking application must meet
the needs of both drivers and garage owners/operators in order to be
successful. By identifying the specific user requirements of each group,
the development team can ensure that the application provides a user-
friendly experience and meets the needs of the target audience.

19
3.1.9 Garage Tracking and Parking Application Require-
ment Specifications
Here in this project we use adobe photo-shop, adobe illustrator and
adobe XD. Also we used Laravel and MySQL for back-end and for
front-end we use HTML, CSS, JavaScript and Bootstrap 5. Here we
use SQL for database.

3.1.10 Functional System Requirement

This section gives us an overview of the system functional requirements
for the Garage Tracking And Parking System For Flutter. In our
system, there are three types of users. User, Garage Owner, Admin.

3.1.11 Product Features

The following are the main features that are to be achieved from the
development of the Green University Computer Club:

Our Apps features:

• Ability to search for garages near their current location
• Real-time information about garage occupancy and available park-
ing spots
• Ability to filter search results based on location, availability, price,
and other criteria
• Real-time location tracking of their parked vehicle
• Notifications for when their parking time is about to expire
• In-app payment options for parking fees

3.1.12 Garage Owner has access to the following features:

Garage owners and operators who are using the garage tracking and
parking application have the following requirements:
• Ability to provide real-time information about garage occupancy
and available parking spots
• Ability to manage parking fees and payment options through the
application

20
 • Access to data and analytics about garage occupancy and usage
patterns
• Ability to communicate with drivers through the application,
such as sending notifications about garage closures or mainte-
nance issues
Admin has access to the following features:
• Admin can manage all the users accounts.
• The admin has the ability to add, delete, and alter the informa-
tion for each place
• The database will be managed by the admin, who will also keep
the system up to date.

3.1.13 Operating Environment

First of all our project is web-based. We used UI, UX for the design
in this website. We used some software like visual studio code, also
used adobe photo-shop as designing tools. We work with HTML, CSS,
JavaScript, MySQL, laravel etc as programming languages for made
our project. We also used other software like MySQL

3.1.14 Methodology
The Garage Tracking and Parking Application is an Android-based
mobile application that enables users to track their garage activities,
such as parking and vehicle maintenance. This application is designed
to make the garage management process easier, faster, and more effi-
cient.

The objectives of this project are as follows:

• To develop a mobile application that can help users keep track of
their garage activities.
• To create an easy-to-use interface that is accessible to everyone.
• To provide users with a platform that can store all of their garage
information in one place.
• To enable users to receive notifications and reminders for impor-
tant events, such as scheduled maintenance.

21
Methodology

• Research: The first step in the development process was to re-

search the current state of garage management applications. This
involved conducting a comprehensive survey of the available ap-
plications, their features, and their user reviews.
• Design: After researching the existing applications, a design was
created for the Garage Tracking and Parking Application. This
design was based on the feedback from the research and aimed
to create a simple and intuitive interface that users could easily
navigate.
• Development: The next step was to develop the application. This
involved coding the application using Java programming language
and the Android Studio development environment. The applica-
tion was developed to be compatible with the latest versions of
Android.
• Testing: The Garage Tracking and Parking Application was thor-
oughly tested to ensure that it was functional and free of bugs.
The application was tested on various devices to ensure that it
was compatible with different screen sizes and resolutions.
• Deployment: Once the testing was complete, the application was
deployed to the Google Play Store, where it was made available
for download by users.
Features
The Garage Tracking and Parking Application includes the following
features:
• Parking Tracker: Users can track the location of their parked
vehicle and set a reminder for when it’s time to move their vehicle.
• Maintenance Tracker: Users can set reminders for scheduled main-
tenance and keep track of when the maintenance was last per-
formed.
• Fuel Tracker: Users can track their fuel usage and set reminders
for when it’s time to refuel.

22
 • Expense Tracker: Users can track their expenses related to their
vehicle, such as repairs, fuel, and insurance.
• Notifications: The application sends notifications to users for
scheduled maintenance, fueling, and other important events.

3.1.15 Process Model

23
3.1.16 System Design
The process of defining parts of a system, such as modules, architec-
tures, components, and their interfaces, as well as system data, based
on given requirements is known as system design. This is the process
of identifying, creating, and building a system that meets a company’s
or organization’s specific objectives and specifications. A graphic or
text modeling language can be used to define designs. Some exam-
ples of graphical modeling languages are Flowchart, Block diagram,
Schema diagram, Use case diagram etc.

3.1.17 System Flowchart:

Figure 1 depicts a user flowchart diagram, whereas Figure 2 illustrates
an administrator flowchart design. A flowchart of a system describes
how information flows through a system and how decisions are made to
control events. The system flowchart depicts decisions that modify the
logic flow of the program. In a system flowchart, the diamond symbol
is used to express yes/no decisions, with a separate line departing the
diamond for each response. They are linked in order to demonstrate
where data goes and what happens to it.

24
 Figure 3.2: User Flowchart

3.1.18 Admin Control Flowchart

According to the Admin flowchart in Figure 2, if an admin uses our
applications, he or she will be directed to the login page first, and if the
admin does not register, he or she will be directed to the registration
page before utilizing our apps. After login in, the administrator can
delete, edit, or add new information from several locations. Finally,
we’ll be able to log out of our system.

25
 Figure 3.3: Admin Control Flowchart

3.1.19 Data Flow Diagram And Work Flow Diagram

Below are data flow diagrams of the green university computer club
part of this project. We have attached the level 0 level 1 and work
flow diagram of this project as you can see in the Figure 4.2 and 4.3

26
Figure 3.4: Data Flow Diagram-Level 0

Figure 3.5: Data Flow Diagram-Level 1

27
3.1.20 Use Case Diagram
Use-case diagrams depict a system’s high-level functions and scope.
The interactions between the system and its actors are also depicted
in these diagrams. In use-case diagrams, the use cases and actors
describe what the system does and how it does it. It is used by the
actors, but not by the system itself.

28
Figure 3.6: Use case Diagram

29
3.1.21 Entity Relation Diagram (ER):
An Entity–relationship (ER) diagram describes the structure of a
database with the use of a diagram. An ER diagram is used to repre-
sent the relationship between entity sets. In a database management
system, an entity is a table or an attribute of a table; thus, an ER
diagram displays the whole logical structure of a database by exhibit-
ing relationships between tables and their characteristics. Figure 4
depicts our project’s ER diagram.

30
 Figure 3.7: ER Diagram

The ER diagram shows how many database tables our project will
or will not have, as well as the primary key and foreign key details,
such as Account ID home owner with authentication table, and the
relationship with pick-up option. Relationship between the End User
Table, Garage Owner Table, and the Pick-up Table and the Rent.
As a result, this page displays a wide range of relationships shown in
figure 4.5 E-R Diagram.

31
3.1.22 Class Diagram:

32
 Figure 3.8: Class Diagram

3.1.23 Sequence Diagram:

33
Figure 3.9: Sequence Diagram-1

Figure 3.10: Sequence Diagram-2

34
3.1.24 Gantt Chart
Below is a Gantt chart of this project as an initial schedule of tasks
to be completed throughout the project life cycle.

35
Figure 3.11: Gantt chart of the time estimation of this project

36
A Gantt chart is a bar chart that provides a visual view of project
tasks scheduled over time. A Gantt chart is used for project planning:
it’s a useful way of showing what work is scheduled to be done on
specific days. The above chart gives an idea about twelve month and
activities of our project. Here the activities part, we include research,
define specification, project planning, development, test plan, testing
question and answer also include delivery activities as you can see in
the Figure 3.1.

3.1.25 Conclusion
In conclusion, the Garage Tracking and Parking Application is an
Android-based mobile application that can help users keep track of
their garage activities. It provides an easy-to-use interface that al-
lows users to store all of their garage information in one place. The
application includes features such as parking tracking, maintenance
tracking, fuel tracking, and expense tracking, and sends notifications
to users for important events. The development of this application
followed a methodology that involved research, design, development,
testing, and deployment.

The architecture of our system design is shown in this chapter. We

tried to clarify how each aspect of our system works using various
diagrams such as flowchart diagram, data-flow diagram, use case di-
agrams, ER-diagrams, sequence diagrams, Class diagrams, and gantt
Chart.

37
Chapter 4

Analysis of design and

Specification

4.1 Introduction
The design specification is the foundation of the design concept and
describes the exact operation and attributes of a system. Creating a
clear and unambiguous design specification for tiny designs is a rela-
tively simple undertaking. Design Specification, on the other hand, is
a description of how a design is created. We try to display the design
of our mobile application in the Analysis of Design and Specification
area. We also reviewed a variety of tools that we employ in the devel-
opment of our applications. And we will explain step by step how we
have implemented these tools in our project.

4.1.1 User Interface Design

The Android application basically has to use XML markup language
for any design and we have used XML language for design in our
project. The user interface is very important for any feature or ap-
plication or website. The user-friendly user interface of a website or
application, the more usable than others. Usually, when a user wants
to take advantage of an Android app or a feature, the first thing this
user expects is an attractive graphical interface. They want to read
less text, that’s-why the design needs something that users can eas-
ily understand what they can do from here. So we did those designs
through XML markup language and later added it to the back-end
through Java code.

38
Chapter 5

Implementation System Testing

5.1 Thoughts behind the Prediction Model

There have been research done on ODI and Test match cricket but
very few on T20 cricket, which is currently more favourite than its
older brothers. And that’s why we decided to do research on this for-
mat of the game. The result of a T20 cricket match depends on lots of
in game and pre-game attributes. Pre-game attributes like condition,
venue, pitch, team strength etc. and in game attributes like wickets
in hand, run rate, total run, strike rate etc. influence a match result
predominantly. We gave more emphasis on in game attributes as our
prediction will be when match is in progress. Our intentions would
be to finding out the attributes which is most affecting the result in
different phases of the game. We broke an innings into three phases:
Power-play (1-6 overs), Mid-overs (7- 16) and - final overs (17-20).
Prediction will be active till the last over of mid overs phase. We con-
sider an entire cycle of process of data mining, decision making and
preparing a model to predict. Mining the data according to the at-
tributes and different phases we have divided important to construct
meaningful statistics. Modeling a problem for prediction requires sev-
eral intelligent assumptions and molding the problem with collected
data-sets. As we already mentioned cricket is a game of uncertainty
and T20 format is the most unpredictable format rather than the other
two format because it is the shortest format of the game and one over
can change the result of a game. In this research we tried to design
a prediction model which can go with this unpredictability and try to
make a result prediction.

39
5.2 Aims and Objectives
The aim is to prepare a model which will predict the result of a T20
cricket game while the match is in progress. Our main objective is to
combine pre-game data and in-game data in order to design a good
predictive model. Understanding the different attributes is also needed
in order to get more accuracy in result.

5.3 History of T20 Cricket

From the sixteenth century to first official Test match in 1877 to first
ODI World Cup 1975 with 60 overs to 50 overs world in 1987, cricket
world has changed a lot. Now, we have a new shortest format in
cricket - Twenty20 or T20. T20 cricket is fun, entertaining and more
thrilling than other two formats. It has brought glamour and instant
popularity to the fans and helped marketing Cricket to the rest of the
world. England Cricket Board (ECB) was looking for a cricket compe-
tition to fill the void after the conclusion of Benson and Hedges Cup in
2002. ECB was looking for something new to at-tract more sponsors
and viewers. Marketing Manager of ECB, Stuart Robertson was the
first to came up with the idea of playing cricket match with each team
getting only 20 overs to play. Thus came the name Twenty20. First
official T20 matches were played in English counties. Though first of-
ficial T20 international match took place be-tween Australia and New
Zealand. In 2007 we witnessed ICC World Twenty20, which gener-
ated immense support for this newest form of cricket. Introduction of
T20 cricket gave birth to franchise league in many countries. Among
those Indian Premier League (IPL) is the most watched and expen-
sive cricket league. Big Bash, Caribbean Premier League (CPL) and
Bangladesh Premier League (BPL) other popular franchise leagues.
T20 cricket showed great innovation in batting style, improved field-
ing. Bowlers were also trying their hardest to make them useful in a
format which was made to give preference to the batsmen. With more
viewers and sponsors, T20 cricket brought more money to the Boards
and players. But this format also attracted more illegal activities as
matching fixing, betting, miss con-duct of players. Very recently in
July 2015 BCCI banned Chennai Super Kings and Rajasthan Royals
for match fixing. Ironically this two teams are two of the most suc-
cessful team in IPL with a large number of fan base. The West Indies

40
regional teams completed in tournament named Stanford 20/20 which
was funded by a convicted fraudster Allen Stanford.

5.4 Game Method

After Football, Cricket is the second most popular sports with a fan
base of around 2.5 billion (according to Top End Sports) and mostly
popular in South Asia, Australia, The Caribbean and UK. In inter-
national level Cricket is played in three formats- Test, ODI and T20I
cricket. This game is played on a 22 yards clay pitch with 2 sets of
stamps, each set with 3 stamps and each set having two bells on top of
them. Two batsmen come to pitch with two wooden bats and bowler
bowls with a cricket ball which outer part is made of lather. Test
Cricket is played Red ball which is slightly heavier than the White
bowl played in the limited overs. There is no fixed size of the outfield,
but usually its diameter usually varies between 137 meters and 150
meters. In limited over cricket there is a circle of 30 yards around
the pitch which work as a field restriction for players. Test cricket
is played for 5 days with each team having at most 2 innings. ODI
played for 50 overs per innings and T20 played in 20 overs. Each
team play with 11 players. A coin toss decides who is going to bat
or ball first. In limited over cricket team batting first scores as many
run possible before the overs are finished or they all get out. If team
batting next score more runs they wins and failure to score required
runs in allocated overs or getting all out result in loss for team batting
second. Some basic idea how the game is played: Field Restriction:
According to the latest rule change in 50 overs cricket, there is only
one Power play from over 1-10 with only two fielders outside of the
30 yards circle. Between 11 to 40 overs four fielder are allowed and
five allowed outside the 30 yards circle in the final 10 overs. Like the
ODI format T20 also have only 1 power play form over 1 to 6 with 2
fielders outside the circle. Scoring Runs: The striking batsman must
hit the ball with his bat and must change his position with his partner
to score 1 run. Number of runs scored depend on the number of time
the batsmen change position. If the batsman hit ball and its goes
outside the boundary 4 runs are added and 6 runs are added when the
ball fly over the boundary. Batting team gets extra runs form No ball,
Leg bye, Bye, Wide, Overthrows and Penalty runs when the ball hits
keeper’s helmet or cap lying on the field. Out Types: Batsmen usually

41
get out by being bowled, caught, leg before wicket (LBW), stumped
and run out. There are some rare occasion where batsmen get out
by hit wicket, intentionally hitting the ball twice, handled the ball,
obstructing the field and timed out. Tie match result: If the match is
tie, such as both the team scored same runs then there is a rule called
super over. Super over played for only one over for each team. Each
team can play with two wickets when they are batting and one single
bowler when they are bowling. Batting first team set a target and
second team chase it. In Test cricket there is no restriction on how
many overs a bowler can bowl. But in limited over cricket number
of overs bowled by a single bowler is fixed. in ODI’s each bowler can
bowl up to 10 overs in a match and in T20 cricket bowlers are allowed
to bowl only 4 overs each.

42
Chapter 6

Conclusion Future Work

6.1 Conclusion
This application is developed to provide best parking and garage ser-
vices to the users. We worked extremely hard and came a long way,
finally our project’s android-based mobile appli- cation was success-
fully implemented at the end. In order to implement our application,
we tested it on a variety of smart phones. We observed that our system
functioned well and that all of its features produced accurate results.
This project provide better flexi- bility and performance and it de-
creases the cost and time and it is very easy to use. The user interface
does not appear to be a complicated view because it has so simple
design. Our application can be used in a gentle manner by users. We
hope that users will utilize our app and receive adequate service.

6.1.1 Limitation of the Project

We’ve previously addressed the limitations of the prior system. We
are essentially creating our new system due to the limitations of the
existing system. But all systems have some limitations. There are
some limitations to our system. We will try to overcome this limita-
tion in future:

• We use Firebase database it has restricted querying capabilities.

• Users or saved files cannot be queried or listed.
• Payment only manually
• Currently, our app will work for a limited area in Dhaka city.

43
 • Manually can be confirmed through phone call.
• Prefect result short distance.
• Although the app has details of all the places, it does not deal
with security issues while inspecting.

6.1.2 Future Works

Our system has an option for user feedback. Through which we can
know the opinions and suggestions of different users. We will update
our system in the future based on that advice. Also, we have our own
plans for this project and we will try to develop them.

• We will use the paid version of Firebase Database.

• There is no better transportation in the marginal level, we will
work on it so that user doesn’t have to worry about travel.
• Although the app has details of all the places, it does not deal
with security issues while inspecting. In future we will work for
this issue.
• In the future we have plans to add an online marketplace type
system with this system. Where a variety of travel related prod-
ucts can be found.
• We will develop a website for this system.
Overall, the potential for future development of a garage tracking and
parking application is vast, and there are many possibilities for ex-
panding its features and functionality to meet the needs of users.

44