Fyp Doc Sample 5 It

Final Year Project
E-Parking
By
SAUJANYA REGMI
NP000117
NP3F1901IT
A report submitted in partial fulfillment of the requirements of Asia Pacific
University of Technology and Innovation for the degree of
B.Sc. (Hons) Information
Technology Supervised by Ms.
nd
Dolma Sherpa 2 Marker: Mr. Ravi
Rauniyar
26-January-2019
ACKNOWLEDGEMENT
This Final Year Project report is prepared for the partial fulfilment of the requirement for the
degree of BSc.IT in accordance to the rules and regulations prescribed by Asia Pacific
University (APU). I would like to express my deepest gratitude to my college Lord Buddha
Education Foundation (LBEF) and my university APU which provided this opportunity to
learn many things related to Investigation and Research. This project wouldn’t be completed
without the kind cooperation of faculties of this college.
Further, I am grateful to Supervisor Ms. Dolma Sherpa, and Second Supervisor Mr. Ravi
Rauniyar for their guidance and help to complete this project. I also would like to show my
appreciation to all who supported directly or indirectly to complete this project in limited
timeframe.
Sincerely,
Saujanya Regmi (NP000117)

ABSTRACT
E-Parking is a cost effective, efficient, admin portal from which admins can regulate parking
actions. It is a web application that is intended to entertain big parking lots like of Shopping
Malls, Movie Theaters, Big Marts, Hotels, Office Buildings, airports, stadiums, and Colonies.
Where the population of vehicles will be high and where surged parking approach is
implemented. E-Parking clearly is intended to track the parking space/spot to be able to use
the parking spot as the vehicle leaves the parking lot. The system does not use IOT (Internet
of Things) devices.
The general procedure would be: The vehicle identification number is added to the system
and a vacant parking spot is provided. The time in which the VIN (Vehicle Identification
Number) is added is recorded by system as in time. At the time of vehicle exit, VIN is entered
in vehicle exit form. The time of exit is noted and total parking time is calculated. Based on
that the bill gets generated. And, the parking spot status is changed to vacant again in the
system. Nevertheless, total revenue generated is also visible in dashboard and invoice report
in invoice page.
At the end of the research and development, following enhancement were taken into
consideration, use of IOT devices for tracking parking space, fetch VIN at entry and exit
time, which would reduce the direct enrollment of staff in monitoring system. Also, booking
the spot before reaching the parking space by consumer. Never the less limited access right to
user operating the system is also considered in the future enhancement in order to have strong
control over the system.
ABBREVIATION
KMC – Kathmandu Metropolitan City
VIN – Vehicle Identification Number
JSON – Java Script Object Notation
IDE – Integrated Development Environment
ITS – Intelligent Transportation System
VANET – Vehicular Ad-Hock Network
RSU – Restricted Stock Unit
GPS – Global Positioning System
GIS – Geographic Information System
RTVR – Real Time Vehicle Tracking and Recognition
ANPR – Automatic Number Plate Recognition
PHP – Hypertext Preprocessor
ASP.NET – Active Server Page
JSP – Java Server Page
SDM – Software/System Development Methodology
OS – Operating System
RDBMS – Relational Database Management System
SDLC – Software Development Life Cycle
SQL – Scripted Query Language
PL – Procedural Language
Table of Contents
1 CHAPTER 1: INTRODUCTION TO THE STUDY........................................................1
1.1 Background to the project...........................................................................................1
1.2 Problem context...........................................................................................................1
1.3 Rationale......................................................................................................................3
1.4 Potential benefits.........................................................................................................3
1.4.1 Tangible benefits..................................................................................................3
1.4.2 Intangible benefits................................................................................................4
1.5 Target users.................................................................................................................4
1.6 Scope and objectives...................................................................................................4
1.6.1 Aim.......................................................................................................................4
1.6.2 Objectives.............................................................................................................4
1.6.3 Deliverables - Functionality of the proposed system...........................................5
1.6.4 Nature of Challenges............................................................................................5
1.7 Overview of this Investigation report..........................................................................5
1.8 Project Plan..................................................................................................................7
1.8.1 Project Plan for First Semester.............................................................................7
1.8.2 Gantt chart..........................................................................................................10
2 CHAPTER 2: LITERATURE REVIEW........................................................................12
2.1 Introduction...............................................................................................................12
2.2 Domain research........................................................................................................12
2.2.1 Domain Research 1............................................................................................12
2.2.2 Domain Research 2............................................................................................13
2.2.3 Domain Research 3............................................................................................14
2.3 Similar System/s (with similar features)...................................................................15
2.3.1 RTVTR...............................................................................................................15
2.3.2 Park KTM...........................................................................................................15

2.4 Summary....................................................................................................................17
3 CHAPTER 3: TECHNICAL RESEARCH.....................................................................18
3.1 Programming language chosen..................................................................................18
3.2 IDE (Interactive Development Environment) chosen...............................................19
3.3 Database Management System chosen......................................................................19
3.4 Operating System chosen..........................................................................................20
3.5 Summary....................................................................................................................21
4 CHAPTER 4: SYSTEM DEVELOPMENT METHODOLOGY....................................22
4.1 Introduction...............................................................................................................22
4.2 Agile..........................................................................................................................23
4.3 Waterfall....................................................................................................................24
4.4 Spiral..........................................................................................................................25
4.5 Chosen Methodology.................................................................................................26
4.6 Summary....................................................................................................................26
5 CHAPTER 5: RESEARCH METHODS.........................................................................27
5.1 Introduction...............................................................................................................27
5.1.1 Data Gathering Analysis....................................................................................27
5.1.2 Project Deliverables...........................................................................................27
5.1.3 Focus on Methods..............................................................................................27
5.1.4 Data Collection...................................................................................................28
5.2 Design........................................................................................................................28
5.2.1 Observation........................................................................................................28
5.2.2 Questionnaire, Survey, Interviews, Focus Groups.............................................29
5.2.3 Objective of the Question...................................................................................29
5.3 Summary....................................................................................................................32
6 CHAPTER 6: REQUIREMENTS VALIDATION..........................................................33
6.1 Analysis of Data........................................................................................................33

6.1.1 Analysis of data collected through Questionnaire.............................................33
6.2 Summary....................................................................................................................45
7 CHAPTER 7: SYSTEM ARCHITECTURE...................................................................46
7.1 Introduction...............................................................................................................46
7.2 Abstract Architecture.................................................................................................48
7.2.1 System Design....................................................................................................48
7.2.2 Database Design.................................................................................................60
7.2.3 Interface Design (Story Board)..........................................................................65
8 CHAPTER 8: PROJECT PLAN......................................................................................71
8.1 Features......................................................................................................................71
8.2 Details of Release Plan..............................................................................................71
8.2.1 Version 1.0 of e-Parking....................................................................................71
8.2.2 Version 2.0 of e-Parking....................................................................................72
8.3 Test Plan....................................................................................................................72
8.3.1 Unit Testing Plan................................................................................................72
8.3.2 Acceptance Testing Plan....................................................................................76
9 CHAPTER 9: IMPLEMENTATION...............................................................................77
9.1 Screenshots................................................................................................................77
9.1.1 Screenshots for Login Page i.e. Login.cshtml....................................................77
9.1.2 Screenshots for Register/ Sign up i.e. Register.cshtml......................................78
9.1.3 Screenshots for Dashboard.................................................................................79
9.1.4 Screenshots for Vehicle Info List.......................................................................80
9.1.5 Screenshots for Add Parking Lot.......................................................................81
9.1.6 Screenshots for Parking Lot List........................................................................82
9.1.7 Screenshots for Parking Spot.............................................................................83
9.1.8 Screenshots for Booking....................................................................................84
9.1.9 Screenshots for Update Booking........................................................................85

9.1.10 Screenshots for User List...................................................................................86
9.1.11 Screenshots for Add User...................................................................................87
9.1.12 Screenshots for Direct Vehicle Entry.................................................................88
9.1.13 Screenshots for Spot Allocation.........................................................................89
9.1.14 Screenshots for Vehicle Exit..............................................................................90
9.2 Sample Codes............................................................................................................91
9.2.1 Sample codes written for i.e. Login.cshtml........................................................91
9.2.2 Sample codes written for Register.cshtml..........................................................92
9.2.3 Sample codes written for Logout.cshtml.cs.......................................................93
9.2.4 Sample codes written for Create Parking Price..................................................94
10 CHAPTER 10: SYSTEM VALIDATION.......................................................................95
10.1 Unit testing.............................................................................................................95
10.1.1 Unit testing for Login.........................................................................................95
10.1.2 Unit Testing of Register.....................................................................................96
10.2 User acceptance testing..........................................................................................99
11 CHAPTER 11: CONCLUSION AND REFLECTIONS..............................................102
11.1 Critical Evaluation...............................................................................................102
11.2 Limitations...........................................................................................................102
11.3 Future Enhancement............................................................................................103
11.4 Conclusion...........................................................................................................103
12 References......................................................................................................................105
List of Figures
Figure 1: Gantt chart - Project Plan..........................................................................................10

Figure 2: Gantt chart - Project Timeline..................................................................................11
Figure 3: Agile Methodology...................................................................................................23
Figure 4: Iterative Waterfall Methodology..............................................................................24
Figure 5: Spiral Methodology..................................................................................................25
Figure 6: Gender involved on survey.......................................................................................33
Figure 7: Bar diagram showing Occupation of Percipients.....................................................34
Figure 8: Pei Chart - Participants with Vehicle - Statistics......................................................34
Figure 9: Vehicle Type – Pie-Chart.........................................................................................35
Figure 10: Ease to find parking space......................................................................................35
Figure 11: Average time to find parking spot..........................................................................36
Figure 12: Statistics showing people being late due to parking issue......................................36
Figure 13: Participants’ Recommendation on parking system feature....................................37
Figure 14: Current Parking System Rating..............................................................................37
Figure 15: Personal Information Recording Information.........................................................40
Figure 16: Result for recording personal information..............................................................40
Figure 17: Statistics on Using VIN for Space Allocation........................................................41
Figure 18: System Architecture...............................................................................................47
Figure 19: Use Case Diagram..................................................................................................48
Figure 20: Activity Diagram - Register...................................................................................53
Figure 21: Activity Diagram – Login.......................................................................................54
Figure 22: 7.2.1.5 Activity Diagram - - Vehicle Type..........................................................55
Figure 23: Activity Diagram - Parking Lot..............................................................................56
Figure 24: Activity Diagram - Price.........................................................................................57
Figure 25: Activity Diagram - Booking...................................................................................58
Figure 26: Activity Diagram - Direct entry..............................................................................59
Figure 27: Screenshot - Login Page.........................................................................................77
Figure 28: Screenshot - Register page.....................................................................................78
Figure 29: Screenshot - Dashboard..........................................................................................79
Figure 30: Screenshot - Vehicle Info.......................................................................................80
Figure 31: Screenshot - Add Parking Lot................................................................................81
Figure 32: Screenshot - Parking Lot List.................................................................................82
Figure 33: Screenshot - Parking Spot.......................................................................................83
Figure 34: Screenshot - Booking..............................................................................................84
Figure 35: Screenshot - Update Booking.................................................................................85
Figure 36: Screenshot - User list..............................................................................................86
Figure 37: Screenshot - Add user page....................................................................................87
Figure 38: Screenshot - vehicle entry.......................................................................................88
Figure 39: Screenshot - Spot Allocation..................................................................................89
Figure 40: Screenshot - Vehicle Exit.......................................................................................90
Figure 41: Screenshot - Sample Code Login...........................................................................91
Figure 42: Screenshot Sample Code - Register........................................................................92
Figure 43: Screenshot - Sample code Logout..........................................................................93
Figure 44: Screenshot - Create parking price...........................................................................94
List of Tables
Table 1: Project Plan for First Semester....................................................................................7

Table 2: Programming Language Evaluation..........................................................................18
Table 3 : Choosing Database - Evaluation...............................................................................19
Table 4: System Development Methodology...........................................................................22
Table 5: Use Case Specification for Login..............................................................................49
Table 6: Use Case Specification for Register..........................................................................49
Table 7: Use Case Specification for Add Parking Lot.............................................................50
Table 8: Use Case Specification for New Booking.................................................................50
Table 9: Use Case Specification for Update Booking.............................................................51
Table 10: Use Case Specification for Vehicle Entry................................................................51
Table 11: Use Case Specification for Vehicle Exit..................................................................52
Table 12: Use Case Specification for Spot Allocation and Status...........................................52
Table 13: Pms_booking............................................................................................................60
Table 14: Pms_booking_status................................................................................................61
Table 15: Pms_invoice_dtl.......................................................................................................61
Table 16: Pms_parking_price..................................................................................................61
Table 17: Pms_parking_spot....................................................................................................62
Table 18: Pms_parkinglot_dtl..................................................................................................62
Table 19: Pms_parkinglot_mst................................................................................................62
Table 20: Pms_vehicle_detail..................................................................................................63
Table 21: Pms_vehicle_type....................................................................................................63
Table 22: AspNetUsers............................................................................................................64
Table 23: Test Plan for Signup or Register..............................................................................72
Table 24: Test plan for sign in or log in...................................................................................74
Table 25: Test Plan For Add User...........................................................................................75
Table 26: Acceptance testing plan...........................................................................................76
Table 27: Unit Testing - Login.................................................................................................95
Table 28: Unit Testing Register...............................................................................................96
Table 29: Unit Testing Add User.............................................................................................98
Table 30: Acceptance testing - Test 1......................................................................................99
Table 31: Acceptance testing -Test 2.....................................................................................100
Table 32: Acceptance Testing - Test 3...................................................................................101
NP3F1901IT Final Year Project NP000117
1 CHAPTER 1: INTRODUCTION TO THE STUDY

1.1 Background to the project
Parking issues have attracted more and more attention in the past few years, as the number of
motor vehicles are immensely growing. Having an empty car park in a densely populated city
can be very difficult (Like Kathmandu). Most of the time, Drivers will keep wandering
around the parking lot or wait until there's a space at the door to the parking lot. The time
taking parking process contributes to a variety of environmental problems such as extreme
excess fuel and exhaust emissions from cars. Never the less, many official tasks or academic
courses are affected.
E-parking is a web based application for parking management. E-parking is simply an admin
portal from which the admin can regulate the parking actions. E-parking does not entertain
customer to operate the system. The system focuses mostly on the parking lots of Shopping
Malls, Movie Theaters, Big Marts, Hotels, Office Buildings, airports, stadiums, and Colonies.
Where the population of vehicles will be high and where surged parking approach is
implemented.
Most of the cities around the globe has implemented the different parking mechanisms in
order to make parking efficient. By digitalizing the parking system, is sought to help in
vehicle guidance by assigning parking space, managing and monitoring parking spaces, add
vehicle entry and exit record and auto generate parking bill as well as keep track of daily
transaction/income.
In this project, the research will analyze deeper about parking problems, trends, and
techniques on how to make most from the system. The focus field area of the research is the
web based application for parking. From the analysis, the research will be perforated in deep
about how e-Parking can enhance parking efficiency.
1.2 Problem context
Today, over half of the mankind, about 4000 million people, lives in cities areas. Which is
seen to raise to 60% by the year 2030. Cities are having huge mobility, energetic and
pollution problems which ultimately lowers the live quality. Parking spots are hard to find
especially during the rush hours as around 35% of vehicles run on that moment. This is the
reason why
1
parking is very important issue of current generation. Also, it is very important to regulate
vehicle flow and atmospheric pollution (Circontrol, 2019).
The number of parking spaces available in Nepalese cities especially in Kathmandu are
significantly less, compared to the number of cars commuting in the city every day. The
speed at which the new vehicles are being registered is always creating a barrier in
maintaining the equilibrium between demand and supply of parking lots. Thus, increasing the
number of parking lots is never seems the solution (ktm2day, 2018). According to Donald
Shoup, putting a cap on the parking requirement, setting a maximum will limit the
availability of the infrastructure and replace public transport with private vehicles. (Citylab,
2019)
Another factor why private vehicles become the most favored form of transportation is that
the price for the car park is extremely low. In most of the locations throughout Nepal, the
notion of expanded parking is not present, contributing to spillovers.
Since most people prefer road parking rather than off-street parking, the former is more costly
than the latter. This is why people tend to travel in their vehicles at lower costs, which makes
for reasonable charging of all forms of spaces, ease pollution and unnecessary traffic battles,
complaints and injuries. When the parking lots are packed cruising are yet another problem
that is encountered. One of the policies proposed by renowned scholar Donald Shoup avoids
peaks of more than 80 per cent and promotes at least 40%. Parking above 90% leads to long
quest periods and departure lines and the driver wastes his energy. The parking crowd can be
managed from early bird and early off peak discounts. (Nagar, n.d.)
Another major and severe problem is cruising. The shortage of connections to car parks that
lead to long lines and congestion in public places also forces the cars to roll. Parking cruising
causes pollution, leading to waste of time and carbon pollutants. Donald Shoup claimed that
there were cases in which the drivers offered to ride if there was not free parking on the curb
and the car park on the path was open. (Shoup, 2007). Thus by underpricing curb parking,
cities create an economic incentive to cruise. Another factor that impacts in parking is
difficulty to find vacant space and once occupied are not vacated easily. (Shoup, 2015)
The Rising Nepal, one of the newspaper publication wrote on the weak management policy
of Kathmandu Traffic Police and KMC. “Potholes and dust exist everywhere as construction
works are continuing everywhere. In such a chaotic situation, management of traffic and
parking in Kathmandu, where hundreds of vehicles are added each day, is another severe and
dismaying challenge” (therisingnepal, n.d.). This can be considered as the biggest problem,
the
2
disability of such powerful force not able to foresee and tackle the problem of traffic and
parking (B360Nepal, 2019).
1.3 Rationale
According to the problem stated above and government planning to create multistory parking
lots in different parts of Kathmandu valley, an e-Parking will be a standalone web application
which allows parking chaos to control in some extent. The parking lot spaces will be used at
its best with the proper management of parking spaces. Price calculation will be accurate and
convenient ultimately increasing customer-owner relationship. People don’t have to worry
about the parking slip at all. Time has been the most important aspect in busy city like
Kathmandu, searching for minutes for finding parking hour will be cut as the parking space
will be allocated in the time of vehicle entry. Besides that, the owner will be able to monitor
the daily transaction data minimizing the incorrect or inaccurate transaction. This can
certainly grow the business. Nevertheless, the workload of parking staffs will reduce. Here
are the benefits that follow as the outcome of project.
1.4 Potential benefits

1.4.1 Tangible benefits
a. Proper utilization of parking spaces. With proper manipulation of parking spaces,

public will be highly beneficiated.
b. With the proper record of transaction details, no transaction data can be changed, by
which the owner of parking can get accurate transaction data resulting in effective
further planning.
c. The cost benefit analysis can be done whenever wanted and can help in applying new
strategy.
d. When e-parking is managed in a structured way, both access and regulation are very
easy to manage. It'll also be user-friendly and there'll be no problems with the system
for the parking workers.
e. Auto bill generation at the time of exit will cut the extra time of parking staff as well
as vehicle owner.
f. Since the application is web application and can be implemented in multiple parking
lots at a single time will definitely save money
3
1.4.2 Intangible benefits
The intangible benefits that follow tangible benefits are specified below:
a. Public vehicles will get more security.

b. Less work load pressure to parking staffs, as the calculation and report generation is
done by system itself.
c. Helps owners to plan and finalize business logic.
1.5 Target users
It is very important to understand the target market prior to development during research and
collection phase. The architecture and development of the application can be begun by
studying the kinds of users most likely to be interested in the App. Upon defining the
intended consumers, it would be easier to design the app in the context of these users. The
targeted users to operate system are parking staffs as it is an admin system/portal. And the
users that are going to get beneficiated by the system will be drivers as well as parking
owners.
1.6 Scope and objectives

1.6.1 Aim
The aim of the project is to develop a web application for efficient parking management.
Therefore, the users does not have to get stuck for minutes in parking areas to find the
parking space, to pay parking bill etc. Nevertheless, No parking space stays vacant which
ultimately makes most out of parking.
1.6.2 Objectives
The objectives of this project are:

a. To create a system that will show the vacant spaces available for parking.
b. To create a user friendly interface that will calculate time, price & can generate the
bills.
c. To add vehicle identification number (VIN) & allocate space for parking.
d. To create a system that will add, remove and update price based on vehicle type &
parking slot available.
4
1.6.3 Deliverables - Functionality of the proposed system
There is no hard and fast solution for such pace at which the new vehicles are being
registered resulting a barrier in maintaining the equilibrium between demand and supply of
parking lots. But the E-Parking will definitely help in reducing the problems by making most
out of the parking spaces. As it is a web application it can be accessed by any part of the
world and can be implemented to any place.
Following are the lists of actions that the system is seen to perform:-
a. Allows different admins to login to the system at a same time.
b. Allows admin to add Vehicle Identification Number during vehicle entry and Check
out at the time of exit.
c. Automatically tracks entry and exit time as the admin adds VIN and checks out the
vehicle.
d. Automatically calculates parking bill and generates invoice as admin checks out
vehicle.
e. Allows the admin to see number of vacant spaces available.
f. Allows the admin to allocate a parking space to vehicle in the time of entry.
g. Allows the admin to see and generate report of daily transaction.
1.6.4 Nature of Challenges
Since, the number of vehicles is exceeding the number of parking spaces available. The
project will be challenging to manipulate the vehicle flow in parking lot as well. Although,
parking lots being built accommodating more than 2500 cars will definitely help in reducing
the challenge. Browsing experience is one of the most challenging aspect. Different users
might view the application from different screen resolutions, browsers and different version
of browsers. Apart from that, security is another scope that certainly cannot be skipped. Also
proper structuring of the project will be very challenging.
1.7 Overview of this Investigation report
Chapter 1: Introduction
The introduction part is explaining about the current condition of parking, its purpose behind
the development of the proposed system. It explains the scope of e-parking. Also it describes
in detail the rationale, background and then decides the deliverable of the application/system.
5
Chapter 2: Literature Review
In the literature reviews, the most significant chapter, plays a major role in the research study,
in which an in-depth evaluation of inquiries is rendered that are already underway on a
specific topic. This includes knowledge of the different technical and design fields and other
subjects based on previous study. The Literature Review enables developers to identify
consistent information and develop existing knowledge.
Chapter 3: System Development Methodology
SDM is a framework for structuring, organizing and managing the creation of a business. It
addresses the approach for system development used in the creation of the proposed project
and few different methodologies of the option of one.
Chapter 4: Development/Deployment
The implementation and delivery areas and the technology conditions selected for the
proposed project will be addressed in this chapter. There are a few very important aspects of
potential comparisons between them in this portion. Such operations will take place either for
suppliers or clients.
Chapter 5: Primary Research
The planner explains the primary research method and thus defines the data collection and
quality research strategies that help the emerging organization in gathering various
information. Descriptive are the strategies chosen by the author for data collection, reasoning
and targets.
Chapter 6: Requirement Validation
The information collected will be evaluated using the methodology described in the above
sections.
6
1.8 Project Plan

1.8.1 Project Plan for First Semester
Table 1: Project Plan for First Semester
PROJECT PLAN SEMESTER I

TASK DURATI START END STA
TASK NAME
ID ON DATE DATE TUS
Meeting with Supervisor (6 4-Hrs 30-
WBS
meetings) Mins
Meeting with Supervisor (1- DON
45 Minutes 26-June-19 26-Jun-19
Meeting) E
Meeting with Supervisor (2- DON
45 Minutes 4-July-19 4-July-19
Meeting) E
Meeting with Supervisor (3- 11-July- DON
45 Minutes 11-July-19
Meeting) 19 E
Meeting with Supervisor (4- 06- 06- DON
45 Minutes
Meeting) August-19 August-19 E
01- 01-
Meeting with Supervisor (5-
45 Minutes September Septembe DON
Meeting)
-19 r-19 E
WBS-C1 INTRODUCTION TO THE STUDY

WBS- 5-Hours(2- DON
Background to the project 3-June-19 4-June-19
C1-1-1 Days) E
WBS- 7-Hours(2- DON
Problem context 5-June-19 6-June-19
C1-1-2 Days) E
WBS- DON
Rationale 5-Hours 7-June-19 7-June-19
C1-1-3 E
WBS- Potential benefits (Tangible 5-Hours(2- 11-June- DON
10-June-19
C1-1-4 and Intangible) Days) 19 E
WBS- 5-Hours(2- 13-June- DON
Target Users 12-June-19
C1-1-5 Days) 19 E
2 Hours(1-
WBS- 14-June- DON
Aim Day 14-June-19
C1-1-6 19 E
)
WBS- 5 Hours(3- 19-June- DON
Objectives 17-June-19
C1-1-7 Days) 19 E
WBS- Deliverables- Functionality of 3-Hours(2- 21-June- DON
20-June-19
C1-1-8 the proposed Days) 19 E
WBS- 6-Hours(3- 26-June- DON
Nature of Challenges 24-June-19
C1-1-9 Days) 19 E
7
WBS- Overview of this 27-June- DON

3-Hours 27-June-19
C1-1-10 Investigation Report 19 E
WBS-C2 LITERATURE REVIEW
WBS- 10-hrs (3- DON
Introduction 28-June-19 2-July-19
C2-2-1 Days) E
WBS- 18-hrs (6- 10-July- DON
Domain Research 3-July-19
C2-2-2 Days) 19 E
WBS- 14-hrs (5- 17-July- DON
Similar System 11-July-19
C2-2-3 Days) 19 E
WBS- 1-hrs(1- 18-July- DON
Summary 18-July-19
C2-2-4 Day) 19 E
WBS-C3 TECHNICAL RESEARCH
Programming Language 19-July-19
C3-3-1 Days) 19 E
WBS- IDE (Interactive 3-hrs(2- 24-July- DON
23-July-19
C3-3-2 Development Environment) Days) 19 E
WBS- Database Management 4-hrs(2- 26-July- DON
25-July-19
C3-3-3 System Days) 19 E
Operating System 29-July-19
C3-3-4 Days) 19 E
WBS- 31-July- DON
Summary 4-hrs 31-July-19
C3-3-5 19 E
WBS-C4 SYSTEM DEVELOPMENT METHOD
WBS- 3-Hours(2- DON
Agile 1-Aug-19 2-Aug-19
C4-4-1 Days) E
WBS- 3-Hours(2- DON
Waterfall 5-Aug-19 6-Aug-19
C4-4-2 Days) E
WBS- 3-Hours(2- DON
Spiral 7-Aug-19 8-Aug-19
C4-4-3 Days) E
WBS- DON
Selection of Methodology 2-Hours 9-Aug-19 9-Aug-19
C4-4-4 E
WBS- 12-Aug- DON
Summary 30-Minutes 12-Aug-19
C4-4-5 19 E
WBS-C5 RESEARCH METHODS
35-
WBS- DON
Questionnaire Hours(15- 13-Aug-19 2-Sep-19
C5-5-1 E
days)
WBS-C6 REQUIREMENT VALIDATION – ANALYSIS
WBS- Analysis of data collected 10-Hours DON
3-Sep-19 5-Sep-19
C6-6-1 through Questionnaire (3-Days) E
WBS- 4-Hours(2- DON
Summary 6-Sep-19 9-Sep-19
C6-6-2 Days) E
8
CONCLUSION AND 5-Hours(2- DON

WBS-C7 10-Sep-19 11-Sep-19
REFLECTION Days) E
PROJECT PLAN SEMESTER II
TASK DURATI START END STA
TASK NAME
ID ON DATE DATE TUS
Meeting with Supervisor (3 2 Hours 30
WBS
Meetings) Minutes
Meeting with Supervisor (1- 17-OCT- 17-OCT- DON
45 Minutes
Meeting) 19 19 E
Meeting with Supervisor (2- 25-NOV- 25-NOV- DON
45 Minutes
Meeting) 19 19 E
Meeting with Supervisor (3- 10-DEC- 10-DEC- DON
1 hour
Meeting) 19 19 E
SYSTEM
WBS-C8
ARCHITECTURE
WBS- 3-Hours(2- DON
Introduction 1-OCT-19 2-OCT-19
C8-8-1 Days) E
WBS- 6-Hours(3- DON
Abstract Architecture 5-OCT-19 7-OCT-19
C8-8-2 Days) E
WBS- 6-Hours(3- 10-OCT- DON
Use Case Diagram 8-OCT-19
C8-8-3 Days) 19 E
WBS- 3-Hours(4- 11- OCT - 14- OCT - DON
Use Case Specification
C8-8-4 Days) 19 19 E
WBS- 3-Hours(5- 14-OCT- 19-OCT- DON
Activity Diagram
C8-8-5 Days) 19 19 E
WBS-C9 PROJECT PLAN
WBS- 10-Hours 5- Nov - DON
Feature 1 3- Nov -19
C9-9-1 (3-Days) 19 E
C9-9-2 (3-Days) 19 E
C9-9-3 (3-Days) 19 E
WBS- 4-Hours(2- 13- Nov - 14- Nov - DON
Details of release plan
C9-9-4 Days) 19 19 E
WBS- 7-Hours(3- 14- Nov - 17- Nov - DON
Test Plan
C10 Days) 2019 19 E
WBS-
IMPLEMENTATION
C11
WBS- 15-Hours(7 17- Nov- 24- Nov - DON
Screenshots
C11-11-1 Days) 19 19 E
WBS- 5-Hours(3 25- Nov - 27- Nov - DON
Sample Codes
C11-11-2 Days) 19 19 E
WBS-
SYSTEM VALIDATION
C12
9
WBS- 6 Hours (3 01- Dec - DON

Unit Testing 28-Nov-19
C12-12-1 Days) 19 E
WBS- 6 Hours (7 02- Dec - 09- Dec - DON
User Acceptance Testing
C12-12-2 Days) 19 19 E
WBS- CONCLUSION AND
C13 REFLETION
WBS- 10 Hours (4 DON
Critical Evaluation 10-Jan-20 13-Jan-20
C13-13-1 Days) E
WBS- 2 Hours (1 DON
Limitations 14-Jan-20 14-Jan-20
C13-13-2 Day) E
WBS- 2 Hours (1 DON
Future Enhancement 15-Jan-20 15-Jan-20
C13-13-3 Day) E
WBS- 06 Hours (3 DON
Conclusion 16-Jan-20 17-Jan-20
C13-13-4 Days) E
1.8.2 Gantt chart
Figure 1: Gantt chart - Project Plan
10
Figure 2: Gantt chart - Project Timeline
11
2 CHAPTER 2: LITERATURE REVIEW

2.1 Introduction
Domain work is carried out on the basis of reviews of historically developed papers,
publications and different systems. The main advantage of domain analysis is that it helps
developers to obtain information regarding structures and experiments that have already been
developed. On the premise that this system adds more functionality or deletes the new
systems following analysis into the previously designed framework.
The main purposes of the domain research on the application is to help the consumer to come
up with ideas on how the application to be built can change or improve. The researchers
should review and think about the same experiments as the above-mentioned method.
Domain research certainly gives a blueprint of how the system development should be done
and considerations that has to be overlook.
2.2 Domain research

2.2.1 Domain Research 1
From the research done from the journal of Michel Owayjan Beirut, Bahaa Sleem, Elio Saad,
Amer Maroun entitled “Parking management system using mobile application”, I came up
with detailed summary mentioned below. They have done research based on Sensors but the
technique they have come up with could be of some use in my project.
Malls comprising a concentration of stores and restaurants have flourished in towns around
the globe in latest years. This concentration causes issues in parking spaces and traffic jams.
This article presents a parking management scheme that uses a mobile application to tackle
parking issues in malls. Two folds are the contribution in this scheme. The hardware
component consisting of custom-made sensor units based on a phototransistor with an
infrared transmitter that is accountable for determining whether a certain parking space is
occupied or free. Using Arduino microcontrollers with Ethernet shields, the devices connect
wirelessly to a main controller. The main controller is a server hosting a database accessible
through the advanced mobile application. The mobile application is created using the Eclipse
IDE and is running on the Android platform. It connects to the database using the format of
JSON (JavaScript Object Notation). Users can use this request when they join the mall. They
can find free parking spaces, check parking charges, find their vehicles, and even pay using
12
the mobile app.
13
Recommendation and Future Enhancement
Based on the research proposed or domain research above, it is seen that the researcher is
looking to develop an mobile application for users to see and find vacant parking spaces and
check parking charges from their own phone but such system has to be deployed looking the
market area. It may cause huge traffic over server as there might me huge number of users as
once, never the less the parking lots has to be well managed and has to give access of the
details to parking spaces in order to make the system a success. As a future enhancement,
system recommending vacant parking lot as a notification to driver would be suitable, so that
he/she do not have to look for vacant parking space on his/her own (Michel Owayjan Beirut,
Bahaa Sleem, Elio Saad, Amer Maroun entitled , 2017).
The research paper from Faheem, S.A. Mahmud, G.M. Khan, M. Rahman and H. Zafar, the
Pakistani researchers have proposed a paper on Intelligent Car Parking System. The aim is to
control mismanagement of available parking, slow paced city development etc. The system of
parking is aimed at a reliable system that can be used to search the unoccupied car park, to
guide the car park, to negotiate the parking charge and to manage the parking facility
properly. Smart Parking Service is part of Intelligent Transport Systems (ITS). The system is
proposed to use Vehicular Communication Systems i.e. VANET guarded by RSUs, GPS
based systems, Wireless Sensors, Vision based techniques etc.
The economic, social and security aspects of society can be supported by that infrastructure.
It also refers to the protection of the environment, power and time. The financial analysis can
allow us to identify the viable solution so that we can boost the parking system without
hurting the economy (Faheem, 2013).
The system also has to have a payment integration so that there will be no direct human
interaction on the system minimizing mistakes, minimizing time and investment on an
employee. As there has been already many policies implemented in order to make the country
cashless (Pakistan Economist, 2019).
14
“Modeling Parking Search to Establishing Urban Parking Policy” is a research paper from the
researchers from department of geography and human environment, Radboud University
Nijmegen, the Netherlands. Itzhak Benenson, Karel Martens, Nadav Levy are the personnels
involved in the research of entitled paper.
Due to the fact that drivers has to search for long time and has to walk long way from the
place of parking to place of work; Illegal parking in street areas and air pollution due to
crowded vehicles, Municipality not being able to provide efficient parking system and
enforcement overhead they have proposed the system.
They have considered few things that could in some way improve parking policies, i.e.
Increasing Street parking fees, maintaining existing systems of parking zones, introducing
restrictions to various driver groups, increasing enforcement levels. They have also proposed
the impacts that could arise due to the considerations made above, impact on the individual
driver's parking actions, impact on commuter, resident and visitors ' mutual parking patterns,
effects on the traffic in and around the regulatory region, balance on and off-street parking,
income generated by policy and compliance costs.
The proposed system is based on geosimulation where each and every real world entity will
be presented in a single model. The system will use high resolution GIS maps, requires
driver's comportment and overall parking conditions to be tested, fits with almost limitless
vehicles etc.
The system is likely to go in any direction either failure or success as there will be lots of
parameters that has to be considered. But as the problem of parking is increasing every day
every hour, the system is worth giving a try in country like Netherland (Expatica, 2019).
Parking is a big issue but has impact on city due to small and individual actions performed
collaboratively. The researchers has to consider the small ways of regulating the parking
issue and can be planned GIS based system later. This could enhance the parking efficiency
as there will be less chance of growth of issue due to proper monitoring of small issues.
15
2.3 Similar System/s (with similar features)

2.3.1 RTVTR
By visiting and studying the project named “Real Time Vehicle Tracking and Recognition
System (RTVTR)” of Inspiring Lab; One of the leading Artificial Intelligence Company of
Nepal, I came to know and learn about the concept elaborated below: RTVTR is an image
processing system that recognizes vehicles and license plates without direct human
interference using ANPR. It can be used in many applications such as traffic control and
surveillance, speed control, identifying stolen cars, in toll booths/gates and parking lots and a
variety of potential security applications. Many techniques have been developed to detect
vehicles and license plates but only work under standardized rules that determine plate sizes
and/or shapes. In this regard, RTVTR proves to be robust and dynamic by recognizing all
types of number plates, standard or random plates.
The Features of RTVTR System currently includes;
 Classification of different vehicles up to 15 categories (Car, Bus, Bike etc.).

 Count specific types of vehicles over a region of interest.
 Identify and distinguish different license plate types.
 Nepali as well as Embossed character recognition.
 Matching detected plates to their corresponding vehicles.
The system can firmly be applied in private as well as public sectors. Parking Lots, Road
Tax/Toll, Hotel, Housing, or Apartment, Commercial Buildings. Government sectors consists
of Checkpoints, Traffic Surveillance, Time card management etc.
The system has been developed considering different current and future issues that can come
into play. The concept can be used in my project as a future enhancement to minimize or
reduce direct human interference during vehicle entry, exit and spot allocation.
2.3.2 Park KTM
KMC has coordinate with Wheels Truly Yours Private Limited and has introduced a Smart
Parking System, an android based application “Park KTM”, in five different place of
16
Kathmandu (in front of Bishal bazar, Dharma Path, Behind Rameshwaram Sweet Shop, Pako,
and in front of RB Complex).
With the help of the app, one can easily monitor the parking time of their vehicle along with
the space available for parking using the app. The procedure for doing so is:
 Select Vehicle Type

 Select desired location (Only Five Available Currently)
 Tap the book Button.
 Call Toll Free Number to book you parking spot
 Park at reserved spot (City Motorbike, 2019).
The person has to reach in the parking place within the 15 minutes of booking confirmation
else the parking spot will be released again. The system uses GPS location, Map, Sensors
(Infra-Red Sensor to detect empty space, LED Screen). The spaces are mapped in certain
coordination created by KMC.
The date, place, vehicle type, in time and customer id is noted at the time of vehicle entry and
a QR code is generated with the information. At the time of exit, keeping exit time and
calculating the total time, bill is generated and the statement is synced to the application of
parking system and customer (Aditya Thakuri, 2019).
IT is a good start in context of parking but looking at the pricing and policy that Park KTM has
Made things are seen to have more complicated. It is seen that the spot were too wide and the
number of bikes that could have been parked decreased. The price of 25 Rupees an hour for
two wheeler, 60 for four and 200 for more than four is too high for Nepalese people. Never
the less, the traffic is so high in Kathmandu, even more during pick/office hour the
reservation duration of 15 minute would exceed in 8 out of 10 case. So these things has to be
considered for effective implementation of smart parking (therisingnepal, 2019).
Lastly, No customer is entertained to get driven off from one app to other for acquiring
service. People has to switch to Phone app from Park KTM app for placing order. So, the
facility has to be either merged in the application itself or the booking procedure has to be
changed to something easy and quick. (KTM, 2019)
17
2.4 Summary
The above chapter assesses work already begun on a specific topic. This includes knowledge
of the different technical fields and design as well as other subjects based on previous study.
The literature review allows developers to reveal the ability to identify and establish
consistent data.
18
3 CHAPTER 3: TECHNICAL RESEARCH

3.1 Programming language chosen
Everything in this universe has bind in some boundaries. Programming language is a rule or
notation for writing programs. Programming language has been categorized into two low
level language and high level language. High level language are intended to be machine
independent as they can be used in any computer. The suitable programming language for
proposed system is explained below.
Table 2: Programming Language Evaluation
Functionality ASP.NET(Chosen) PHP JSP
Programming language VB, C#, C++, Java, C, C++ Primarily Java

support JavaScript, Jscript, Script
etc.
Supports Databases listed: Yes Yes Yes

MySQL, PostGreSQL,
Oracle, Sybase, DB2.
Compatible for Operating Yes Yes Yes

Systems like Microsoft
Windows, Linux, macOS
License Apache License 2.0 PHP License JSR 245
Cost Low Moderate Moderate
Tools and Features Lot Lot Few
Customizable No Yes No
Page Speed Fairly Slow at start Fast Fast
Error handling Yes No Yes
19
3.2 IDE (Interactive Development Environment) chosen
ASP.Net is a server side scripting language, famous for developing interactive and dynamic
web pages. It is necessary to use an efficient IDE which provides all necessary tools and
elements which makes it easier for developing proper web applications in sole environment.
Some of the IDEs for ASP.Net are Webbo, WebMatrix, Visual Studio, Quick Sharp etc.
Visual studio is an official IDE or tool used for developing web applications using ASP.Net.
It offers firm editor tool for creative user interface design. Debugging option helps developer
test the program time and again as per the need. Features like drag and drop, smart indenting
make it easy for developers. So I have decided to choose Visual Studio as IDE
(VERACODE, 2019).
3.3 Database Management System chosen
The study of database is alike battleground of ideas. With the increasing desire of more
dynamic web sites, the developers has been facing more and more issues in database. It is
always daunting choice considering many available DBMSes, among open and closed source,
and vast spectrum of differences between them.
The database hierarchy model used to store, manage and query databases is the most
fundamental choice to make in DBMS hierarchy. Probable the most important general feature
to consider in DBMS is security. Today security has grown far beyond keeping out malicious
users. Ability to integrate into incremental backup regimens, multi user support etc. has to be
considered before choosing a DBMS (IBM, 2010). For a web application like this relational
database management system is important inside it Microsoft SQL Server seems to be the
valid choice considering immense features.
Table 3 : Choosing Database - Evaluation
Functionality MS SQL Server Oracle

(Chosen)
Procedure/Language Used Transact Structured Procedural

Query language (T- Language
SQL) (PL/SQL).
20
Generally used to store simple data Yes No
21
In Execution of Query changes made are Yes No

committed in database
Expensive No Yes
Database Objects Organized By Database Names By Schemas
Used for small projects Yes No
I have chosen MS SQL Server among all the other RDBMSes. MySQL has sought to have
vulnerable to SQL injection so did not fulfill the criteria. Between MS SQL server and
Oracle, MS SQL being the free, and with the other features listed above which are exactly
suitable for project like mine, I have considered MS SQL Server as my Database (seguetech,
2014).
3.4 Operating System chosen
The foundational software on system server is the operating system. Without operation
system, the server is just collection of electronics that cannot understand how to communicate
with rest of world. The first and foremost decisions one has to make is whether he/she wants
something that runs on MacOS, Microsoft Windows, Chrome OS or Linux (Lifewire, 2019).
MacOS is one of the famous operation system put out by Apple. It is considered a bit costly
but is highly preferred in industry of development and design. Microsoft Windows being the
one most common and comparatively cheaper operating system in current generation has
been favorite to many technical or non-technical users. Linux is one of the powerful, free and
open source operating system.
When considering operating systems, it is necessary to keep in mind that it has capacity to
run on different cross platforms or not. Decision process involved in choosing an operating
system for everyday computing and for web hosting space is different. Windows and Linux
stand out for the system like e-Parking. As the application will be built on Microsoft’s .NET,
it is likely to be well-served with Linux host or the Windows host.
Due to the fact that it is going to be Windows based web application, I chose to go with
Windows operating system in order to avoid Linux hosting complications (whoishostingthis,
2019).
22
3.5 Summary
The similar systems were taken on the technical part and work was carried out between them.
Technical work included the vocabulary of programming used and, the software used. The
characteristics of the program are also discussed in accordance with the technical term.
ASP.NET was selected for the operating system programming language, the MS SQL Server,
the database and Windows.
23
4 CHAPTER 4: SYSTEM DEVELOPMENT METHODOLOGY

4.1 Introduction
A system development approach encompasses the mechanism used to organize, prepare and
control the procedure for the creation of the information system. There are a broad range of
frameworks with their pros and cons appropriate for particular types of activities based on
different considerations of organization, team and project. The technique is chosen according
to the complexity of the development system. There are different system development
methodologies including cascade, scrum, agile, rapid development, funnel, etc. program
development. The three system development methodologies that can be considered for e-
Parking development are described below:
Table 4: System Development Methodology
Functionality Agile Spiral Waterfall (Chosen)
Documentation Oriented No No Yes
Used for Complex Projects Yes Yes No

where changes are often
Rapid Development Yes Yes Yes/ Maybe
Complete Working Procedure is Not Necessarily Not Necessarily Yes

defined at the beginning of
project
Cost High High Moderate/ Cheap
Task Done or to be done Not Necessarily Not Necessarily Yes

properly documented so easy to
hand over
24
4.2 Agile
Agile architecture offers fast and monotonous path for software to be built by splitting the
complex project into smaller parts, constantly evaluating and modifying plans. Projects of
limited development time, recurring customer specifications, and actualizations make the
main justification to choose agile approach in the application development process. There is
very little scope to change the traditional methods, but the agile method is flexible. Agile
development offers stable and less error applications for users. Scrum, lean growth, Kanban,
Extreme Programming, fast development of code, crystal and much more fall under agile
philosophy. (SAP Application, 2011).
Figure 3: Agile Methodology
25
4.3 Waterfall
Waterfall is considered the lead in the lifecycle of system development. The software
development cycle is split in this SDM model into various aspects and each dimension is
special. The early model used in the development of the program was the waterfall technique.
The sub phases from the key process are known as the feedback in this model for the later
phases. The Waterfall concept is not overridden, because a step must be finished before
another process is completed. The creation of the next step starts with the completion of the
key process, each element of the waterfall model is described perfectly well. It's because the
phases go from higher to lower level that name this model as a waterfall model.
(tutorialspoint, 2019).
Figure 4: Iterative Waterfall Methodology
26
4.4 Spiral
Often recognized as an evolutionary process, the spiral pattern. The spiral paradigm is similar
to the phase of iterative modeling when multiple iterations occur. The spiral paradigm of
different fields differs from the iterative model. The central motto of the spiral approach is
risk reduction. A specific number of iterations awaits and prepares the spiral model because
the spiral model is based on creation of evolutionary tools. The spiral model often allows
further variations, equivalent to the iterative model, following the original expected iterations.
The spiral concept requires organizing and carrying out various tasks (Margaret Rouse,
2019).
Figure 5: Spiral Methodology
27
4.5 Chosen Methodology
Software development methodology refers to the framework or technique that is used to plan,
structure, and control and develop a system. Among the different development methodologies
above, I have chosen waterfall as it suits best for my project. There are other methodologies
that can be considered for the system development but with the features my project holding,
waterfall would be the first and foremost system development methodology. In waterfall
model breaks down the project steps in linear sequential phases. Requirement analysis,
Design, Implementation, Testing and Verification and Maintenance are the phases of
waterfall model (Gianpaul Rachiele, 2018). No phase can be skipped as it strictly ensures the
sequence. Alongside that, it is the ideal methodology for supporting new or less experienced
project managers. The project progress can be easily mapped resulting in no confusion in
action to be performed in current phase as well as in next phase. Waterfall methodology
highly promotes the proper documentation. Someone new to the project can easily understand
the works done by going through the documents (Tatvasoft, 2017).
4.6 Summary
This chapter explores the approach of system development used to create the proposed
project, as well as comparing several different methodologies from which waterfall was
picked as appropriate one.
28
5 CHAPTER 5: RESEARCH METHODS

5.1 Introduction
The problem of science, policy, expenditure and time are all important aspects of all projects.
This is before we analyze the necessary facts and discuss the best approaches for each
discipline
.The researchers must make compromises and generalizations in every experimental design
so that they minimize them while remaining realistic. Here are the list of few research
methods explained in brief (Martyn Shuttleworth, Jun 19, 2008).
5.1.1 Data Gathering Analysis
Usually, data are collected by qualitative and quantitative methods. Qualitative approaches
are aimed at addressing a program's how and why and tend to use unstructured data collection
methods to fully explore the topic (John Dillard, 2018). On the other side, the quantitative
methodology approaches the software "what." It utilizes a systemically structured strategy,
using tools including surveys and questions such as “Used the software before?” and “What
kind of software have you been using?” (National Institute of Health, 2019)
5.1.2 Project Deliverables
The results of CIMS quantitative analysis are systematic so that associations can be made
easily and the impact magnitude can generally be calculated, since they are cheaper to
implement. Furthermore, longitudinal data collection methods for peer-based programs are
often challenging for organizations to adopt because the lack of resources available for robust
surveys and often encountered limited participation and failure of follow-up level are
commonly experienced causes.
5.1.3 Focus on Methods
Conference groups are good for discussing a subject more, provide an explanation of why the
community may act or behave in a similar way and help to evaluate the cause behind attitudes
and beliefs. I have done a small sampling of target groups to stimulate discussion by using
questionnaires and obtaining greater insight.
Strategies and discussions are useful as they are:
29
 Important to analyze organizational principles.

 Can be used to look at how people perceive and why.
 Dynamic issue discovery.
 No students must be told to be included in the study. •
5.1.4 Data Collection
Significant sets of documents are often called "thick explanations" which can be used for
further study of a subject. This method provides a detailed overview of the "survey
participants" and presents a consistent pattern of culture to be collected in surveys. These
records, through survey and questionnaires, are informal feedback and reflection.
Creative approaches have been developed to enable the learners to represent perceptions
across different art forms that often show perspectives that are not conveyed in language.
This can be attributed to a prior negative experience or lack of confidence in their own skills.
The approach for collecting information is a difficulty in producing a good final product or
learning outcome in information technology.
Triangulation is used as a method of valuing data collection to address the validity of the
data. Triangulation methods use multiple forms of data collection to evaluate the system to be
developed, such as focus groups, observation and in-depth interviews. This will reduce the
cost of the evaluation substantially (Research Methodology, 2019).
5.2 Design
5.2.1 Observation
Observation is used as a technique also called as survey questionnaires using observation

templates. Observation is an information collection technique in which scientists observe a
particular field of studies. Sometimes it is called an unobtrusive method. It provides a chance
to learn things that people may be unwilling to discuss in an interview (Merriam Webster,
2019).
I designed a questionnaire set for the interview session to be discussed in greater depth.
Finally, each question will be justified on its purpose and how the outcome will contribute to
the results of the project.
30
5.2.2 Questionnaire, Survey, Interviews, Focus Groups
The Questionnaire, Surveys are Attached with the documents at the end.
5.2.3 Objective of the Question
The objective of each question in Questionnaire, and how the result would help for the
project deliverables is elaborated as:
Do you own a vehicle?
The objective is to show that the questionnaire is distributed to potential users from different
sectors. If the uses has experienced the parking problems as he/she owns a vehicle. The
research mostly focuses on the people with vehicle.
What type of vehicle do you own?
To get a broad view of what type of vehicle are more likely to be used in parking and which
vehicle type to focus more during the project development.
How easy is it to find the parking space?
To get idea about how difficult has it been for people to get a vacant parking space in their
daily life.
How much average time do you spend looking for a parking spot?
The question is placed in the questionnaire in order to find the average time that most of the
vehicle owners spend in a parking lot finding a parking space. This data would provide the
time that we can reduce by developing new system.
Have you ever been late to class/office because you could not find a parking space?
The question’s objective is to find if majority of people has suffered the problem of being late
from the current parking system.
What would you recommend between following options?
To get idea about what feature people want the new system to have to reduce the problem of
parking.
31
How would rate the current parking system?
The objective of the question above is to find, what the idea of people about current systems
is and how badly they need the new system?
Do you get any assurance of vehicle protection during parking? / Do you provide any
assurance of vehicle protection during parking?
There are two questions in Customer and Staff end in order to get same information out of
them. The first question is asked to people who own vehicle whereas the second question is
asked to staff/owner of parking lot. The question tends to know if people are benefited in
security context by parking vehicle in the parking lots.
How is Parking Time Tracked?
To get idea about the current parking system procedure in tracking time. And to get idea how
the new system can be developed in order to track the time and generate bill.
Do they record personal information?
The question is to know, how serious parking systems are in keeping people’s personal detail
and security.
Should the information be recorded for security propose (if any damage caused) and for
recording transaction details?
The question tends to get results about how people want to be considered by parking staffs in
maintaining security concerns and in recording transaction details.
Do you thing using vehicle identification number for allocating parking space will ease
the parking?
The question has sole objective of knowing the view of people or staffs about using the
vehicle identification number in order to by allocate parking space would if reduce the
parking issues.
What kind of system do you recommend for better parking? / What type of system do
you recommend in order to make most out of parking spaces in order to generate more
revenue out of it?
32
Innovative ideas are always accepted in the society. This recommendation is to have the
respondents to think, to share and even to create. It also helps to get motivated and inspired
by the brilliant ideas shared with different perspectives and diverse background.
How easy is to manipulate parking spaces?
It is always good to know the problem of parking staffs in the parking space manipulation.
The question looks to know what the staffs working in a parking lot think about the system
that they follow for parking space management.
How much time do you spend generating daily transaction report?
It is always necessary for every person to generate daily transaction at the end of day. Most of
the time, it is a very challenging task to perform. The question aims to know how much time
the staffs are giving at the end of day to finalize the report. This also gives how good the idea
of generating daily transaction/ revenue report would help staffs.
How is the information of customer recorded?
In current context, generating customer information has been vital for mainly security
concern. The question’s objective is to know if the staffs record the personal information or
not.
How is daily transaction recorded?
To get broad knowledge about the current trend on recording daily transaction detail.
How is the daily vehicle flow recorded?
To get broad knowledge about the current trend on recording daily vehicle flow.
What if staffs don’t record parking and transaction details, how would you take the loss?
By not recording the daily parking detail and transaction details some or majority of staffs
have sought to make fluctuation in revenue. The question has sole objective of knowing the
view of staffs and owners in this issue.
How strongly do you recommend a new parking system which will let you know about
how many parking spots are available at each lot?
To know the need of staffs of new parking system that would let them to see how many
33
parking spots are available at each lot.
34
5.3 Summary
The information collection technique was chosen to go to the questionnaire information

collection technique because it is the most appropriate way to collect information from
customers directly and to comprehend their requirements and suggestions.
35
6 CHAPTER 6: REQUIREMENTS VALIDATION

6.1 Analysis of Data
Data analysis done for e-Parking describes the needs and goals of the client in the context of
information finding and reporting through the scheme. This analysis report shows the
information in a way that is understandable to meet the study goal. In the event of translating
the study question set issues were well structured and presented to the surveyors.
6.1.1 Analysis of data collected through Questionnaire
a. Gender
Result:
Figure 6: Gender involved on survey:
Evaluation: The question aims to know what percentage of survey group belongs to what
gender. From the result we can conclude that the majority of people enrolled in the survey
were male i.e. 90.3%.
b. Occupation
Result:
36
Figure 7: Bar diagram showing Occupation of Percipients.
Evaluation: 48% of the participants are seen to be students followed by different occupations
like developer, freelancer, pharmacist, business man, banker etc.
c. Do you own a vehicle?
Result:
Figure 8: Pei Chart - Participants with Vehicle - Statistics
Evaluation: The survey focuses more with the group who own a vehicle. The question aims to
make sure most or majority of people enrolled in survey own a vehicle. According to the
result above 93.5% people participate in the survey have vehicle.
37
d. What type of vehicle do you own?
Result:
Figure 9: Vehicle Type – Pie-Chart
Evaluation: The majority of the participants are 2 wheeler users with 80.6%.
e. How easy is it to find the parking space?
Result:
Figure 10: Ease to find parking space
Evaluation: According to result only a person out of 31 responded the parking space is easy
to find. Whereas, 45.2% find it extremely hard and 35.5% find it hard. We can conclude that
the new efficient system is required.
f. How much average time do you spend looking for a parking spot?
Result:
38
Figure 11: Average time to find parking spot
Evaluation: 41.9% of people are able to find the parking spot within 5 minutes whereas others
find parking spot at about 10 or more time.
g. Have you ever been late to class/office because you could not find a parking space?
Result:
Figure 12: Statistics showing people being late due to parking issue
Evaluate: Majority of person are late to school or office because they could not find a parking
space, 80% of people are late on average to their destination.
h. What would you recommend between following options?
Result:
39
Figure 13: Participants’ Recommendation on parking system feature.
Evaluation: 61.3% prefer vacant spot name form the parking staff rather than searching
vacant space on their own. We can conclude from this that the spot has to be given to
consumer at the time of entry.
i. How would rate the current parking system?
Result:
Figure 14: Current Parking System Rating
Evaluation: Among the 31 respondents, 38.7% of them rate it as ‘Extremely Poor’, 45.2% of
participants rated it as ‘Poor’ and rest of them rated ‘Average’. This certainly means there is
need of new system that resolves the parking problems.
j. Do you get any assurance of vehicle protection during parking? / Do you provide
any assurance of vehicle protection during parking?
Result of Consumers:
40
Result of Staffs: (11 Responses)
 Yes : 0
 No : 11
Evaluation: 83.9% of the people (consumers) found they didn’t get assurance of vehicle
protection during parking and 100% of the parking staff participants said that didn’t give
assurance of vehicle protection.
k. How is Parking Time Tracked?
Result of Consumers:
Time
No idea!
Written records
The parking staff tracks the time based on the time noted on the parking ticket.
By parking staff
Record of Entry
Record slip with vehicle number
They give me slip mentioning the time
Difference between arrival time and departure time
Bills
Hourly Basis
Using bike number
From the slip
Parking time is kept in register book
41
Morning office time

Don’t know
Check-in and Check-out Time

Unknown
Onrecording
By some spot
Randomly, it literally depends on mood of the collector.

Hourly
Mostly
They by a slip
usually thatus
provide is provided or awith
small paper paper record
time written on it and charge us accordingly
10 To 4
Cheat
Goodevaluate the in and out time.

They
On few places
Manually they have
with paper sheetticket and parking now
Too Hard
Result of Staffs:
Give
We parking
provide slip
slip at the
with the time
entryof vehicle
time notedentry.
on it.
Wegive
We don’t track
the slip parking time written
with in-time rather take
on itone
andtime charge.
charge hourly.
On the1-60
Hourly, basisminutes
of vehicle parkedIfper
(1 Hour), thehour.
consumer parks for 80 minutes, 2 hour’s charge is liable.
Hourly,onBased
Based on the
the cheat weentry timeduring
provide notedthe
on vehicle
the entry
in book.
time.
Vehicle and Entry

Evaluation: Fromtime
the islistings
recorded in logbook.
above it is found that current parking systems has been using
slip or cheat with the entry time written on it. In case of, lost slip, the total time from the
parking opening hour to current time is calculated and the hourly based charge is laid.
42
l. Do they record personal information?
Result:
Figure 15: Personal Information Recording Information
Evaluation: It is found form the above pie-chart that, 58.1% of the participants did not find
their personal information being recorded whereas 32.3% found that their details were
recorded occasionally. It can be concluded that in most of the cases the personal information
is not given priority.
m. Should the information be recorded for security propose (if any damage caused)
and for recording transaction details?
Result:
Figure 16: Result for recording personal information
43
Evaluation: 61.3% of participants claimed that the information must be recorded for the
security purpose or for recording transaction details. Whereas 32.3% voted on ‘Not
Necessarily’ category. It’s needs to be considered, the majority of percentage of participants
and should make a system that is capable of recording personal information.
n. Do you thing using vehicle identification number for allocating parking space
will ease the parking?
Result:
Figure 17: Statistics on Using VIN for Space Allocation
o. What kind of system do you recommend for better parking? / What type of
system do you recommend in order to make most out of parking spaces in order
to generate more revenue out of it?
Aim of the Question:
Result:
E-Parking
Low space hydraulic parking.
An online system.
Automated / online parking system, where I can book the parking spot before I actually arrive at the
parking station.
DigitalSystem
Digital
Foe managed
Well effective parking, separate
with proper block of parking for 2 wheeler and 4 wheeler with numbering system.
security
Along with online parking system should be more effective for systematic parking.
44
Parking system in which we can book our space from the office or home through handheld devices
and better management of vehicles in the parking lot may be a solution.
E-parking
Automated
Online System
booking
Electronic
Parking recording
system shouldsystem
be justifiable to every vehicle holder and they must convey how must duration
they will park and incoming time and outgoing of every vehicle should be recorded..
E parking
Dont know
Recording
Smart maximum
parking system information of vehicles, allocating pre time duration for each vehicles as per
their need
Something
One like e-parking that have the functionality like vaccant space with notifications, location
side parking
tracking and availability and so on
IfInwe
mypay
opinion,
moneyowing a vehicle
for parking, is should
they the main cause
make of there
sure this alarming situation.
occurs no Its better
any damage you
to the travel via
vehicle
public transportation.
I Your
think idea was really
reserving good. Do
park space well online will be best practice as it will reduce the time consumption
through
while searching for vacant space.
Nice one
Online space finding
Hybrid underground parking

E-parking
Pre booking,
Every vehicle
ground floor insurance
should be forand availability
parking in busyinformation
areas
Overall goodMany different ideas has been proposed on this segment. Taking the ideas into
Evaluation:
consideration an ideal idea has to be created and implemented for the creation of new system.
p. How easy is to manipulate parking spaces?
45
Result:
 Easy : 0
 Neutral : 3
 Hard : 6
 Extremely Hard : 4
Evaluation: Out of 11 parking staffs or employees 6 of them found the management of

parking space hard and 4 found it extremely hard. It can be concluded that the new system
with easy parking space management is required.
q. How much time do you spend generating daily transaction report?
Result:
 About 30 Minutes : 2
 About 1 Hour : 6
 More Than 1 Hour : 3
Evaluation: In 9 out of 11 cases it was recorded that the generation of daily transaction report
took 1 hour or more time. So new system needs to be developed considering the transaction
report generation procedure.
r. How is the information of customer recorded?
Result:
 Never recorded the personal Information : 7

 Registered in daily log Book : 3
Evaluation: Majority of parking lots don’t record the personal information maybe because it
is time consuming and the data listed may not come to any use. But the security if big
concern so the information recording should be put into play.
s. How is daily transaction recorded?
Result:
 Logbook : 4
 ExcelSheet : 4
46
 Not Recorded : 3
 Other : 0
Evaluation: Auto recording of transaction needs to be implemented as the majority of the

current transactions are recorded in logbook (a traditional approach) and Excel sheet (Use of
different application/ not a parking app).
t. How is the daily vehicle flow recorded?
Result:
 Logbook : 1
 Not Recorded : 9
 Other: 1 – We check the excel sheet of vehicle entry and count to determine average
flow.
Evaluation: It is found that the vehicle flow in not recorded in 9 out of 11 parking lots. It is
good to record the vehicle flow as it will be easy to parking management committee to
allocate more human resource at peak hour.
u. What if staffs don’t record parking and transaction details, how would you take
the loss?
Result:
 Not necessarily the concern as there are other aspects to consider right now.
 Believing on our staff is all that we should do.
 The case does not apply and it’s not good to believe on our own staff.
 Not sure
 That does not happen as all the transaction has to be recorded in the computer.
 Such things are common, deduction of 50-100 rupees from daily parking revenue
won’t really affect the parking revenue. We get bored all day, at least tea and
cigarettes from that money helps.
 Good system is required in order to minimize these kinds of loss.
 We have to believe our staffs for now but a good system is required to reduce such
incidents.
 Non-ethical, we can only hope they put every record on the log sheet and pay all the
bills.
47
Evaluation: Few of the parking staffs do not take this issue as a problem as according to
them, won’t make huge impact on the revenue of the parking. Some of them consider
believing on the staffs as such issues does not happen. Whereas rest of the participants
recommend a system to reduce this issue.
v. How strongly do you recommend a new parking system which will let you know
about how many parking spots are available at each lot?
Result:
 Strongly : 7
 Not Sure : 3
 Not Necessarily : 1
Evaluation: 7 out of 11 strongly feel the need of new parking system from which the vacant
parking spots can be monitored.
6.2 Summary
From the analysis done above it is found that the new system that can calculate and generate
bill from entered in and out time needs to be developed. Also, the system should be able to
generate transaction report, and add the personal information of consumers to system in order
to maintain security concerns. Few things that can be taken as future enhancement were also
acquired to make the system efficient in long run. Use of IOT for tracking parking space,
fetch VIN at entry and exit time which would reduce the direct enrollment of staff in
monitoring system, spot booking facility to consumer even before reaching the parking space
are the functionalities that can be added in the system which I consider to be future
enhancement. This reduces the direct human interaction that reduces mistakes and burden
from staffs as well. Nevertheless use of payment gateway systems for paying bills is another
aspect that can be considered as the future enhancement.
48
7 CHAPTER 7: SYSTEM ARCHITECTURE

7.1 Introduction
‘E-Parking’ is a web based application for parking management. It is simply an admin portal
from which the admin can regulate the parking actions. The system is sought to be more
profitable where the population of vehicles will be high and where surged parking approach
is implemented. ASP.NET platform has been chosen for the development of the system. The
data entered in the system by user will be stored in database; SQLServer as the database
server. As the system is web-based application and will be accessible by authorized users
only.
The authorized user can login to the system with his/her username and password. The details
will undergo verification process in system’s database and authenticated with rightful access.
The authorized user can then add another user to the system and the new user will have same
access rights as the old one i.e. full access. From the system, the user, say admin, can firstly
add the parking lot details to the system as per the parking lot he owns or works for. Once the
parking lot is added, he can then add vehicle type that the parking lot facilitates for parking.
He can further update or delete the vehicle type as per his requirement.
Similarly, Price for each vehicle type can be added to the system, with the help of vehicle
type, price, and total time parked, the invoice will be generated. Booking is another feature
that the system possesses, as per the request of client (person who parks his/her vehicle),
admin can book a spot for the client which is liable to user unless rest of all spots in the
parking lot are occupied.
The most important section of ‘E-Parking’ is Direct Vehicle Entry, The admin will record
vehicle identification number to the system at the time of entry and will allocate parking spot,
where the client is supposed to park his vehicle. At the time of vehicle exit, again, the vehicle
identification number and the vehicle exit action is performed and parking spot status is
changed back to vacant. At the same time, parking invoice is generated which then is given to
client to pay the bill.
All the details that were mentioned above are viewable and can be recorded for any sort of
requirements.
49
Browser
URL Routing
Tables HTML
View / Front
End
Forms CSS
Controller JS
Model
MsSQL
Database
Figure 18: System Architecture
The Admin is able to surf the application with the help of browser, Microsoft Edge, Chrome,
Firefox Mozilla, and Brave; any of these is recommended for better performance. The
browser then routes the URL of system and front end/ View is accessed. View is controlled
by Controllers. Controllers goes through model to the database from which the data are
fetched.
50
7.2 Abstract Architecture

7.2.1 System Design
7.2.1.1 Use-Case Diagram
For a program which is in developing process, use case diagram, provides a primary system
requirement form. It can be represented in visual or textual format depending on the nature of
system, facilitating the developer design the system from user’s vision. It gives a general
relationship between different components involved (Visual Paragism, 2020). The diagram
demonstrates the detailed structure of e-Parking.
Validate Data
<<include>>
Register
<<extend>>
Dispaly Registration Error
Login
<<include>>
Admin
Verify Password
<<extend>>
Add Parking Lot

Dispaly Login Error
Add/Update/Delete Vehicle Type
Add /Update/Delete Price
Vehicel Entry
<<include>>
Vehicle Entry/ Exit

<<include>>
Allocate Parking Spot
<<include>>
Book Parking Spot Vehicle Exit
Print Invoice
Figure 19: Use Case Diagram
51
7.2.1.2 Use Case Specification

Table 5: Use Case Specification for Login
Use Case Login/Sign In
Details The purpose of the use case is to enable actor to login to system
Actors Admin
Pre- Condition Valid Username and Password
Main Flow 1. Enter username and password

2. Click Login Button
3. Actor is logged into system and redirected to dashboard.
Alternative Flow If the entered details are incorrect the error message will be
displayed.
Post Condition Login Successful
Table 6: Use Case Specification for Register
Use Case Add User/ Register
Details The purpose of the use case is to enable actor to add another actor to system
Actors Admin
Pre- Valid and Unique Email, Username, Password, Confirm Password, Phone
Condition Number
Main Flow 1. Enter Email, Username, Password, Confirm Password, and Phone
Number
2. Click Register/ Add User Button.
3. New user is added; in case of register, actor is successfully added and
redirected to dashboard.
Alternative If the details are empty or possesses invalid datatypes, unsuccessful error is
Flow displayed
52
Post Registration / Add User Successful.

Condition
Table 7: Use Case Specification for Add Parking Lot
Use Case Add Parking Lot
Details The purpose of the use case is to enable actor to add parking lot to
system
Actors Admin
Pre- Condition Parking Lot Name, Shot Name, Vehicle Type, Parking Lot Capacity,
Price
Main Flow 1. Enter Parking Lot Name, Short Name, Vehicle Type, Parking Lot
Capacity and Price.
2. Click + Button to add new vehicle type with capacity and price.
3. Click Submit Button.
Alternative Flow Error Showing Value Cannot Be Null.
Post Condition Parking Lot Successfully Added.
Table 8: Use Case Specification for New Booking
Use Case New Booking
Details The purpose of the use case is to enable actor to book new client to
system.
Actors Admin
Pre- Condition Date, Time, Vehicle Type, Vehicle No, Full Name and Phone Number
Main Flow 1. Enter all the values specified above.

2. Click Book Now button.
Alternative Show error, No details are entered.

Flow
53
Post Condition Booked Successfully.
Table 9: Use Case Specification for Update Booking
Use Case Update Booking
Details The purpose of the use case is to enable actor to update

booking.
Actors Admin
Pre- Condition
Main Flow 1. Change Details entered previously if any.

2. Change booking status as required
3. Click Update Button
Alternative Flow
Post Condition Booking Details Successfully Updated.
Table 10: Use Case Specification for Vehicle Entry
Use Case Vehicle Entry
Details The purpose of the use case is to add ‘Direct Entry’ vehicle to
system.
Actors Admin
Pre- Condition Vehicle Identification Number, Vehicle Type
Main Flow 1. Enter Vehicle Identification Number i.e. vehicle Number

2. Enter Vehicle Type ID
Alternative Flow
Post Condition The vehicle is added to the system
54
Table 11: Use Case Specification for Vehicle Exit
Use Case Vehicle Exit
Details The purpose of the use case is to exit parked vehicle and generate
invoice.
Actors Admin
Pre- Condition Vehicle Identification Number i.e. Vehicle Number
Main Flow 1. Add Vehicle Number to exit.

2. Click Send Button
Alternative Flow
Post Condition The vehicle has exited from parking, invoice is generated in system.
Table 12: Use Case Specification for Spot Allocation and Status
Use Case Vehicle Exit
Details The purpose of the use case is to manipulate parking spot.
Actors Admin
Pre- Condition Spot Code, Spot Status
Main Flow 1. Enter Spot Code and Spot Status as “OCCUPIED” at the time of
vehicle entry.
2. Enter Spot Code and Spot Status as “VACANT” at the time of vehicle
exit.
Alt. Flow
Post Condition The spot is allocated & status is changed at the time of vehicle entry &
exit.
55
7.2.1.3 Activity Diagram – Register

The purpose of designing the activity diagram is to understand the behavior of system as it
describes what the application has to have which is being modeled. It simplifies the
understandability of system as it describes algorithm’s logic, clarifies complicated use cases,
and illustrates workflow between system and user and many more (Lucidchart, 2020). Below
shows the activity diagram of register. We can understand the detailed registration process
from the diagram below.
Register
Enter Email
Enter User Name
Enter Password
Confirm Password
Enter Phone
NUmber
Login To System
Figure 20: Activity Diagram - Register
56
7.2.1.4 Activity Diagram – Login
Login
Enter User Name
Invalid Details
Enter Password
Verify Login Details
Login To System
Figure 21: Activity Diagram – Login
57
7.2.1.5 Activity Diagram - Vehicle Type
Vehicle Type
Add Vehicle Update Delete Vehicle

View List
Type Vehicle Type Type
Enter Vehicle
Type
Description
Enter Short
Cancel
Name
Delete
Submit
Figure 22: 7.2.1.5 Activity Diagram - - Vehicle Type
58
7.2.1.6 Activity Diagram - Parking Lot
Parking Lot
Add Parking View Parking

Lot Lot List
Enter Parking
Lot Name
Enter Shot
Name
Add Parking
Space
Select Vehicle
Type
Parking Lot Created
Enter Capacity
Enter Price
Submit
Figure 23: Activity Diagram - Parking Lot
59
7.2.1.7 Activity Diagram - Price
Price
View Price List Add Price Update Price Delete Price
Cancel
Select Vehicle
Type
Enter Price Per Confirm Delete

Hour
Cancel
Delete
Submit
Figure 24: Activity Diagram - Price
60
7.2.1.8 Activity Diagram - Booking
Booking
Update
Add New Delete
View List Booking
Booking Booking
Details
Enter Date
Enter Time
Delete
Select Vehicle
Type
Enter Vehicle
Number
Cancel
Enter Full Name
Enter Phone
Number
Book Now
Figure 25: Activity Diagram - Booking
61
7.2.1.9 Activity Diagram - Direct Entry
Direct
Entry
Open
VehicleEntryAPI /
PostMan
Vehicle Entry Allocate Spot Vehicle Exit
Add Vehicle
Number Add Spot Add Vehicle
Code Number
Auto Add
Vehicle Detail ID: Identity Int
Add Status :
"Occupied"
Add Vehicle
Type Generate
Invoice
Auto Entry
Type: Direct
Entry Print Invoice
Auto Add
Date:
Date.Now
Auto Add Entry Time : Time.Now
Auto Add
Status : IN
Figure 26: Activity Diagram - Direct entry
62
7.2.2 Database Design

7.2.2.1 Entity Relationship Diagram
The structure of the database is thoroughly illustrated with the help of entity relationship
diagram. Simply, we can term it as blueprint of database to be implemented for the system or
application. There are various shapes that has to be considered while designing ER-diagram
(Beginnersbook, 2012-2020). The diagram of database design model of e-Parking is attached
in APPENDIX V.
7.2.2.2 Database Table Structure

In the process of creating database, once we have listed entities and attributes that will be
needed, next step is to layout the visual representation of database. To do so, it is necessary to
have clear knowledge about exactly how relational databases are structured. The database
table structure shows the entiy name, attribute name, datatype and constraints if any
(lucidchart, 2020). Below are the database table structure for e-Parking.
Table 13: Pms_booking
Pms_booking
Column Name Data Type Allow Nulls
booking_id Int No
vehicle_type_id Int No
Full_name Varchar(50) No
vehicle_no varchar(50) No
phone_no varchar(50) No
booking_date Datetime No
booking_status_id Int Yes
booking_time Time(7) Yes
63
Table 14: Pms_booking_status
Pms_booking_status
Column Name Data Type Allow Null
status_id Int No
Description varchar(50) No
Table 15: Pms_invoice_dtl
Pms_invoice_dtl
invoice_id Int No
invoice_no varchar(50) No
rate decimal(18, 0) No
amount decimal(18, 0) No
vehicle_dtl_id Int No
Table 16: Pms_parking_price
Pms_parking_price
price_id Int No
price_per_hour decimal(18, 0) No
64
Table 17: Pms_parking_spot
Pms_parking_spot
spot_id Int No
spot_code varchar(50) No
parkinglot_dtl_id Int No
status varchar(50) Yes
parkinglot_mst_id Int Yes
booking_id Int No
Table 18: Pms_parkinglot_dtl
Pms_parkinglot_dtl
parkinglot_dtl_id Int No
parkinglot_mst_id Int No
capacity Int No
price Int Yes
Table 19: Pms_parkinglot_mst
Pms_parkinglot_mst
parkinglot_mst_id Int No
65
name varchar(50) Yes
total_capacity Int Yes
code varchar(20) Yes
Table 20: Pms_vehicle_detail
Pms_vehicle_detail
Vehicle_dtl_id Int No
Vehicle_number Nvarchar(50) No
Vehicle_type Int No
Entry_type Varchar(50) Yes
Entry_date Datetime Yes
Exit_date Datetime Yes
Entry_time Varchar(50) Yes
Exit_time Varchar(50) Yes
Parked_hour Varchar(50) Yes
Price Varchar(50) Yes
Satus Varchar(50) Yes
Booking_id Int Yes
Table 21: Pms_vehicle_type
Pms_vehicle_type
66
Vehicle_type_id Int No
Description Varchar(50) Yes
Code Varchar(20) Yes
Table 22: AspNetUsers
AspNetUsers
Id Nvarchar(450) No
UserName Nvarchar(256) Yes
NormalizedUserName Nvarchar(256) Yes
Email Nvarchar(256) Yes
NormalizedEmail Nvarchar(256) Yes
EmailConfirmed Bit No
PasswordHash Nvarchar(Max) Yes
SecurityStamp Nvarchar(Max) Yes
ConcurrencyStamp Nvarchar(Max) Yes
PhoneNumber Nvarchar(Max) Yes
PhoneNumberConfirmed Bit No
TwoFactorEnable Bit No
LockoutEnd Datetimeoffset(7) Yes
LocuoutEnable Bit No
AccessFailedCount Int
67
7.2.3 Interface Design (Story Board)

7.2.3.1 Interface for Dashboard
Page Title: Dashboard
Content: The page is created for the customers ease as the page will show key data like total
spaces, total vacant spaces, total revenue generated, recent booking list, recent direct vehicle
entry list etc.
Header
Statistics Statistics Statistics Statistics
Statistics
Statistics
Side Bar / Navigation
Statistics
Statistics
Statistics
Statistics
Statistics
Footer
Background: White Audio: N/A
Color Scheme: Black, Blue, Orange, Green, Red, and Purple Video: N/A
Text Attributes: Helvetica Neue, Helvetica, and Arial, sans-serif Stills: N/A
68
7.2.3.2 Interface for Vehicle Info

Page Title: Vehicle Info
Content: The page consists header at top followed by footer at the button. The left side
consists the side bar through which we can navigate. The body in vehicle info page will
contain detailed list of vehicle entered in the parking lot. Details like vehicle id, vehicle type,
entry exit date time, amount generated etc.
Header
Heading Heaing

Table / List
Footer
Color Scheme: Black, Blue, and Purple Video: N/A
69
7.2.3.3 Interface for Parking Spot

Page Title: Parking Spot Page
Content: The general format of all the page is same, what differs is the body part. In this
interface, the parking lot’s design will be shown with all parking spaces/spots it possesses.
The color in parking spot indicated if it is vacant, reserved or occupied.
Header
Color Help Color Help Color Help

Heaing Heading
Parking Lot 1 - Spots Parking Lot 2 - Spots
Parking Lot 3 - Spots
Footer
70
7.2.3.4 Interface for New Booking

Page Title: New Booking
Content: The page contains booking form through which all the information for booking an
spot will entered into the system.
Header
Heaing Heading

Booking Form
Footer
71
7.2.3.5 Basic Interface

Page Title: Basic Interface – The base interface that all the interfaces follows
Content: The e-Parking follows the basic interface which is given below. The interface shown
below is the basic format in which all the pages of e-Parking are designed in.
Header
Heading Heaing

Table / List
Footer
72
7.2.3.6 Interface for Login/Register

Page Title: Login/Register
Header
Heaing Heading

Form
Footer
73
8 CHAPTER 8: PROJECT PLAN

8.1 Features
In order to get information about the features and functionality that system will possesses at
particular time frame, the project plan is developed. It is a estimation of task to be completed
at the expected deadline. The system that I have proposed is e-Parking, a web application
based on ASP.NET. Features are something that are responsible for acquiring objectives of
the project. Some of the features that will facilitate the project are:
 Responsive design.
 User Friendly Interface.
 Adding Parking lot visual design to find the overview of parking lot and parking spot.
 Adding booking facility.
8.2 Details of Release Plan
It is necessary to go through various version control processes for any software or application
development. The version released afterward always will have certain changes, updates or
modifications. Each version propels the step to reach final system. Comparatively, it is likely
for new version to have better features and efficiency.
8.2.1 Version 1.0 of e-Parking
Version 1.0 is the first version of e-Parking. The version was launched with partial features
that system should possess. Following features were included in Version 1.0:
 Login & Register

 Add New User Page
 Vehicle Detail and Parking Lot Interface
 Add Parking Lot Page
 Price and Vehicle Entry Controller
All the features mentioned above were working as expected and were tested successfully. At
the launch of first version, it was considered that the rest of the features would be included in
coming version of project.
74
8.2.2 Version 2.0 of e-Parking
For successful completion of project under the specified deadline, it is necessary to work on
version 2 of the project right away. So, immediate actions were taken right after the launch of
‘Version 1.0 of e-Parking’. The Version 2.0 includes following features:
 Dashboard Page
 Invoice Detail Page
 Print Invoice Function
 Direct Vehicle Entry Function
 Set up page for Vehicle type and Booking
 Logout
 Design Formulation (For Good Design Interface)
Version 2.0 is the final release of the system, with previous and this version of the system, the
features listed covers all the objectives of the system. Even though the system possesses what
it needs to have to give possible benefits, more improved features and functionalities can be
implemented in order to increase flexibility and efficiency of application. If project is
considered for the future enhancement those features will definitively be included.
8.3 Test Plan

8.3.1 Unit Testing Plan
8.3.1.1 Test Plan for Register and Login
Table 23: Test Plan for Signup or Register
Test Plan for Sign up / Register
Test Test Description Expected Result Actual Test Remarks

No. Output Priority
TR1 Keep all the fields Following validation Shown in High

blank and Submit the message will appear: Testing
Sign up form Section
 Email Field is
required.
75
 Password Field is
required.
TR2 Fill Email and Following validation Shown in High

Password field only. message will appear: Testing
Section
 Password and
Confirm password
do not match.
TR3 Fill Email, Password Following validation Shown in High

and Confirm message will appear: Testing
Password field only. Section
 Username is
invalid can only
contain letter or
digits.
TR4 Fill Email without Validation message Shown in High

@gmail.com. with, The Email field Testing
is not a valid e-mail Section
address, will appear.
TR5 Fill Password field Validation message Shown in High

with 3 letters. with, The Password Testing
must be at least 6 and Section
at max 100 characters
long, will show up.
TR6 Fill Password field Following validation Shown in High

with 8 letters. No message will appear: Testing
numbers, Section
 Passwords must
alphanumeric, and
have at least one
Uppercase letters
non alphanumeric
included.
character.
76
 Passwords must
have at least one
digit ('0'-'9').
 Passwords must
have at least one
uppercase ('A'-'Z').
TR7 Fill all the fields with Redirected to Shown in High

valid input types. Dashboard. Testing
Section
Table 24: Test plan for sign in or log in
Test Plan for Sign in/ Log in
Test Test Description Expected Result Actual Test Remarks

No. Output Priority
TL1 Click Login button Following validation Shown in High

leaving all the field message will appear: Testing
empty Section
 The Username
field is required.
 The Password
field is required.
TL2 Login with incorrect Error message will Shown in High

username and appear, invalid login Testin
correct password. attempt, in the screen. g
Sectio
n
TL3 Login with correct Error message will Shown in High
username and appear, invalid login Testin
incorrect password. attempt, in the screen. g
Sectio
n
77
TL4 Login with correct Successfully Shown in High

username and redirected to Testing
correct password Dashboard. Section
Table 25: Test Plan For Add User
Test Test Conditions Test Expected Actual Test Remarks

No. Description Result Result Priority
TAU1 Email: Empty User Add Shown in High

Fields Unsuccessful Testin
Username:
g
Password: Sectio
n
Confirm
Password:
Phone No:
TAU2 Email: Complete User Add Shown in High

and Valid Testing
pathmaker1999@ Successful
Values Section
gmail.com
Username:
smIle17
Password:
*******
Confirm
Password:
****** Phone
No: 9846160011
78
8.3.2 Acceptance Testing Plan
Table 26: Acceptance testing plan
Tester’s Name
Date of Testing
S.N. Test Questions Test Rating (Out of 5)
1 2 3 4 5
1 User Friendly
2 Design
3 Ease in System Usage
4 Consistency
5 System Flexibility
6 Appropriate Tests Used
7 System Performance
- Error Free
- System Validation
8 Software Efficiency
9 Satisfaction
Feedbacks:
79
9 CHAPTER 9: IMPLEMENTATION
9.1 Screenshots
In this section, the screenshots of all the pages that the system possesses are attached and
described in short.
9.1.1 Screenshots for Login Page i.e. Login.cshtml

9.1.1.1 Description
User can login into the application with the valid username and password. Once logged in
he/she will be able to access the functions and features that the system possesses.
9.1.1.2 Screenshot
Figure 27: Screenshot - Login Page
80
9.1.2 Screenshots for Register/ Sign up i.e. Register.cshtml

9.1.2.1 Description
It is necessary for any user to be successfully registered in order to use the system. The below
shown field needs to be filled with valid data in order to register to the system.
9.1.2.2 Screenshot
Figure 28: Screenshot - Register page
81
9.1.3 Screenshots for Dashboard

9.1.3.1 Description
Once registered and logged in the user will be redirected to this page on which the detail data
from different pages will be shown for the user’s ease. Details like number of total parking
lot, number of vacant spot, recent booking, recent list of entered vehicle etc. will be shown in
this page.
9.1.3.2 Screenshot
Figure 29: Screenshot - Dashboard
82
9.1.4 Screenshots for Vehicle Info List

9.1.4.1 Description
This page consists all the list of vehicles that have entered in the parking lot through direct
vehicle entry. Details like vehicle number, vehicle type, entry & exit date, total parking hour,
amount and status will be shown in this page.
9.1.4.2 Screenshot
Figure 30: Screenshot - Vehicle Info
83
9.1.5 Screenshots for Add Parking Lot

9.1.5.1 Description
User can add the parking lot as per his requirement or as per the parking lot he/she owns.
Parking lot name, short name, vehicle type, capacity that the lot possesses and price needs to
be added in order to add parking lot to the system.
9.1.5.2 Screenshot
Figure 31: Screenshot - Add Parking Lot
84
9.1.6 Screenshots for Parking Lot List

9.1.6.1 Description
The page shows list of parking lots added by user in previous screen i.e. Add Parking Lot.
9.1.6.2 Screenshot
Figure 32: Screenshot - Parking Lot List
85
9.1.7 Screenshots for Parking Spot

9.1.7.1 Description
As the user adds parking lot to the system, design of parking lot will be created automatically.
With vacant color mark, once a spot is allocated to a vehicle during vehicle entry the
allocated spot will change its color to orange i.e. ‘Occupied’. The color will be purple in case
of booking.
9.1.7.2 Screenshot
Figure 33: Screenshot - Parking Spot
86
9.1.8 Screenshots for Booking

9.1.8.1 Description
User can book client or customer on this table. Customer will have to call and specify the
booking details. The booking will be valid until all the spots are occupied. Date of booking,
time, vehicle type, vehicle number, full name and phone number are the details that needs to
be mentioned during booking.
9.1.8.2 Screenshot
Figure 34: Screenshot - Booking
87
9.1.9 Screenshots for Update Booking

9.1.9.1 Description
Booking can be updated and the status of booking can be changed from this page. At first the
booking will be ‘pending’. It can be changed to ‘confirmed’ or to ‘cancelled’.
9.1.9.2 Screenshot
Figure 35: Screenshot - Update Booking
88
9.1.10 Screenshots for User List

9.1.10.1 Description
The page shows the number of users that the system possesses. All the users in the user list
have full right to use all the features of the system.
9.1.10.2 Screenshot
Figure 36: Screenshot - User list
89
9.1.11 Screenshots for Add User

Form this page registered user can add new user to the system. The user will be able to access
the system as the registered user.
9.1.11.2 Screenshot
Figure 37: Screenshot - Add user page
90
9.1.12 Screenshots for Direct Vehicle Entry

With entering the vehicle identification number at the time of vehicle entry, direct vehicle
entry is done.
9.1.12.2 Screenshot
Figure 38: Screenshot - vehicle entry
91
9.1.13 Screenshots for Spot Allocation

For the entered vehicle a spot is given to which the person can park his/her vehicle. The status
will be changed to ‘OCCUPIED’ at the same time.
9.1.13.2 Screenshot
Figure 39: Screenshot - Spot Allocation
92
9.1.14 Screenshots for Vehicle Exit

At the time of vehicle exit, the vehicle identification number is entered to the system. After
that the total parking price is calculated and invoice is generated.
9.1.14.2 Screenshot
Figure 40: Screenshot - Vehicle Exit
93
9.2 Sample Codes

9.2.1 Sample codes written for i.e. Login.cshtml
Figure 41: Screenshot - Sample Code Login
94
9.2.2 Sample codes written for Register.cshtml
Figure 42: Screenshot Sample Code - Register
95
9.2.3 Sample codes written for Logout.cshtml.cs
Figure 43: Screenshot - Sample code Logout
96
9.2.4 Sample codes written for Create Parking Price
Figure 44: Screenshot - Create parking price
97
10 CHAPTER 10: SYSTEM VALIDATION

10.1 Unit testing
10.1.1 Unit testing for Login
Table 27: Unit Testing - Login
Unit Testing for Sign in/ Log in
Test No. Test Description Expected Result Actual Output Remarks
TL1 Click Login button Following validation Login Failed

leaving all the field message will appear:
empty
 The Username field is
required.
 The Password field is
required.
TL2 Login with incorrect Error message will Login Failed

username and correct appear, invalid login
password. attempt, in the screen.
TL3 Login with correct Error message will Login Failed

username and incorrect appear, invalid login
password. attempt, in the screen.
TL4 Login with correct Successfully redirected to Logged In

username and correct Dashboard. Successfully
password
98
10.1.2 Unit Testing of Register
Table 28: Unit Testing Register
Unit Testing for Sign up / Register
Test Test Description Expected Result Actual Remarks

No. Output
TR1 Keep all the fields blank Following validation Register

and Submit the Sign up message will appear: Failed
form
 Email Field is
required.
 Password Field is
required.
TR2 Fill Email and Password Following validation Register

field only. message will appear: Failed
 Password and
Confirm password do
not match.
TR3 Fill Email, Password and Following validation Register

Confirm Password field message will appear: Failed
only.
 Username is invalid
can only contain letter
or digits.
TR4 Fill Email without Validation message with, Register

@gmail.com. The Email field is not a Failed
valid e-mail address, will
appear.
99
TR5 Fill Password field with 3 Validation message with,

letters. The Password must be at
least 6 and at max 100
characters long, will show
up.
TR6 Fill Password field with Following validation Register

8 letters. No numbers, message will appear: Failed
alphanumeric, and
 Passwords must have
Uppercase letters
at least one non
included.
alphanumeric
character.
at least one digit ('0'-
'9').
at least one uppercase
('A'-'Z').
TR7 Fill all the fields with Redirected to Dashboard. Successfully

valid input types. Registered
10
Table 29: Unit Testing Add User
Test Test Conditions Test Expected Actual Test Remarks

No. Description Result Result Priority
TAU1 Email: Empty User Add Shown in High

Fields Unsuccessful Testin
Username:
g
Password: Sectio
n
Confirm
Password:
Phone No:
TAU2 Email: Complete User Add Shown in High

and Valid Testing
pathmaker1999@ Successful
Values Section
gmail.com
Username:
smIle17
Password:
*******
Confirm
Password:
****** Phone
No: 9846160011
10
10.2 User acceptance testing
Table 30: Acceptance testing - Test 1
Tester’s Name Dikshit Guragain
Date of Testing January 19, 2020
1 2 3 4 5
1 User Friendly
2 Design
4 Consistency
- Error Free
- System Validation
9 Satisfaction
Feedbacks:
10
Table 31: Acceptance testing -Test 2
Tester’s Name Inusha Aaryal
Date of Testing January 24, 2020
1 2 3 4 5
1 User Friendly
2 Design
4 Consistency
- Error Free
- System validation
9 Satisfaction
Feedbacks:
10
Table 32: Acceptance Testing - Test 3
Tester’s Name Saudibya Regmi
Date of Testing 24 January 2020
1 2 3 4 5
1 User Friendly
2 Design
4 Consistency
- Error Free
- System validation
9 Satisfaction
Feedbacks:
10
11 CHAPTER 11: CONCLUSION AND REFLECTIONS

11.1 Critical Evaluation
At the end of the final year project report, I got to learn so many things in making the project
successful and complete in every possible way. Every chapters had new learning
opportunities for me. The Introduction, taught be how to write project introduction based on
the gathered information and intended project details. Introduction was followed by key
headings like aim, objectives, potential benefits, rationale, nature of challenges, project plan
etc. Literature review was yet another challenging but qualitative chapter. Knowing about
current trend on parking system, systems already in use in context of parking system in Nepal
and across the world was really worth knowing. Both the technical and domain research, and
similar systems gave so many things to learn. Questionnaire was the research method that
was used in order to conduct the survey. Survey was challenging yet very productive. I got to
know about how the survey should be conducted and how the data should be analyzed and so
on. At the second half of the project, I had to build an application followed with different
designs; system architecture, database design, use case, activity diagram and so on. Also
testing plan and testing were key aspects that I got to work thoroughly.
The world of technology has been growing every minute, technology has advanced almost
every elements that currently persists in the planet. So, it can be considered to be obvious that
the technology can offer huge benefits in the field of parking too.
Since, the project had very limited time frame under which research and application
development had to be done. As the application development was supposed to start after the
completion of research report and project report, I have chosen water fall as my software
development methodology. The system was developed with one of the trending and powerful
platform i.e. ASP.NET. C# is used as the programming language along with JavaScript in
some extent. Many challenges were faced during the development though were tackled
successfully to reach the objective of the proposed system.
11.2 Limitations
The proposed system has many functions and functionalities but they can be improved for the
application to stand tall in long run. All the users who manipulate the system has complete
access to the system which may cause problem. On the other hand the system must be
10
operated
10
manually by human, there is more chances of mistakes to happen as human more likely to
make one. Also human interaction might slow up the working process than that of artificial
sensors. These are some limitations that the system possesses which possibly can be reduced.
11.3 Future Enhancement
Numerous features and functionalities have been included in the developed system. For
betterment of system and increase efficiency there is need of more features to be added in the
system. The proposed system does not facilitate any client in order to book the parking spot.
The feature can be considered as the future enhancement that the system would not just be an
admin portal but a common platform for both admin and client; authorizing minimal access to
client. The best way to make application to work smart is make it smart i.e. implementation
of IOT in ‘e-Parking’. Image recognition for vehicle entry and exit, IR sensors in each
parking spot so that the spot status would be automatically recorded. These two
implementations would cut off the human interaction in the system making it more profitable,
effortless and secure. Nevertheless, provision of limited access to user can also be
implemented to the system so that the owner can have more control over the system.
The ultimate result of the enhancements mentioned above will reduce the admin’s work.
Booking operation from client himself and parking manipulation from IOT devices would be
worth the investment.
11.4 Conclusion
The proposed system was chosen after the detailed analysis of current environment of parking
system. Though many parking lots were being constructed to overcome the parking problem
it was found that the parking lots available were not manipulated properly. So in order to
manipulate the parking lots I came up with solution called ‘e-Parking’ which ensures each
parking spot is used at its best. That is possible when one can track the spot that is empty or
vacant. The detail of system is illustrated in the paragraph below for better understanding.
E-Parking is a cost effective, efficient, admin portal from which admins can regulate parking
actions. It is a web based application that is intended to entertain big parking lots like of
Shopping Malls, Movie Theaters, Big Marts, Hotels, Office Buildings, airports, stadiums, and
Colonies. Where the population of vehicles will be high and where surged parking approach
is implemented. E-Parking clearly is intended to track the parking space/spot to be able to use
10
the
10
parking spot as the vehicle leaves the parking lot. The general procedure would be: The
vehicle identification number is added to the system and a vacant parking spot is provided.
The time in which the VIN is added is recorded by system as entry time. At the time of
vehicle exit, the VIN is entered. The time vehicle exits is noted and total parking time is
calculated. Based on that the bill gets generated. And the parking spot status is changed to
vacant again in the system. Nevertheless, total revenue generated is also visible in dashboard
and report in invoice page.
The developed system is designed in way it is easy for admin to use the system with foremost
comfort. No admin will have to face difficulties while operating the system. The system will
definitely help to make most out of any parking lot.
For the successful completion of the project, many research were done, in order to gather
information regarding the topic, problem and possible solutions, Questionnaire was prepared
and survey was conducted. Also different research papers, websites, newspapers and books
were studied. Nevertheless, communication and discussions were done with different sectors
of people.
Similarly, at the phase of development, technical research was conducted to acquire the
technical knowledge. Consulting with seniors, teachers and colleagues also helped
enormously in application development. References from books journals articles, YouTube
videos, official documentation from Microsoft, online forums were taken for application
development.
Thanking university, college, supervisors, all the lecturers, family, colleagues and every
single person that supported me directly or indirectly for successful completion of my final
year project, I like to conclude the project report here.
10
12 References
1. Aditya Thakuri, 2019. Smart Parking facility starts at Newroad, Kathmandu |

What’s Smart Parking?. [Online]
Available at: https://www.autoncell.com/detail/news/smart-park-facility-start-
newroad-kathmandu-what-smart-parking
[Accessed 2019].
2. B360Nepal, 2019. Multi Storey Vehicle Parking Initiatives in Kathmandu. [Online]

Available at: https://www.b360nepal.com/feature/multi-storey-vehicle-parking-
initiatives-in-kathmandu.html
[Accessed 24 06 2019].
3. Beginnersbook, 2012-2020. ER Model in DBMS. [Online]

Available at: https://beginnersbook.com/2015/04/e-r-model-in-dbms/
[Accessed 07 01 2020].
4. Circontrol, 2019. The-parking-of-the-future-problems-challenges-and-solutions.

[Online]
Available at: https://circontrol.com/the-parking-of-the-future-problems-challenges-
and-solutions/
[Accessed 17 06 2019].
5. City Motorbike, 2019. KMC LAUNCHED SMART PARKING SYSTEM IN NEW

ROAD, KATHMANDU. [Online]
Available at: http://citymotorbike.com/kmc-launched-smart-parking-system-in-new-
road-kathmandu/
[Accessed 2019].
6. Citylab, 2019. parking-is-sexy-now-thank-donald-shoup. [Online]

Available at: https://www.citylab.com/transportation/2018/05/parking-is-sexy-now-
thank-donald-shoup/560876/
[Accessed 21 06 2019].
7. Expatica, 2019. Driving and parking rules in The Netherlands. [Online]

Available at: https://www.expatica.com/nl/living/transportation/driving-and-parking-
11
rules-in-the-netherlands-100583/
[Accessed 3 August 2019].
8. Faheem, S. M. G. K. M. R. H. Z., 2013. Intelligent Car Parking System. [Online]

Available at: https://www.elsevier.es/en-revista-journal-applied-research-technology-
jart-81-articulo-a-survey-intelligent-car-parking-S1665642313715803
[Accessed 2019].
9. Gianpaul Rachiele, 2018. Software development Methodologies. [Online]

Available at: https://medium.com/@gianpaul.r/software-development-methodologies-
a856883a7630
[Accessed 16 July 2019].
10. IBM, 2010. Database. [Online]

Available at: https://www.ibm.com/developerworks/library/ws-dbpick/index.html
11. John Dillard, 2018. Data Analysis Processes. [Online]

Available at: https://www.bigskyassociates.com/blog/bid/372186/The-Data-Analysis-
Process-5-Steps-To-Better-Decision-Making
12. ktm2day, 2018. vehicle-registration-in-nepal-crosses-3-million-mark. [Online]

Available at: https://www.ktm2day.com/2018/08/21/vehicle-registration-in-nepal-
crosses-3-million-mark/
[Accessed 23 06 2019].
13. KTM, P., 2019. App Details, Park KTM. [Online]

Available at:
https://play.google.com/store/apps/details?id=com.yarshastudio.smartparking&hl=en
[Accessed 2019].
14. Lifewire, 2019. Operating Systems. [Online]

Available at: https://www.lifewire.com/operating-systems-2625912
15. lucidchart, 2020. Database Design. [Online]

Available at: https://www.lucidchart.com/pages/database-diagram/database-design
[Accessed 11 01 2020].
11
16. Lucidchart, 2020. UML Activity Diagram. [Online]

Available at: https://www.lucidchart.com/pages/uml-activity-diagram
[Accessed 03 01 2020].
17. Margaret Rouse, 2019. Spiral Model. [Online]

Available at: https://searchsoftwarequality.techtarget.com/definition/spiral-model
[Accessed 2019].
18. Martyn Shuttleworth, Jun 19, 2008. Different Research Methods.. [Online]
Available at: https://explorable.com/different-research-methods
19. Merriam Webster, 2019. Observation. [Online]

Available at: https://www.merriam-webster.com/dictionary/observation
20. Michel Owayjan Beirut, Bahaa Sleem, Elio Saad, Amer Maroun entitled , 2017.
Parking management system using mobile application. Parking management system
using mobile application.
21. Nagar, A., n.d. [Online]

Available at: https://220913-671961-raikfcquaxqncofqfm.stackpathdns.com/wp-
content/uploads/2017/03/Issues-and-Challenges-of-Parking-in-Indian-Metropolises-
by-Avnika-Nagar.pdf
[Accessed 22 06 2019].
22. National Institute of Health, 2019. Data gathering and Analysis. [Online]
Available at: https://hr.nih.gov/competency/data-gathering-and-analysis
23. Pakistan Economist, 2019. The future of pakistan be cashless. [Online]

Available at: http://www.pakistaneconomist.com/2019/03/04/can-the-future-of-
pakistan-be-cashless/
[Accessed 2019].
24. Research Methodology, 2019. Data Collection Methods. [Online]

Available at: https://research-methodology.net/research-methods/data-collection/
[Accessed 09 September 2019].
11
25. SAP Application, 2011. Agile Method. [Online]

Available at: https://www.sapapplication.com/agilemethod.php
[Accessed 7 August 2019].
26. seguetech, 2014. microsoft-sql-server-vs-oracle-same-different/. [Online]

Available at: https://www.seguetech.com/microsoft-sql-server-vs-oracle-same-
different/
27. Shoup, D., 2007. Cruising For Parking. Volume ACCESS no. 30, pp. 16 - 22.
28. Shoup, D., 2015. Informal Parking: Turning Problems Into Solutions. ACCESS No.
46(Informal Parking), pp. 14 - 19.
29. Tatvasoft, 2017. Twelve Top Software development methodologies and its advantages
and disadvantages. [Online]
Available at: https://www.tatvasoft.com/blog/top-12-software-development-
methodologies-and-its-advantages-disadvantages/
30. therisingnepal, 2019. KMC’s smart parking bites dust. [Online]

Available at: http://therisingnepal.org.np/news/30945
[Accessed 2019].
31. therisingnepal, n.d. 17668. [Online]

Available at: http://therisingnepal.org.np/news/17668
[Accessed 25 06 2019].
32. tutorialspoint, 2019. Waterfall Model. [Online]

Available at: https://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm
33. VERACODE, 2019. Integrate Development Environment. [Online]

Available at: https://www.veracode.com/security/integrated-development-
environment
34. Visual Paragism, 2020. What is use case diagram. [Online]

Available at: https://www.visual-paradigm.com/guide/uml-unified-modeling-
11
language/what-is-use-case-diagram/
[Accessed 10 01 2020].
35. whoishostingthis, 2019. Operating Systems. [Online]

Available at: https://www.whoishostingthis.com/compare/operating-systems/
11
NP3F1901 FYP- NP0001
APPENDICES
APPENDIX I – TURNITIN REPORT

APPENDIX II – FYP POSTER

APPENDIX III – ENTITY RELATIONSHIP

MODEL/DIAGRAM
APPENDIX IV – LOG SHEETS

APPENDIX V – ETHICS FORM

APPENDIX VI – GANTT CHART

APPENDIX VII - QUESTIONAIRE

APPENDIX VIII – PROJECT PROPOSAL FORM

APPENDIX IX – PROJECT SPECIFICATION FORM

APPENDIX X – OFFLINE SURVEY

Fyp Doc Sample 5 It

Uploaded by

Document Information

Original Title

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

Fyp Doc Sample 5 It

Uploaded by

Copyright:

Available Formats

Final Year Project

A report submitted in partial fulfillment of the requirements of Asia Pacific

University of Technology and Innovation for the degree of

B.Sc. (Hons) Information

Technology Supervised by Ms.

Saujanya Regmi (NP000117)

KMC – Kathmandu Metropolitan City

VIN – Vehicle Identification Number

JSON – Java Script Object Notation

IDE – Integrated Development Environment

ITS – Intelligent Transportation System

VANET – Vehicular Ad-Hock Network

RSU – Restricted Stock Unit

GPS – Global Positioning System

GIS – Geographic Information System

RTVR – Real Time Vehicle Tracking and Recognition

ANPR – Automatic Number Plate Recognition

PHP – Hypertext Preprocessor

ASP.NET – Active Server Page

JSP – Java Server Page

SDM – Software/System Development Methodology

RDBMS – Relational Database Management System

SDLC – Software Development Life Cycle

SQL – Scripted Query Language

1.1 Background to the project...........................................................................................1

1.2 Problem context...........................................................................................................1

1.4 Potential benefits.........................................................................................................3

1.4.1 Tangible benefits..................................................................................................3

1.4.2 Intangible benefits................................................................................................4

1.5 Target users.................................................................................................................4

1.6 Scope and objectives...................................................................................................4

1.6.3 Deliverables - Functionality of the proposed system...........................................5

1.6.4 Nature of Challenges............................................................................................5

1.7 Overview of this Investigation report..........................................................................5

1.8 Project Plan..................................................................................................................7

1.8.1 Project Plan for First Semester.............................................................................7

1.8.2 Gantt chart..........................................................................................................10

2 CHAPTER 2: LITERATURE REVIEW........................................................................12

2.2 Domain research........................................................................................................12

2.2.1 Domain Research 1............................................................................................12

2.2.2 Domain Research 2............................................................................................13

2.2.3 Domain Research 3............................................................................................14

2.3 Similar System/s (with similar features)...................................................................15

2.3.2 Park KTM...........................................................................................................15

3 CHAPTER 3: TECHNICAL RESEARCH.....................................................................18

3.1 Programming language chosen..................................................................................18

3.2 IDE (Interactive Development Environment) chosen...............................................19

3.3 Database Management System chosen......................................................................19

3.4 Operating System chosen..........................................................................................20

4 CHAPTER 4: SYSTEM DEVELOPMENT METHODOLOGY....................................22

4.5 Chosen Methodology.................................................................................................26

5 CHAPTER 5: RESEARCH METHODS.........................................................................27

5.1.1 Data Gathering Analysis....................................................................................27

5.1.2 Project Deliverables...........................................................................................27

5.1.3 Focus on Methods..............................................................................................27

5.1.4 Data Collection...................................................................................................28

5.2.2 Questionnaire, Survey, Interviews, Focus Groups.............................................29

5.2.3 Objective of the Question...................................................................................29

6 CHAPTER 6: REQUIREMENTS VALIDATION..........................................................33

6.1 Analysis of Data........................................................................................................33

7 CHAPTER 7: SYSTEM ARCHITECTURE...................................................................46

7.2 Abstract Architecture.................................................................................................48

7.2.1 System Design....................................................................................................48