Module Code & Module Title

CS6P05NI Final Year Project

Assessment Weightage & Type

25% FYP Interim Report

Year and Semester

2020 Autumn

College ID:

Assignment Due Date:

Assignment Submission Date:
Word Count (Where Required): 3837

I confirm that I understand my coursework needs to be submitted online via Google Classroom under
the relevant module page before the deadline in order for my assignment to be accepted and marked.
I am fully aware that late submissions will be treated as non-submission and a mark of zero will be
awarded.
CS6P05NI Final Year Project

Acknowledgement
This interim report of Final Year Project is prepared in partial fulfilment with prescribed
rules and regulations of London Metropolitan University for Bachelor 3rd year, 1st
semester. It is the result of cooperation and support of Islington College and Final
Year Project internal supervisor Mr. Bibek Raj Joshi and external supervisor Mr.
Sumit Bajracharya.

So, I would like to express my hearty appreciation and gratitude to our respected
teachers Mr. Bibek Raj Joshi and Mr. Sumit Bajracharya for providing valuable
feedback, suggestion, guidance and monitoring for preparing this report and project.
Your precious time has certainly helped me in giving the meaning to my project work.

Last but not the least, I wish to express my sincere gratitude to my family, teachers,
friends and all those who helps me to complete this report.

Date:

NP01CP4A180002 | December 25, 2020

CS6P05NI Final Year Project

Summary
This report provides the overview in the progress of Digital Parking application which
is based on mobile and web. Mobile application for customer and staff whereas web
application for admin user. Here, mobile application is based on Flutter, Dart and web
application is based on Django Framework, Django Rest Framework and HTML, CSS
and Bootstrap. With the help of mobile application customer can view parking policy,
book parking slot before s/he reach to the destination and Staff user can make offline
booking for offline customer. Similarly, through web application admin user can
manage parking location details, view users’ feedback and can terminate staff as per
required.

In this report, detail progress of the final year project is included. This report has been
divided into five different chapters which are Introduction, Background/Literature
review, Development to data, Analysis of progress and Future Work. In Introduction
section project topic has been explained. Similarly, tools, technology and methodology
that has been used in this project has been explained in chapter Background/Literature
review.

Progress of project development is included in chapter Development to date. Similarly,

Analysis of progress chapter include the progress analysis to obtain the information
on the state of project, how it is being developed and it helps to determine the actual
progress of project according to Gantt chart. Thus, the chapter Future work include
the remaining task of this project.

NP01CP4A180002 | December 25, 2020

CS6P05NI Final Year Project

Table of Contents
1.Introduction ............................................................................................................. 1

1.1. Introduction to topic ....................................................................................... 1

1.2. Current Scenario ........................................................................................... 2

1.2.1. Nepal ...................................................................................................... 2

1.3. Problem Domain ........................................................................................... 3

1.4. Project Scope ................................................................................................ 4

1.5. End User ....................................................................................................... 4

1.6. Aims and objectives ...................................................................................... 5

1.7. Structure of Report ........................................................................................ 6

1.7.1. Introduction ............................................................................................. 6

1.7.2. Background/Literature review ................................................................. 6

1.7.3. Development to date .............................................................................. 6

1.7.4. Analysis of progress ............................................................................... 6

1.7.5. Future work............................................................................................. 6

1.7.6. References ............................................................................................. 6

1.7.7. Appendix................................................................................................. 6

2. Background/Literature review ............................................................................. 7

2.1. Technology used ........................................................................................... 7

2.1.1. UI Framework ......................................................................................... 7

2.1.2. Programming Language ......................................................................... 7

2.1.3. Framework.............................................................................................. 8

2.1.4. API .......................................................................................................... 8

2.1.5. Database ................................................................................................ 8

2.2. Methodology.................................................................................................. 9

2.2.1. Considered Methodology ........................................................................ 9

2.2.2. Selected Methodology ............................................................................ 9

NP01CP4A180002 | December 25, 2020

CS6P05NI Final Year Project

2.3. Review of similar project ............................................................................. 11

2.3.1. Similar Project ...................................................................................... 11

2.3.2. Comparison Between System .............................................................. 14

3. Development to date ......................................................................................... 16

3.1. Requirement Gathering ............................................................................... 16

3.1.1. Survey Conducted at Parking Location ................................................ 16

3.1.2. Conducted Online Survey with Public ................................................... 16

3.2. Use Case .................................................................................................... 17

3.3. Designed Logo for Application .................................................................... 18

3.4. SRS Document ........................................................................................... 18

3.5. High Level Use Case Diagram .................................................................... 18

3.6. Wireframes .................................................................................................. 18

3.7. ERD ............................................................................................................ 19

3.8. System Architecture Diagram...................................................................... 20

3.9. Database Migration ..................................................................................... 21

3.10. Developed features in Android ................................................................. 22

3.10.1. Display parking location in Google Map with Markers ....................... 22

3.10.2. Navigate to parking location using Google Map ................................ 23

3.10.3. Login Screen ..................................................................................... 24

3.10.4. User Register Screen ........................................................................ 25

3.10.5. User Feedback Screen ...................................................................... 26

3.11. Developed features in Web Application ................................................... 27

3.11.1. Manage Parking Location .................................................................. 27

3.11.2. Update Parking Location Page .......................................................... 27

3.11.3. Staff Registration Page ..................................................................... 28

3.11.4. Manage Staff Page............................................................................ 28

3.11.5. Staff Personal Detail.......................................................................... 29

NP01CP4A180002 | December 25, 2020

CS6P05NI Final Year Project

3.11.6. Staff Contract Detail Page ................................................................. 29

3.11.7. Staff Account Detail Page ................................................................. 30

3.11.8. Update Individual Staff Personal Detail Page .................................... 30

3.11.9. Update Staff Contract Page .............................................................. 31

3.11.10. User’s Feedback Page ................................................................... 31

4. Analysis of progress .......................................................................................... 32

4.1. Progress Table ............................................................................................ 32

4.2. Progress Review ......................................................................................... 34

4.3. Progress Timeline ....................................................................................... 34

4.4. Action Plan .................................................................................................. 34

5. Future work ....................................................................................................... 35

6. References ........................................................................................................ 37

7. Appendix ........................................................................................................... 41

7.1. SRS Document ........................................................................................... 41

7.1.1. Project Title: Digital Parking.................................................................. 41

7.1.2. Category: Web and Android application ............................................... 41

7.1.3. Introduction ........................................................................................... 41

7.1.4. Overall Description ............................................................................... 44

7.2. High Level Use Case Diagram .................................................................... 67

7.2.1. Actors of Digital Parking Application ..................................................... 67

7.2.2. Register People .................................................................................... 67

7.2.3. Login ..................................................................................................... 67

7.2.4. View Profile........................................................................................... 67

7.2.5. Online Parking Slot Booking ................................................................. 67

7.2.6. View Booked Parking Slot .................................................................... 68

7.2.7. Make Payment ...................................................................................... 68

7.2.8. Payment History ................................................................................... 68

NP01CP4A180002 | December 25, 2020

CS6P05NI Final Year Project

7.2.9. Send Feedback .................................................................................... 68

7.2.10. Parking Policy.................................................................................... 69

7.2.11. Offline Parking Slot Booking .............................................................. 69

7.2.12. Offline Payment ................................................................................. 69

7.2.13. History ............................................................................................... 69

7.2.14. Check Booked Parking Slot ............................................................... 70

7.2.15. Register Staff..................................................................................... 70

7.2.16. Deregister Staff ................................................................................. 70

7.2.17. View Staff .......................................................................................... 70

7.2.18. Register Location .............................................................................. 71

7.2.19. Deregister Location ........................................................................... 71

7.2.20. View Location .................................................................................... 71

7.2.21. View Feedback .................................................................................. 71

7.3. Wireframes .................................................................................................. 72

7.3.1. Common Wireframe of Android End User: Customer and Staff............ 72

7.3.2. Wireframes of Android End User: Customer......................................... 73

7.3.3. Wireframe of Android End User: Staff .................................................. 86

7.3.4. Wireframe of Web Application End User: Admin .................................. 94

7.4. Entity Relationship Diagram ...................................................................... 104

7.4.1. Possible entities.................................................................................. 104

7.4.2. Relationship Between Entities ............................................................ 105

7.4.3. Data Dictionary ................................................................................... 109

7.5. Project as a solution .................................................................................. 114

7.6. Revision of Milestone ................................................................................ 115

7.7. Revison of Project Gantt Chart.................................................................. 117

7.8. Considered Methodology .......................................................................... 118

7.8.1. Waterfall Model................................................................................... 118

NP01CP4A180002 | December 25, 2020

CS6P05NI Final Year Project

7.8.2. Unified Process .................................................................................. 119

7.8.3. Agile Methodology .............................................................................. 119

7.9. Selected Methodology............................................................................... 120

7.9.1. Rational Unified Process (RUP) ......................................................... 120

7.10. Survey at Parking Location .................................................................... 122

7.10.1. Buddha Mall - Machhapokhari ......................................................... 122

7.10.2. BG Mall – Gongabu ......................................................................... 126

7.10.3. Biswa Joyti Mall – Jamal ................................................................. 127

7.10.4. Rising Mall – Durbar Marg ............................................................... 131

7.10.5. City Center – Kamal Pokhari ........................................................... 135

7.10.6. World Trade Center ......................................................................... 136

7.10.7. CTC Mall – Sundhara ...................................................................... 140

7.10.8. Civil Mall – Sundhara ...................................................................... 144

7.10.9. Kathmandu Mall – Sundhara ........................................................... 148

7.10.10. Peoples Plaza .............................................................................. 152

7.11. Evidence as Invoice of Parking Location Survey ................................... 153

7.12. Conducted Online Survey with Public .................................................... 154

7.12.1. Do you have your own vehicle?....................................................... 154

7.12.2. When you go outside for your work with your own or friend’s or relative
vehicle, have you faced any difficulties in finding a parking location to park your
vehicle? 154

7.12.3. When you go outside for your work with your own or friend’s or relative
vehicle, where you usually park your vehicle? ................................................ 155

7.12.4. Have you faced any problems while parking your vehicle? If yes, then
list out the problems otherwise write no. ......................................................... 156

7.12.5. Name the android application which you generally use. .................. 157

7.12.6. Would an android application with features of online and offline vehicle
parking lot booking applications be developed? .............................................. 157

NP01CP4A180002 | December 25, 2020

CS6P05NI Final Year Project

7.12.7. Have you used any other android/web application in order to book a
parking lot to park your vehicle before you reach your destination?................ 158

7.12.8. If you had used any other mobile or web application to book the parking
lot then write down the name of the application (like Park KTM). What kind of
improvement should be done in their application? .......................................... 159

7.12.9. What kind of features would you like to suggest in developing parking
applications? ................................................................................................... 160

7.13. Dart code written in Android Studio for android application ................... 161

7.14. Git log of android studio code pushed at GitHub ................................... 164

7.15. Python code written in PyCharm for web application ............................. 165

7.16. Git log of web application code pushed at GitHub ................................. 166

NP01CP4A180002 | December 25, 2020

CS6P05NI Final Year Project

Table of figures
Figure 1: Review and rating of Park KTM application from play store (reviews.com.np,
2019)-------------------------------------------------------------------------------------------------------- 2
Figure 2: Survey report of people who had their own vehicle. ------------------------------ 3
Figure 3: Survey report of people who had faced difficulties in finding parking spaces
to park vehicle -------------------------------------------------------------------------------------------- 3
Figure 4: Survey report of people who had faced problem before and after parking
vehicle at parking space ------------------------------------------------------------------------------- 3
Figure 5: Similar System Park KTM (reviews.com.np, 2019) ------------------------------ 11
Figure 6: Similar System i.e. Smart Parking (SmartParking, 2020) ---------------------- 12
Figure 7: Similar System i.e. Smart Parking (Smart Parking, 2017) -------------------- 13
Figure 8: Overall System Use Case Diagram of Digital Parking Application ---------- 17
Figure 9: Logo of Digital Parking application --------------------------------------------------- 18
Figure 10: Initial ERD of Digital Parking application ----------------------------------------- 19
Figure 11: System Architecture Diagram ------------------------------------------------------- 20
Figure 12: Created database and tables -------------------------------------------------------- 21
Figure 13: Parking location displayed in google map with markers ---------------------- 22
Figure 14: Navigate to parking location using google map --------------------------------- 23
Figure 15: Login screen for staff and normal user -------------------------------------------- 24
Figure 16: Normal user (General Public) registration screen ------------------------------ 25
Figure 17: User Feedback Screen ---------------------------------------------------------------- 26
Figure 18: Manage Parking Location Page----------------------------------------------------- 27
Figure 19: Update Parking Location Page ------------------------------------------------------ 27
Figure 20: New staff registration page ----------------------------------------------------------- 28
Figure 21: Listed all registered staff at parking location ------------------------------------- 28
Figure 22: Display staff personal details according to staff id ----------------------------- 29
Figure 23: Display staff contract according to staff id ---------------------------------------- 29
Figure 24: Display staff account details according to staff id ------------------------------ 30
Figure 25: Update staff personal details according to staff id ----------------------------- 30
Figure 26: Update staff contract according to staff id ---------------------------------------- 31
Figure 27: Display all user feedback ------------------------------------------------------------- 31
Figure 28: System Perspective of Android and Web Application ------------------------- 44
Figure 29: Login Screen ----------------------------------------------------------------------------- 64

NP01CP4A180002 | December 25, 2020

CS6P05NI Final Year Project

Figure 30: Wireframe of login screen ------------------------------------------------------------ 72

Figure 31: Wireframe of drawer of customer --------------------------------------------------- 73
Figure 32: Wireframe of register screen for customer --------------------------------------- 74
Figure 33: Wireframe of Customer Dahsboard ------------------------------------------------ 75
Figure 34: Wireframe of location details screen (selected tab bar i.e. Details) ------- 76
Figure 35: Wireframe of location detail screen (selected tab bar i.e. Parking Slot) -- 77
Figure 36: Wireframe of available two-wheeler parking slot to book -------------------- 78
Figure 37: Wireframe of available four-wheeler parking slot to book -------------------- 79
Figure 38: Wireframe of alert dialogue for booking confirmation i.e. two or four-wheeler
------------------------------------------------------------------------------------------------------------- 79
Figure 39: Wireframe of feedback screen ------------------------------------------------------ 80
Figure 40: Wireframe to register customer eSewa Id ---------------------------------------- 81
Figure 41: Wireframe of Parking Slot Booked History Screen ---------------------------- 82
Figure 42: Wireframe of Transaction History Screen ---------------------------------------- 83
Figure 43: Wireframe of customer profile screen --------------------------------------------- 84
Figure 44: Wireframe of edit user profile screen ---------------------------------------------- 85
Figure 45: Wireframe of staff dashboard -------------------------------------------------------- 86
Figure 46: Wireframe to add new parking policy ---------------------------------------------- 87
Figure 47: Wireframe of staff profile screen ---------------------------------------------------- 88
Figure 48: Wireframe of change profile screen ------------------------------------------------ 89
Figure 49: Wireframe of offline booking screen for staff ------------------------------------ 90
Figure 50: Wireframe of offline booking form screen ---------------------------------------- 91
Figure 51: Wireframe of make slot available screen ----------------------------------------- 92
Figure 52: Wireframe of transaction history of staff ------------------------------------------ 93
Figure 53: Wireframe of login page web application ----------------------------------------- 94
Figure 54: Common side bar for all web pages ----------------------------------------------- 95
Figure 55: Wireframe of admin dashboard in web application ---------------------------- 96
Figure 56: Wireframe of user profile personal info page in web application ----------- 97
Figure 57: Wireframe of user profile account info page in web application ------------ 97
Figure 58: Wireframe of Change Password page in web application ------------------- 98
Figure 59: Wireframe of Feedback page in web application ------------------------------- 98
Figure 60: Wireframe to add new staff from web application ------------------------------ 99
Figure 61: Wireframe to manage registered parking location from web application - 99

NP01CP4A180002 | December 25, 2020

CS6P05NI Final Year Project

Figure 62: Wireframe to update registered parking location image from web application
----------------------------------------------------------------------------------------------------------- 100
Figure 63: Wireframe of Manage Staff page in web application ------------------------ 100
Figure 64: Wireframe of staff profile, contract info page in web application --------- 101
Figure 65: Wireframe of staff profile, personal info page in web application -------- 101
Figure 66: Wireframe of staff profile, contract info page in web application --------- 102
Figure 67: Wireframe of transaction page in web application --------------------------- 103
Figure 68: Wireframe of manage eSewa page in web application --------------------- 103
Figure 69: Relationship between entity parking location and user --------------------- 105
Figure 70: Relationship between entity User and Staff------------------------------------ 105
Figure 71: Relationship between entity Parking_Location and Parking_Policy ----- 105
Figure 72: Relation between entity Parking Policy and Staff ---------------------------- 106
Figure 73: Relation between entity User and Feedback ---------------------------------- 106
Figure 74: Relation between entity User and eSewa -------------------------------------- 106
Figure 75: Relation between entity User and Slot_Booking------------------------------ 107
Figure 76: Relation between entity Staff and Slot_Booking ------------------------------ 107
Figure 77: Relation between entity Staff and Payment------------------------------------ 108
Figure 78: Relation between entity eSewa and Payment--------------------------------- 108
Figure 79: Revision of Project Milestone ------------------------------------------------------ 115
Figure 80: Revision of Project Gantt Chart --------------------------------------------------- 117
Figure 81: Phases of Waterfall Model (Jones & Waddell, 2019) ----------------------- 118
Figure 82: Unified Process (anuragmbst, 2013) -------------------------------------------- 119
Figure 83: Agile Methodology (Chauhan, 2019) -------------------------------------------- 119
Figure 84: Phases of RUP (ang, 2012) -------------------------------------------------------- 120
Figure 85: Invoice of parking location ---------------------------------------------------------- 153
Figure 86: Survey report of people who had their own two, four-vehicle ------------- 154
Figure 87: Survey report of people who had faced problem to find parking location to
park vehicle ------------------------------------------------------------------------------------------- 154
Figure 88: Survey report of people regarding where they usually park their vehicle
----------------------------------------------------------------------------------------------------------- 155
Figure 89: Problems faced by people while parking their vehicle ---------------------- 156
Figure 90: Name of android application which generally used by people. ----------- 157
Figure 91: Response of people regarding an android application should be developed
with online and offline vehicle parking lot booking. ----------------------------------------- 157

NP01CP4A180002 | December 25, 2020

CS6P05NI Final Year Project

Figure 92: Response of people regarding the use of android application like Park KTM
to book the parking lot------------------------------------------------------------------------------ 158
Figure 93: Response of people regarding the improvements in application like Park
KTM ----------------------------------------------------------------------------------------------------- 159
Figure 94: Suggested features for developing application by people ----------------- 160
Figure 95: Screenshot of location model ------------------------------------------------------ 161
Figure 96: Screenshot of dependency used for android application development- 161
Figure 97: Screenshot of location provider --------------------------------------------------- 162
Figure 98: Screenshot of local API used in android application ------------------------ 163
Figure 99: Screenshot of user model ---------------------------------------------------------- 163
Figure 100: Screenshot of git log of android code ------------------------------------------ 164
Figure 101: Screenshot of creating user serializer ----------------------------------------- 165
Figure 102: Screenshot of Customizing User Model--------------------------------------- 165
Figure 103: Screenshot of path URL to navigate pages ---------------------------------- 166
Figure 104: Screenshot of git log of web code pushed at GitHub ---------------------- 166

NP01CP4A180002 | December 25, 2020

CS6P05NI Final Year Project

Table of tables
Table 1:Features comparison between similar system-------------------------------------- 15
Table 2: Progress table of Project according to Gantt Chart------------------------------- 33
Table 3: Functional requirement description of register people --------------------------- 50
Table 4: Functional requirement description of login ---------------------------------------- 51
Table 5: Functional requirement description of online vehicle parking slot booking - 52
Table 6: Functional requirement description of user's profile ------------------------------ 53
Table 7: Functional requirement description of payment history ------------------------- 54
Table 8: Functional requirement description of feedback option ------------------------- 55
Table 9: Functional requirement description of parking policy ---------------------------- 56
Table 10: Functional requirement description of offline vehicle parking slot booking 57
Table 11: Functional requirement description of offline payment ------------------------- 58
Table 12: Functional requirement description of transaction history of staff user ---- 59
Table 13: Functional requirement description of staff registration ------------------------ 60
Table 14: Functional requirement description of staff deregistration -------------------- 61
Table 15: Functional requirement description of register location ------------------------ 62
Table 16: Functional requirement description of feedback receive ---------------------- 62
Table 17: Functional requirement description of transaction history of admin user - 63
Table 18: Non-functional requirement description of performance requirements ---- 65
Table 19: Safety requirement, non-functional requirement description ----------------- 65
Table 20: Other software quality attributes, non-functional requirement description 66
Table 21: Identification of actors ------------------------------------------------------------------ 67
Table 22: High level use case description of register people ------------------------------ 67
Table 23: High level use case description of login ------------------------------------------- 67
Table 24: High level use case description to view profile ----------------------------------- 67
Table 25: High level use case description of online parking slot booking -------------- 67
Table 26: High level use case description of view booked parking slot ----------------- 68
Table 27: High level use case description of make payment ------------------------------ 68
Table 28: High level use case description of payment history ---------------------------- 68
Table 29: High level use case description of send feedback ------------------------------ 68
Table 30: High level use case description of parking policy ------------------------------- 69
Table 31: High level use case description of offline parking slot booking -------------- 69
Table 32: High level use case description of offline payment ----------------------------- 69

NP01CP4A180002 | December 25, 2020

CS6P05NI Final Year Project

Table 33: High level use case description of history ----------------------------------------- 69

Table 34: High level use case description of check booked parking slot --------------- 70
Table 35: High level use case description of register staff --------------------------------- 70
Table 36: High level use case description of staff deregistration ------------------------- 70
Table 37: High level use case description to view staff details ---------------------------- 70
Table 38: High level use case description to register location ---------------------------- 71
Table 39: High level use case description to deregister location ------------------------- 71
Table 40: High level use case description to view location details ----------------------- 71
Table 41: High level use case description to view user's feedback ---------------------- 71
Table 42: Data dictionary of entity Parking_Location -------------------------------------- 109
Table 43: Data dictionary of entity user ------------------------------------------------------- 110
Table 44: Data dictionary of entity staff -------------------------------------------------------- 110
Table 45: Data dictionary of entity parking_policy ------------------------------------------ 111
Table 46: Data dictionary of entity feedback ------------------------------------------------- 111
Table 47: Data dictionary of entity esewa----------------------------------------------------- 111
Table 48: Data dictionary of entity slot_booking -------------------------------------------- 112
Table 49: Data dictionary of entity payment -------------------------------------------------- 113

NP01CP4A180002 | December 25, 2020

CS6P05NI Final Year Project

Table of Abbreviations
S.N. Abbreviations Full Form
1. UI Users Interface
2. API Application Programming Interface
3. OS Operating System
4. DBMS Database Management System
5. UP Unified Process
6. UML Unified Modeling Language
7. OUP Open Unified Process
8. RUP Rational Unified Process
9. AUP Agile Unified Process
10. IDE Integrated Development Environment
11. BaaS Backend-as-a-Service
12. QR Code Quick Response Code

NP01CP4A180002 | December 25, 2020

CS6P05NI Final Year Project

1. Introduction
1.1. Introduction to topic
The title of this project “Digital Parking”. It is the strategy of parking that
incorporates both human and technological advances to use few resources
like fuel, time, spaces and denser vehicle parking for most of the time they
remain idle. (Wessel, 2016)

People are facing lots of problem, before and after parking their vehicle
either on street or off-street. Here, people are frustrated to search parking
space to park their vehicle. Similarly, after parking vehicle in parking spaces,
most of the vehicle owner vehicles gets scratched, helmet stolen etc. due to
the inconvenient parking option and they are confusion in parking location
policies. (Associates, 2003)

To solve these types of problem, this project is being developed in android

and web application. Android application for customer/people and staff
whereas web application for admin.

Page | 1
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

1.2. Current Scenario

1.2.1. Nepal
This is the era of advance technology where people from every aspect
around the world are learning towards the new technology to make the
maximum use of it, to have better facilities and luxurious lifestyle. The use
of mobile phones creatures is now in the blood of every single human being
living on the earth. (Sewell, 2017) Thus, there are less IT industries in Nepal
who are carrying out the real-world project to solve the daily life issues. In
the context of Nepal, lots of parking spaces are unorganized. Due to this
reason, people, young youths are frustrated to find the parking spaces most
of the time to park their vehicle while going outside for their work.

In Nepal, to solve the parking issues, Kathmandu Metropolitan City (KMC)

has introduced a new mobile app called “Park KTM” whose main aim is to
provide Parking space for Two Wheeler’s and Four Wheeler’s.
(reviews.com.np, 2019) But it was found that “Park KTM” application does
not work properly. While reading the review of “Park KTM” application in
play store following common issues was found:

i. User must make a

phone call at parking
location for booking
confirmation.
ii. After choosing the
vehicle type, stuck is
not loaded.
iii. Parking cost is
expensive.

Thus, IT industries of Nepal

most develop the various
application to sole this issue. Figure 1: Review and rating of Park KTM application
from play store (reviews.com.np, 2019)

Page | 2
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

1.3. Problem Domain

Figure 2: Survey report of people who had their own vehicle.

Figure 3: Survey report of people who had faced difficulties in finding parking spaces to park vehicle

Figure 4: Survey report of people who had faced problem before and after parking vehicle at
parking space

Page | 3
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

From the public survey of Digital Parking application, it was found that 102
people had responded in a survey form. Out of 102 people, 54.9% two-
wheeler vehicle, 1% had four-wheeler vehicle, 3.9% had both two, four-
wheeler and 40.2% don’t have their own vehicle. Similarly, out of 102
people, 80.4% people had faced difficulties in finding parking space to park
their vehicle. So, from public survey it was found that people had faced the
following common problems:

a. Difficult to find parking space.

b. Vehicle gets scratched, No safety for vehicle.
c. Parking cost is expensive.
d. Parking spot is congested with two vehicles in one spot.
e. Confusion in parking location policies.

1.4. Project Scope

The android and web application are being developed for a particular
parking location in order to resolve the parking problems faced by people,
staff and parking owners like difficult to find parking location to park vehicle
(by people), confusion in parking policies (between people and staff),
difficult to track total fund raised from parking location (for parking owner)
etc.

1.5. End User

The end users of the android application would be customer (people) and
staff. Similarly, admin will be the end user of web application. The brief
description of end users’ benefit is kept in appendix sub section i.e.
Proposed System.

Page | 4
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

1.6. Aims and objectives

The project aimed to resolve the parking problems faced by people due to
unorganized urbanization in developing countries by developing user
friendly mobile and web application.

The objectives of this project are listed below:

a) Research on similar system.

b) Gather requirements from parking location to know the actual problem
what they had been faced in their parking location.
c) Gather requirements from public through online survey to know the
actual problem what they had been faced while parking their vehicle
either on street or off street.
d) To develop the android and web application to solve the issues of people
before and after parking vehicle and to solve the issues of parking
location.

Page | 5
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

1.7. Structure of Report

1.7.1. Introduction
Introduction consists of information about project, problem domain, end
users, project scope, aims and objectives of the project.

1.7.2. Background/Literature review

Background/Literature review consists of information about ends users,
understanding solution for problem, review of similar application, technology
and methodology that has been used in this project.

1.7.3. Development to date

In Development to date chapter, progress of project is included.

1.7.4. Analysis of progress

Analysis of progress chapter include the progress analysis to obtain the
information on the state of project, how it is being developed? This chapter
helps to determine the actual progress of project according to Gantt chart.

1.7.5. Future work

Future work includes the remaining task of this project to be carried out in
future.

1.7.6. References
In references section, it included all the references that are taken as
reference while doing this project, report.

1.7.7. Appendix
In appendix sections, it contains the brief description of SRS document, high
level use case diagram and wireframes with screenshot. Similarly,
relationship between entities are explained. Data dictionary of each entity is
kept. Additionally, it included brief description of project as solution,
considered and selected methodology. Thus, scanning images of survey
done at parking location, screen shot of android and web code are kept
here.

Page | 6
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

2. Background/Literature review
This application helps to solve the parking problems faced by people, staff and
parking owners like difficult to find parking location to park vehicle (by people),
confusion in parking policies (between people and staff), difficult to track total
fund raised from parking location (for parking owner) etc. This application is
primarily designed for a parking location and for general public.

2.1. Technology used

2.1.1. UI Framework
In this project Flutter is used as UI framework for android application
because Flutter is Google’s UI toolkit for building beautiful, natively compiled
application for mobile, web and desktop from a single codebase. (Flutter,
2020) Similarly, in future with the help of Flutter UI framework, an iOS
application can be developed from a single codebase.

2.1.2. Programming Language

a) Dart

Dart was created by Google in October 2011 which is client optimized

programming language for fast apps on any platform. (Dart, 2020) It is
an open source, structured, object-oriented programming language for
creating complex, android, web and desktop application. (Buckett, 2013)
Due to this reason, Dart programming language have been used for
android application.

b) Python

In this project Python is used in web application because it is a general

purpose, object-oriented programming language created by Guido van
Rossum. (Refsnes Data, 2020) It can be used in server-side to develop
either static or dynamic web application and can be used for rapid
prototyping or production ready software development. (Refsnes Data,
2020)

Page | 7
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

2.1.3. Framework
a) Django

Django Framework has been used in this project for web development
because it is a high level, fully featured web framework which purely written
in Python and enables for rapid development of secure and maintainable
websites. (django, 2005 - 2020)

b) Django REST Framework

Django REST framework is a powerful and flexible toolkit which makes more
easier for developer to build web APIs. It has been trusted by internationally
recognized companies including RedHat, Heroku and so on. Due to this
reason, Django REST framework has been used in this project. Thus, the
Django REST framework APIs will be used in mobile application to
communicate with database. (Django REST framework, 2020)

2.1.4. API
a) Geocoding API

Geocoding API enables us to associate longitude and latitude with an

associated address. (MAPQUEST, INC, 2018) Due to this reason,
Geocoding API is used in this project.

2.1.5. Database
a) MySQL

In this project, MySQL database has been because it is easy to connect and
manipulate MySQL database with Django framework.(Babu, 2018) Thus,
this database will be used to insert, update and delete data of users, parking
location and so on.

Page | 8
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

2.2. Methodology
2.2.1. Considered Methodology
a) Waterfall Model
b) Unified Process
c) Agile Methodology

Note: The description of considered methodology are kept in appendix section

i.e. Considered Methodology.

2.2.2. Selected Methodology

a) Rational Unified Process (RUP)

Ration Unified Process (RUP) is an object-oriented methodology created by

Rational Software Corporation. (ANWAR, 2014) This methodology has
been successfully applied by many organizations which makes easier to find
a professional with RUP experience. (ANWAR, 2014) Thus, this
methodology has been selected for this project because of the following
reasons which are listed below:

i. This project is an academic, yearlong project. So, here, time is bounded.

Within the given time, the project must be completed by fulfilling all the
requirements of users. If the defined requirement were not fulfilled, within
in each time, then it will be pointless. Due to this reason, I have selected
RUP methodology for this project because this methodology keeps user
requirements on mind while developing software and produce high
quality of software by fulfilling all the requirement of users, within a
predictable schedule. (ANWAR, 2014)
ii. In this academic project, the author has frequent meetings with
supervisors to show their project progress. Here, project progress may
be either project report or system development. After showing their
project progress, supervisors provide feedback to author. So, according
to the feedback of supervisors, author must make changes and that
changes need to be shown in next meeting for supervisors. So, here
iterative process is more important to refine the project. Thus, RUP
methodology follows iterative approach to address the problem in each
phase and can go back as many times as required to make changes to

Page | 9
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

refine and upgrade the software. Due to this reason, I have selected
RUP methodology for this project. (ANWAR, 2014)
iii. While developing this system, the code of one component may be same
for another component. So, if we write the same code for both
components twice then it may take our valuable time and more
resources. As we known that this academic project which is bounded by
time. So, time is more valuable for this project. Thus, in RUP
methodology, the code that has been developed for one component can
be used in another component which helps to save time and resources
while developing project. Due to this reason, I have selected RUP
methodology for this project. (ANWAR, 2014)
iv. Similarly, testing is more important for this project to control changes in
developing system. Thus, RUP methodology help to control software
changes because it contains continuous testing which means in each
phases of software development system testing will be carried out by
developers to detect the errors, to solve it and helps to control changes
in software. Due to this reason, I have selected RUP methodology for
this project. (ANWAR, 2014)
v. In this academic project, documentation also plays important role. So, in
RUP methodology, in each phases task of documentations are carried
out. Here, in inception phase, requirement gathering, project problem,
solution, vision document, initial use cases of system will be prepared.
Similarly, in elaboration phase use case diagram, wireframes, system
architecture diagram will be drawn. In construction phase, system build,
user manual, test cases will be prepared, and testing will be done. At
last, system deployment, system maintenance will be carried out and
finalized system documentation. Due to this reason, I have selected RUP
methodology for this project. (ANWAR, 2014)

Note: Furthermore, the detail description of RUP methodology is kept in

appendix section i.e. Selected Methodology.

Page | 10
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

2.3. Review of similar project

2.3.1. Similar Project
a) ParkKTM

Kathmandu Metropolitan City (KMC) has introduced a new mobile app

called “Park KTM” whose main aim is to provide Parking space for Two
Wheeler’s and Four Wheeler’s. (reviews.com.np, 2019) In this system, for
booking confirmation customer must call at parking location otherwise
booking will be cancelled after 15mins, if customer don’t reach at parking
location. Similarly, this system lacks the features like online payment,
parking policy, feedback and so on.

Figure 5: Similar System Park KTM (reviews.com.np, 2019)

Page | 11
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

b) Smart Parking

With the help of Smart Parking application customer can find nearer parking
location, can view parking location details, can book available space by
paying certain amount and can navigate to parking location. (SmartParking,
2020) This application lacks the features of parking policy. Parking policy is
important because it makes clear for customer regarding rules and
regulation of parking location.

Figure 6: Similar System i.e. Smart Parking (SmartParking, 2020)

Page | 12
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

c) Smart Parking

Smart Parking is an online on street parking application which is used in

Danang city. With the help of this application user can find parking location,
can make four-wheeler parking registration through online transaction. And
user can view his/her transaction history. (Smart Parking, 2017) This
application is based for four-wheeler i.e. car only so the application must be
developed for other vehicle by making parking space available to them as
well by adding features like two-wheeler booking, parking policy and so on.

Figure 7: Similar System i.e. Smart Parking (Smart Parking, 2017)

Page | 13
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

2.3.2. Comparison Between System

SN. Features Digital ParkKTM Smart Smart

Parking Parking Parking
[My
Project]
1. Login Available Not Available Available
Available
2. Register Available Not Available Available
Available
3. Display Parking Available Available Available Available
Location Details
4. Display Available Available Available Available Available
Parking Spaces
5. Online Parking Space Available Available Available Not
Booking for two- Available
wheeler
6. Online Parking Space Available Available Available Available
Booking for four-
wheeler
7. Add, View Parking Available Not Not Not
Policy Available Available Available
8. Navigate to Parking Available Not Available Available
Location Available
9. Online Payment Available Not Available Available
Available
10. Offline Payment Available Not Not Not
Available Available Available
11. Transaction History Available Not Available Available
Available
12. Feedback Available Not Not Not
Available Available Available

Page | 14
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

13. Phone Booking Not Available Not Not

Available Available Available
Table 1:Features comparison between similar system

Page | 15
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

3. Development to date
3.1. Requirement Gathering
The requirement of this project is gathered by conducting survey at parking location
and online survey with public using google form from November 3 to November 7,
2020. While conducting online survey with public, total 102 people had responded
in survey form whereas out of 10 selected parking location 7 parking location had
responded in survey form which was conducted at parking location. The detail
description of public and parking location survey is explained below:

3.1.1. Survey Conducted at Parking Location

The description of parking location survey has been kept in appendix section i.e.
Survey Conducted at Parking Location.

3.1.2. Conducted Online Survey with Public

The full description of online survey conducted with public has been kept in
appendix section i.e. Conducted Online Survey with Public.

Page | 16
NP01CP4A180002 | December 25, 2020
 CS6P05NI Final Year Project

3.2. Use Case

Figure 8: Overall System Use Case Diagram of Digital Parking Application

Page | 17
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

3.3. Designed Logo for Application

Figure 9: Logo of Digital Parking application

3.4. SRS Document

The full description of SRS document is kept in Appendix section i.e. SRS
Document.

3.5. High Level Use Case Diagram

The full description of High-Level Use Case Diagram is kept in Appendix
section i.e. High-Level Use Case Diagram.

3.6. Wireframes
The images of wireframes are kept in Appendix section i.e. Wireframes with
its full description.

Page | 18
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

3.7. ERD

Figure 10: Initial ERD of Digital Parking application

Note: Identification process of entities, Relation between entities are kept in

appendix section i.e. Entity Relationship Diagram with full description.

Page | 19
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

3.8. System Architecture Diagram

Figure 11: System Architecture Diagram

When a user submits data or information through API, here, Django serializers takes
data, validate it, convert it into Django Model instance and save it into database.
(Mays, 2018) Similarly, when user access data or information through API, then the
relevant instances are fed into serializers, which parses them into a JSON format. So
that user can easily access it. (Mays, 2018)

Page | 20
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

3.9. Database Migration

Figure 12: Created database and tables

Page | 21
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

3.10. Developed features in Android

3.10.1. Display parking location in Google Map with Markers

Figure 13: Parking location displayed in google map with markers

Page | 22
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

3.10.2. Navigate to parking location using Google Map

Figure 14: Navigate to parking location using google map

Page | 23
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

3.10.3. Login Screen

Figure 15: Login screen for staff and normal user

Page | 24
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

3.10.4. User Register Screen

Figure 16: Normal user (General Public) registration screen

Page | 25
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

3.10.5. User Feedback Screen

Figure 17: User Feedback Screen

Page | 26
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

3.11. Developed features in Web Application

3.11.1. Manage Parking Location

Figure 18: Manage Parking Location Page

3.11.2. Update Parking Location Page

Figure 19: Update Parking Location Page

Page | 27
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

3.11.3. Staff Registration Page

Figure 20: New staff registration page

3.11.4. Manage Staff Page

Figure 21: Listed all registered staff at parking location

Page | 28
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

3.11.5. Staff Personal Detail

Figure 22: Display staff personal details according to staff id

3.11.6. Staff Contract Detail Page

Figure 23: Display staff contract according to staff id

Page | 29
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

3.11.7. Staff Account Detail Page

Figure 24: Display staff account details according to staff id

3.11.8. Update Individual Staff Personal Detail Page

Figure 25: Update staff personal details according to staff id

Page | 30
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

3.11.9. Update Staff Contract Page

Figure 26: Update staff contract according to staff id

3.11.10. User’s Feedback Page

Figure 27: Display all user feedback

Page | 31
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

4. Analysis of progress
Analysis of progress sections includes the progress of final year project and
how it is developing? This section helps to determine the actual progress of
project by comparing with Gantt Chart.

4.1. Progress Table

SN Tasks Status Progress (%)
1. Topic Selection Completed 100%
2. Feasibility Study Completed 100%
3. Scheduling Resources Completed 100%
4. Cost and time estimation Completed 100%
5. Research on similar projects Completed 100%
6. Finalize Proposal Completed 100%
7. Conduct Public Survey Completed 100%
8. Conduct Survey at Parking Completed 100%
Location
9. Design Logo for the project Completed 100%
10. Develop Overall System Use Completed 100%
Case Diagram
12. Develop SRS Document Completed 100%
13. Develop High Level Use Case Completed 100%
Diagram
14. Develop Wireframes Completed 100%
15. Finalized Initial ERD Completed 100%
16. Develop System Architecture Completed 100%
Diagram
17. Develop Admin Panel in Web Partially Completed 10%
Application
18. Develop Android Application for Partially Completed 10%
Customer and Staff
19. Finalize Interim Report Completed 100%
20. Develop System Operation Not Completed 0%
Manual

Page | 32
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

21. Prepared Test Cases and Not Completed 0%

Testing
22. Application Deployment Not Completed 0%
23. Finalize FYP Report Not Completed 0%
24. Review and Refinement Not Completed 0%
25. Submit Final Report to RTE Not Completed 0%
Table 2: Progress table of Project according to Gantt Chart

Page | 33
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

4.2. Progress Review

In initial phase, topic was selected for the final year project and feasibility study
was carried out for making sure if the topic is viable or not. To gather the project
requirements two survey was conducted i.e. Public Survey and Survey at Parking
Location.

Public survey was conducted through online google form to know the actual
problem they have been faced before and after parking their vehicle either at on
street or off street. Similarly, survey was done as parking location to identity the
problems that they have been faced at their parking location. Based on the
requirement cost and estimation was done. In addition to that, research was done
on similar project to identify the features what they have included, what they have
not and what are their major issues.

Public and parking location survey and research on similar project helps me a lot
to identify the features for the current project. After identifying all the actors,
features of the project, use case was drawn, project logo was designed, and SRS
document was started. After getting feedback of use case from project supervisor,
High Level Use Case and Wireframes was drawn. Similarly, after getting feedback
of Wireframes and High-Level Use Case diagram, project UI development was
started and initial ERD was designed.

By the end of 2020, in web and application development features like customer,
staff registration, login, feedback, manage parking location and manage staff will
be completed.

4.3. Progress Timeline

The works of the project has been carried out on time according to the Gantt Chart
which was submitted in the proposal.

4.4. Action Plan

New Gantt Chart will be made because, in old Gantt Chart which was submitted to
proposal had mistaken in date. The tasks of the project will be carried out according
to the revised Gantt chart made for the interim report. Multiple tasks such as
reporting, development, testing and project refinement will be carried out as per
feedback of supervisors simultaneously to keep project in track as it is.

Page | 34
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

5. Future work
Future work includes the remaining task of project that is to be done in future within
a time estimated in Gantt Chart. According to the Gantt chart, following tasks were
remaining to complete which are listed below:

a) Develop Admin Panel in web application.

 From admin panel, admin can manage parking location, manage parking staff,
can track current total transaction and can view users’ feedback.
b) Develop Android Application for customer and staff.
 In android application, if user is customer (people) s/he can navigate to parking
location through google map, can book vehicle parking slot, make online
transaction and so on.
 Similarly, if user is staff then s/he can view current total transaction, can make
offline vehicle slot booking for customer, offline payment and so on.
c) Develop System Operational Manual.
 In developed system operational manual, it included contents like how to make
online and offline payment? how to book online vehicle parking slot? And so
on.
d) Prepared test cases and testing.
 Test cases are prepared for system testing to check whether the developed
system contains any error or not. If error, bug was found while testing then that
system bug, error will solve by developers to make developed system free from
errors.
e) FYP report finalization.
 FYP report finalization will be done according to the Gantt Chart. While
finalizing the FYP report, Use Case diagram, ERD, System architecture
diagram, sequence diagram, test cases etc. will be finalized.
f) Review and refinement of project report.
 As per supervisors’ feedback, the changes will be done in FYP report to refine
it and to make well formatted documentation.
g) Submit Final Year Project report to RTE.
 In the given deadline, here, the Final Year Project will be submitted in RTE
classroom i.e. Project which included files like final documentation report in pdf
format and folder like Project folder, Development folder. In project folder,

Page | 35
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

evidence of project is kept which may include screenshots of stack overflow,

journal articles and so on. Similarly, in development folder it included the
development of code of android and web application.

Page | 36
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

6. References
a., 2012. have dreams and make it happen. [Online]
Available at: https://theexplorationofmyworlds.wordpress.com/2012/07/02/rup-
rational-unified-process/
[Accessed 18 Dec 2020].

a., 2013. slideshare. [Online]

Available at: https://www.slideshare.net/anuragmbst/unit2-18477505
[Accessed 18 Dec 2020].

ANWAR, P. A., 2014. A Review of RUP (Rational Unified Process).

International Journal of Software Engineering (IJSE), 5(2), pp. 8-24.

Associates, B. &., 2003. AN OVERVIEW OF COMMON PARKING ISSUES,

PARKING MANAGEMENT OPTIONS, AND CREATIVE SOLUTIONS, s.l.: s.n.

Babu, A., 2018. {coding}Sight. [Online]

Available at: https://codingsight.com/structured-query-language-importance-of-
learning-
sql/#:~:text=SQL%20is%20an%20exceptional%20reason,data%20fields%20i
n%20their%20tables.
[Accessed 20 Dec 2020].

Buckett, C., 2013. Dart IN ACTION. 1st ed. s.l.:Manning Publications Co..

Chauhan, A., 2019. Appventurez. [Online]

Available at: https://www.appventurez.com/blog/why-choose-agile-app-
development-method/
[Accessed 18 Dec 2020].

Dart, 2020. Dart. [Online]

Available at: https://dart.dev/
[Accessed 20 Dec 2020].

Django REST framework, 2020. Django REST framework. [Online]

Available at: https://www.django-rest-framework.org/
[Accessed 20 Dec 2020].

Page | 37
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

django, 2005 - 2020. django. [Online]

Available at: https://www.djangoproject.com/
[Accessed 20 Dec 2020].

Flutter, 2020. Flutter. [Online]

Available at: https://flutter.dev/
[Accessed 20 Dec 2020].

Javed, M. et al., 2012. RUP Certification via CRM Certification Process:

Development of Software with Zero Defect Rate. International Journal of
Advanced Science and Technology, Nov, Volume 48, pp. 1-10.

J. & W., 2019. Medium. [Online]

Available at: https://medium.com/@joneswaddell/the-cascading-costs-of-
waterfall-5c3b1b8beaec
[Accessed 18 Dec 2020].

MacIsaac, B. & Kroll, P., 2006. informIT. [Online]

Available at:
https://www.informit.com/articles/article.aspx?p=473452&seqNum=5
[Accessed 23 Dec 2020].

MAPQUEST, INC, 2018. MAOQUEST Developer. [Online]

Available at: https://developer.mapquest.com/documentation/geocoding-
api/#:~:text=Whether%20you%20want%20to%20show,longitude%20with%20
an%20associated%20address.
[Accessed 20 Dec 2020].

Mays, C., 2018. Basics of Django Rest Framework. [Online]

Available at: https://www.caktusgroup.com/blog/2018/02/26/basics-django-
rest-
framework/#:~:text=When%20a%20user%20submits%20information,slot%20i
nto%20a%20Model%20instance.&text=Setting%20fields%20allows%20you%
20to,are%20accessible%20using%20this%20serializer.
[Accessed 24 Dec 2020].

Page | 38
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

ProjectManager.com, Inc., 2020. PROJECTMANAGER. [Online]

Available at: https://www.projectmanager.com/waterfall-methodology
[Accessed 22 Dec 2020].

Refsnes Data, 2020. w3schools. [Online]

Available at: https://www.w3schools.com/python/python_intro.asp
[Accessed 20 Dec 2020].

reviews.com.np, 2019. Reviews The Best Guide. [Online]

Available at: https://reviews.com.np/article/park-ktm-app-going-live-on-tuesday
[Accessed 23 Dec 2020].

Rigby, D. K., Sutherland, J. & Takeuchi, H., 2016. Harvard Business Review.
[Online]
Available at: https://hbr.org/2016/05/embracing-agile
[Accessed 22 Dec 2020].

Rouse, M., 2019. SearchSoftwareQuality. [Online]

Available at: https://searchsoftwarequality.techtarget.com/definition/waterfall-
model
[Accessed 22 Dec 2020].

Sewell, E., 2017. TECHCRATES. [Online]

Available at: https://www.techcrates.com/mobile-technology-and-its-effects-on-
human-life/
[Accessed 20 Dec 2020].

Smart Parking, 2017. Smart Parking. [Online]

Available at: https://www.doxedanang.com/help
[Accessed 18 Dec 2020].

SmartParking, 2020. SmartParking. [Online]

Available at: https://www.smartparking.com/

[Accessed 18 Dec 2020].

Techopedia Inc., 2011. techopedia. [Online]

Available at: https://www.techopedia.com/definition/3885/unified-process-up
[Accessed 23 Dec 2020].

Page | 39
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

Wessel, P., 2016. Parksmart. [Online]

Available at: https://parksmart.gbci.org/what-smart-parking
[Accessed 20 Dec 2020].

Page | 40
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7. Appendix
7.1. SRS Document
7.1.1. Project Title: Digital Parking
7.1.2. Category: Web and Android application
(Note: Web Application for Admin Panel and Android application for all users)

7.1.3. Introduction
7.1.3.1. Purpose:
Software Requirements Specification (SRS) document is developed in order to
provide the detail information about system functionalities and non-functionalities.
This document defines the required features for android and web application. This
document also shows the detail information about hardware, software and other
technical dependencies.

7.1.3.2. Intended Audiences and Reading Suggestions:

This document is developed for the system developers in order to develop android
and web applications which helps people to book vehicle parking lot through online,
parking owner to track daily transaction and available and booked parking lot. The
end user for this android application will be general public (people) and staff of
parking location. Similarly, the end user for the web application will be parking
owner (admin). This document will be blueprint for the developers to develop the
system i.e. Digital Parking. Thus, this document can be used by users in order
gain knowledge about the features that are required in android and web
application.

7.1.3.3. Project Scope:

The android and web application are being developed for a particular parking
location in order to resolve the parking problems faced by people, staff and parking
owners like difficult to find parking location to park vehicle (by people), confusion
in parking policies (by people and staff), difficult to track total fund raised from
parking location (by parking owner) etc. The features that are required for android
application are listed below:

a) Online and offline parking lot booking.

b) Online and offline payment.

Page | 41
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

c) Booked Parking Slot and transaction history.

d) Send feedback regarding parking location issues.
e) Add parking policy.

Similarly, the features that are required for web application are listed below:

a) Add, update and terminate staff.

b) Update parking location details.
c) Receive feedback.
d) View transaction history.
e) Track available and booked parking slot.

7.1.3.4. Existing System

The present system is a manual system which involves a paperwork in the form of
maintaining daily transaction in parking location. Maintaining daily transaction in a
file is time consuming and cost expensive process. A manual system has following
disadvantages which are listed below:

a) It is limited system and not user friendly.

b) Managing transaction in a file is a time-consuming process.
c) The existing system needs to save information of parked vehicle in the form of
token.
d) The manual system gives us less security for saving data, some data may be
lost due to mismanagement.
e) In the existing system people need to find parking location own self to park their
vehicle which is time consuming and frustrating process.
f) If vehicle owner lost the token given from parking location, then s/he may have
to pay full charge before leaving parking location.

Page | 42
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.1.3.5. Proposed System

The main aim of proposed system is to replace the existing system of parking
location by developing user friendly android application for people and staff and
web application for parking owner. There are many advantages of Digital Parking
to the people, as well as staff and the associated parking location owner which are
listed below:

Advantages for People:

a) People can see available parking lot.

b) People can book vehicle parking slot before they reach to their destination
which saves their time.
c) People can read parking location policies.
d) People can send feedback directly to parking owner regarding the issue of
parking location, application and so on.
e) People can navigate to parking location with the help of this application.
f) People can pay charge of parking cost through online and able to track their
transaction history.

Advantage for Staff:

a) Misunderstanding between staff and parking owner will not occur time and
again because daily transaction will be calculated by system automatically.
b) Staff can update parking location policies.

Advantage for Parking owner (Admin):

a) Daily transaction will be calculated by system automatically. So that actual daily

transaction of parking location can be tracked.
b) Staff records are maintained systematically. As per required new staff can be
added and staff record can be updated.
c) Location details are maintained systematically. As per required parking location
details can be updated.
d) Receive feedback from people regarding parking location.
e) Available and booked parking slot can be tracked through application.

Page | 43
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.1.4. Overall Description

7.1.4.1. System Perspective

Figure 28: System Perspective of Android and Web Application

Page | 44
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

7.1.4.2. System Features

Some of the features that should be included in web application are listed below:

7.1.4.2.1. Register Staff

The web application will facilitate admin user to register, update and terminate staff
as per required.

7.1.4.2.2. Register Location

The web application will facilitate admin user to register, update the parking
location details which also included the total number of parking slot to park vehicle.

7.1.4.2.3. Online Vehicle Parking Lot Booking

Android application will facilitate normal user (general public) to book available
vehicle parking slot according to their vehicle i.e. Two-Wheeler (Bike), Four-
Wheeler (Car).

7.1.4.2.4. Offline Vehicle Parking Lot Booking

Android application will facilitate staff user to make available vehicle parking slot to
book parking lot for normal users, according to their vehicle i.e. Two-Wheeler
(Bike), Four-Wheeler (Car).

7.1.4.2.5. Online Payment

Online Payment will be available for normal user to pay their total charges of
vehicle parked at parking location.

7.1.4.2.6. Offline Payment

Offline Payment will be available for staff user. General public will pay the total
charge of vehicle parked at parking location to the staff of parking location. The
staff of parking location will record it through this application.

7.1.4.2.7. Parking Policy

Parking Policy will be available for both normal (General Public) and staff users.
Staff user will facilitate to add, update policy as per required. Similarly, normal user
will facilitate to view the parking policy.

Page | 45
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

7.1.4.2.8. Transaction History

Transaction History will be facilitated for all users (normal, staff and admin) who
are registered in this application. All users will be facilitated to filter their transaction
history.

7.1.4.2.9. Feedback

Normal users of this android application will be facilitated to send their feedback to
the admin user so that necessary changes can be carried out in application.

Page | 46
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

7.1.4.3. User class and characteristics

Digital Parking application will be used by three users i.e. Normal User (General
Public), Staff and Admin (Owner of parking location). According to the users their
roles are listed below:

UC1: Normal User (General Public)

UC1.1

Can view parking location details

UC1.2

Can navigate to parking location using google map

UC1.3

Book available parking lot according to their vehicle

UC1.4

Online payment can be done through dummy ESewa Id

UC1.5

Send feedback for further improvement

UC1.6

Able to read parking policy

Page | 47
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

UC2: Staff

UC2.1

Manage transaction history

UC2.2

Manage offline and online vehicle parking lot booking

UC2.3

Manage offline and online payment of booked parking lot

UC2.4

Add and update parking policy according to requirement

UC3: Admin (Owner of Parking Location)

UC3.1

Add details of parking location and update it according to requirement

UC3.2

Can appoint, update and terminate staff according to requirement

UC3.3

Can review users’ feedback

UC3.4

Manage Transaction

Page | 48
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

7.1.4.4. Operating Environment

OE1: In the present context, Digital Parking application is focused on Android
platform from normal users (general public) and staff and focused on Web platform
for admin only. Further planning is to make this application run on different platform
like IOS and Web for all users.

OE2: Digital Parking application operates in android devices having android

version minimum 5.1.

7.1.4.5. Assumption and Dependencies

AS1: The main targeted audience of this application is general public and parking
location owners.

AS2: Developed application will be an online application.

AS3: Documents and report of this system can be accessible by developer and the
researcher who are interested to develop this kind of system with new features.

Page | 49
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

7.1.4.6. Functional Requirements

7.1.4.6.1. Register People

Req. ID Requirement Description

FR.01 General public can register in this application.
Sys. Req. System Requirement
ID
SR.01 User (People) can view register form.
SR.02 The system shall check whether the
compulsory area is entered or not.
SR.03 The system shall check whether provided
information is valid or not.
SR.04 The system shall check user entered email is
unique to this application or not.
SR.05 The system shall display message whether
the user registration is successful or not.
Table 3: Functional requirement description of register people

Page | 50
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

7.1.4.6.2. Login (People / Staff)

Req. ID Requirement Description
FR.02 Registered people and parking location staff should login to use
the features of this application like online vehicle parking lot
booking, view transaction history and so on.
Sys. Req. System Requirement
ID
SR.06 User (People and Staff) can view login form.
SR.07 The system shall check whether the
compulsory area is entered or not.
SR.08 The system shall control username and
password in secure way.
SR.09 The system shall check user entered email and
password is valid or not.
SR.10 The system shall display message if user login
is unsuccessful.
SR.11 If user entered email and password is valid
then verify user type i.e. people or staff from
user email.
SR.12 If user type is people, then the system shall
display people dashboard otherwise staff
dashboard should be display.
Table 4: Functional requirement description of login

Page | 51
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

7.1.4.6.3. Online Vehicle Parking Slot Booking

Req. ID Requirement Description

FR.03 Registered user i.e. people can book vehicle parking slot only
after login.
Sys. Req. System Requirement
ID
SR.13 The system shall display the parking location
information with available parking slot.
SR.14 The system shall display two-wheeler and four-
wheeler button to book the available parking
slot.
SR.15 When user click on two or four-wheeler button
then the system shall display the available
parking slot with two buttons i.e. Add to Book
and Book Now.
SR.16 If user click on button Add to Book, then the
system shall ask user to choose to start and
end time for parking. After that system should
display carted parking slot with Book Now
button.
SR.17 If user click on Book Now button, then the
system shall display booking confirmation
message. If user confirmed booking then the
system shall display total booked parking slot,
time and total amount and ask user to enter
their transaction id i.e. dummy eSewa id and
parking total amount.
SR.18 The system shall display the information
regarding whether the vehicle parking slot is
booked or not.
Table 5: Functional requirement description of online vehicle parking slot booking

Page | 52
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.1.4.6.4. Profile

Req. ID Requirement Description

FR.04 All the registered users can view their own profile.
Sys. Req. System Requirement
ID
SR.19 When user click on profile button then the
system shall display their profile details
according to their email.
SR.20 While displaying personal information, the
system shall display change password button
option as well.
SR.21 If user click on change password button, then
the system should display reset form.
SR.22 The system shall check the compulsory area
whether the user had entered or not.
SR.23 The system shall check whether the user
entered old password, new and confirmed
password is valid or not.
SR.24 If user account password was changed
successfully then display password changed
message otherwise display error message.
Table 6: Functional requirement description of user's profile

Page | 53
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.1.4.6.5. Payment History

Req. ID Requirement Description

FR.05 According to user id, user can view their own payment history.
Sys. Req. System Requirement
ID
SR.25 When user click on payment history then the
system shall display user’s current transaction
on weekly basis on charts with filter by date
option.
SR.26 If use click on filter by date button, then the
system shall ask user to choose the date.
SR.27 The system shall check whether the user
chosen date is valid or not.
SR.28 If user chosen date is valid then, display on
charts otherwise display error message.
Table 7: Functional requirement description of payment history

Page | 54
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.1.4.6.6. Feedback Option

Req. ID Requirement Description

FR.06 Only registered user, user type people can send feedback.
Sys. Req. System Requirement
ID
SR.29 User can send feedback by clicking on
feedback button.
SR.30 When user click on feedback button, the
system shall ask user to enter subject and
description with send button option.
SR.31 When user click on send button then the
system shall check whether the subject and
description field are filled or not.
SR.32 If users’ feedback was sent successfully then
the system shall inform user by showing
message otherwise display error message.
Table 8: Functional requirement description of feedback option

Page | 55
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.1.4.6.7. Parking Policy

Req. ID Requirement Description

FR.07 User type staff can add, edit, delete and updated parking policy
whereas user type people can only view parking policy.
Sys. Req. System Requirement
ID
SR.33 When user click on add parking policy button,
the system shall check whether the parking
policy file is already updated or not. If not then,
the system shall ask user i.e. staff to upload
parking policy pdf file.
SR.34 The system shall check whether the file has
been uploaded or not.
SR.35 If not, then the system shall display error
message otherwise the system shall check
the user uploaded file extension.
SR.36 If user uploaded file extension is valid then the
system shall display upload successful
message otherwise error message should be
displayed.
Table 9: Functional requirement description of parking policy

Page | 56
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.1.4.6.8. Offline Vehicle Parking Slot Booking

Req. ID Requirement Description

FR.08 Registered user i.e. staff can book offline vehicle parking slot
for vehicle owner only after login.
Sys. Req. System Requirement
ID
SR.37 When user click on offline booking button then
the system shall display the parking location
information with available parking slot.
SR.38 The system shall display two-wheeler and four-
wheeler button to book the available parking
slot.
SR.39 When user click on two or four-wheeler button
then the system shall display the available
parking slot with button Book Now.
SR.40 If user click on button Book Now, then the
system shall ask user to enter vehicle number
and choose start time for parking.
SR.41 The system shall check whether the user
entered vehicle number and time is already
registered or not on that date.
SR.42 The system shall display the information
regarding whether the vehicle parking slot is
booked or not.
Table 10: Functional requirement description of offline vehicle parking slot booking

Page | 57
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.1.4.6.9. Offline Payment

Req. ID Requirement Description

FR.09 Offline payment will be done by general public to parking
location staff. (General public who had booked their vehicle
parking slot directly by reaching to the parking location.)
Sys. Req. System Requirement
ID
SR.43 The system shall ask user to enter vehicle
number.
SR.44 The system shall check vehicle number is valid
or not. If valid then the system shall display
information like vehicle entry time, parking start
time, and total cost till current date and time
and display pay now button otherwise system
shall ask user to re-enter vehicle number.
SR.45 When general public give their parking cost
and the parking location staff click on pay now
button then the system shall display paid
confirmation message and that parking slot
should be available for online and offline
booking.
Table 11: Functional requirement description of offline payment

Page | 58
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.1.4.6.10. Transaction History (For Staff)

Req. ID Requirement Description

FR.10 Only the registered staff can view only current transaction of
parking location.
Sys. Req. System Requirement
ID
SR.46 When user click on transaction history then
the system shall display only current date
transaction of booked parking slot with filter
option i.e. vehicle number or by email.
SR.47 If use click on filter by vehicle number, then
the system shall ask user to enter vehicle
number otherwise ask user to enter email.
SR.48 The system shall check whether the user had
filled all required field or not.
SR.49 If user had filled all required field, then the
system shall display only current transaction
of that registered email or vehicle number
otherwise system shall display error message.
Table 12: Functional requirement description of transaction history of staff user

Page | 59
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.1.4.6.11. Register Staff

Req. ID Requirement Description

FR.11 Only admin (parking location owner) can register and update
staff information in this application.
Sys. Req. System Requirement
ID
SR.50 User (Admin) can view register form.
SR.51 The system shall check whether the
compulsory area is entered or not.
SR.52 The system shall check user entered email is
unique to this application or not.
SR.53 The system shall check whether the user
chosen staff contract date and termination
date has 90 days difference or not.
SR.54 The system shall display message whether
the user i.e. staff registration is successful or
not.
Table 13: Functional requirement description of staff registration

Page | 60
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.1.4.6.12. Deregister Staff

Req. ID Requirement Description

FR.12 Only admin (parking location owner) can deregister staff.
Sys. Req. System Requirement
ID
SR.55 When user click on deregister staff button
then the system shall display register form.
SR.56 The system shall check whether the
compulsory area is entered or not.
SR.57 If the compulsory area is filled, then the
system shall display deregister confirmation
dialogue.
SR.58 If user confirmed the staff deregistration, then
the system shall remove all his/her permission
and change his/her user type from staff to
people.
Table 14: Functional requirement description of staff deregistration

Page | 61
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.1.4.6.13. Register Location

Req. ID Requirement Description

FR.13 Only admin (parking location owner) can add, update and
remove parking location information.
Sys. Req. System Requirement
ID
SR.59 When user click on add new location button,
the system shall display location form.
SR.60 The system shall check whether the
compulsory area is entered or not.
SR.61 The system shall check user entered location
name, latitude and longitude is unique or not.
SR.62 If not unique then the system shall display
error message otherwise location registered
message.
Table 15: Functional requirement description of register location

7.1.4.6.14. Receive Feedback

Req. ID Requirement Description

FR.14 Only admin (parking location owner) can view general public
feedback.
Sys. Req. System Requirement
ID
SR.63 When user click on user’s feedback button,
the system shall display current feedback with
filter by date button.
SR.64 If user click on filter by date button, the system
shall ask user to select date.
SR.65 The system shall check whether the user
chosen date is valid or not. If not valid then
display error message otherwise display the
feedback of that day (user selected date).
Table 16: Functional requirement description of feedback receive

Page | 62
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.1.4.6.15. Transaction History (For Admin)

Req. ID Requirement Description

FR.15 Only admin can view all transaction of parking location.
Sys. Req. System Requirement
ID
SR.66 When user click on transaction history then
the system shall display only current week
daily transaction of booked parking slot in the
form of chart with filter option.
SR.67 If user click on filter option, then the system
shall ask user to select date and year.
SR.68 The system shall check whether the user
entered date and year is valid or not.
SR.69 If user had entered valid date and year, then
the system shall display all transaction of that
date, month or year otherwise the system
shall display error message.
Table 17: Functional requirement description of transaction history of admin user

Page | 63
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.1.4.7. External Interfaces Requirements

7.1.4.7.1. User Interface

Figure 29: Login Screen

The User Interface (UI) of android and web application will be developed in a user-
friendly manner. So that user won’t be confused regarding pages, which they want
to go with. According to the functionality of each pages, there will be proper color
combination and its (pages) name will be declared. Similarly, in case if it required,
according to pages, images will be kept in application to provide the meaningful
information to the end users.

7.1.4.7.2. Hardware

This application has been developed for general public, for parking location owners
and their staff. So general public (normal), parking location staff must have their
own android phone and parking owner must have laptop or desktop computer with
internet connection to run this application. Thus, for this project no extra hardware
device are required.

7.1.4.7.3. Software

Standard resources will be used to develop and maintain database of Digital

Parking application. For developing the android application, Android Studio is
required, for developing the web application of admin users only, PyCharm is
required for coding. Similarly, MySQL database is used in to store the data and
information of users that are required for application.

Page | 64
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.1.4.7.4. Other Non-Functional Requirements

7.1.4.7.4.1. Performance Requirements

Req.ID Requirement Description Priority

PR.01 It should take only 5 second to launch the android Could
application.
PR.02 The application should display login page at first to Should
user, if user is not logged in.
PR.03 The application will display the dashboard of users Should
after successfully login.
PR.04 For the users, all the features of android and web Should
application will be functional.
Table 18: Non-functional requirement description of performance requirements

7.1.4.7.4.2. Safety Requirements

Req.ID Requirement Description Priority

SR.01 Application will take permission from users, if it Should
requires to access camera, location and other
personal data of users.
SR.02 The application should not display any Should
advertisement.
SR.03 Without providing any information to the users, in the Should
background of application, spyware or malware
should not be installed.
SR.04 Application shall be made free from any attacks. Could
Table 19: Safety requirement, non-functional requirement description

Page | 65
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.1.4.7.4.3. Other Software Quality Attributes

Req.ID Requirement Description Priority

SQA.01 Requirements determined for this project should be Should
implemented.
SQA.02 The application should behave same in various Should
android version.
SQA.03 The application should be responsive and easy to Should
operate.
SQA.04 Modern UI, new features could be added in the Could
updated application according to the users (general
public) feedback.
Table 20: Other software quality attributes, non-functional requirement description

Page | 66
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.2. High Level Use Case Diagram

7.2.1. Actors of Digital Parking Application
Actors: User (People), Staff and Admin
Table 21: Identification of actors

7.2.2. Register People

Name: Register People
Actors: User (People)
Description: General public will enroll in this application by filling enrollment
form. So that enrolled people can use the features of Digital Parking
application.
Table 22: High level use case description of register people

7.2.3. Login
Name: Login
Actors: User (People), Staff and Admin
Description: Before using the features of Digital Parking application, first
user should login into system using their email and password.
Table 23: High level use case description of login

7.2.4. View Profile

Name: View Profile
Actors: User (People), Staff and Admin
Description: After login to the Digital Parking application users i.e. People,
Staff and Admin can view their personal information like username, name,
email and so on.
Table 24: High level use case description to view profile

7.2.5. Online Parking Slot Booking

Name: Online Parking Slot Booking
Actors: User (People)
Description: After login to the Digital Parking application, people can view
the available parking slot and book it according to their vehicle type i.e. two
or four-wheeler.
Table 25: High level use case description of online parking slot booking

Page | 67
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.2.6. View Booked Parking Slot

Name: View Booked Parking Slot
Actors: User (People)
Description: People can view their booked parking slot only after login into
the system. While viewing the booked parking slot it provides the information
like date, time, parking selected time, total amount and so on.
Table 26: High level use case description of view booked parking slot

7.2.7. Make Payment

Name: Make Payment
Actors: User (People)
Description: Only after login to the system, user (People) can pay the total
amount of online booking by using their eSewa id.
Table 27: High level use case description of make payment

7.2.8. Payment History

Name: Payment History
Actors: User (People)
Description: User must login into the system to view the payment history.
Payment history included the information like date, time, total amount, eSewa
Id, parking slot etc.
Table 28: High level use case description of payment history

7.2.9. Send Feedback

Name: Send Feedback
Actors: User (People)
Description: User must login into the system to send feedback. User can
send feedback directly to admin reading the issue of parking location and
their application.
Table 29: High level use case description of send feedback

Page | 68
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.2.10. Parking Policy

Name: Parking Policy
Actors: User (People), Staff
Description: Both users must login into the system. Staff can add and update
parking policy as per requirement. Similarly, user (People) can view/ read the
parking policy.
Table 30: High level use case description of parking policy

7.2.11. Offline Parking Slot Booking

Name: Offline Parking Slot Booking
Actors: Staff
Description: Staff makes offline booking of general public who don’t use the
Digital Parking application by inserting vehicle no. and entry time.
Table 31: High level use case description of offline parking slot booking

7.2.12. Offline Payment

Name: Offline Payment
Actors: Staff
Description: Staff ask total charges of parked vehicle by inserting exit time
to general public who had parked their vehicle through offline booking.
Vehicle owner will pay the total charges to the staff of parking location before
leaving the parking location.
Table 32: High level use case description of offline payment

7.2.13. History
Name: History
Actors: Admin
Description: Admin can view the total transaction according to the date and
time. To view these histories, admin must login into the system.
Table 33: High level use case description of history

Page | 69
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.2.14. Check Booked Parking Slot

Name: Check Booked Parking Slot
Actors: Admin
Description: Admin can view the total booked slot of parking location
according to the date and time by logging to the system.
Table 34: High level use case description of check booked parking slot

7.2.15. Register Staff

Name: Register Staff
Actors: Admin
Description: To enroll the new staff, at first, admin should login into the
system using their email and password.
Table 35: High level use case description of register staff

7.2.16. Deregister Staff

Name: Deregister Staff
Actors: Admin
Description: Admin can terminate the staff as per requirement. To terminate
the staff, admin must login to the system.
Table 36: High level use case description of staff deregistration

7.2.17. View Staff

Name: View Staff
Actors: Admin
Description: Admin can view the details of all staff who has been registered
in this application. Admin can view staff information like termination date,
appointed date, phone no, email and so on. But staff login password will be
hidden to the admin.
Table 37: High level use case description to view staff details

Page | 70
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.2.18. Register Location

Name: Register Location
Actors: Admin
Description: Admin login into the system and fill up the location form which
included location name, latitude, longitude, total parking slot and so on to
register the parking location.
Table 38: High level use case description to register location

7.2.19. Deregister Location

Name: Deregister Location
Actors: Admin
Description: To deregister the location, first admin should login into the
system. If location is deregistered, then parking location information will be
hidden to the general public. Similarly, the functionality like online booking,
online payment of user (People) will be disabled.
Table 39: High level use case description to deregister location

7.2.20. View Location

Name: View Location
Actors: Admin
Description: Admin login into the system to view the location details.
Similarly, if any information of parking location needs to be updated then
admin can make changes.
Table 40: High level use case description to view location details

7.2.21. View Feedback

Name: View Feedback
Actors: Admin
Description: Admin can view all the feedback of user according to the date
and time by logging into the system. If necessary, changes is required in
application or in parking location according to the users feedback, then admin
will make it.
Table 41: High level use case description to view user's feedback

Page | 71
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3. Wireframes
7.3.1. Common Wireframe of Android End User: Customer and Staff
7.3.1.1. Login Screen
This is the login screen for android end users i.e. Customer and Staff. From this
screen user enter their registered account email and password to use the features
of Digital Parking application. If user entered email and password is valid then
system checks whether that user is staff or customer. If user is customer then it will
display customer dashboard otherwise staff dashboard. Similarly, in this screen
there is a Create New Account button. This button will be used by those people
who don’t have their account in this application. Thus, this button is which navigate
to register screen.

Figure 30: Wireframe of login screen

Page | 72
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.2. Wireframes of Android End User: Customer

Note: Most of the screen have drawer, which have common buttons. So, drawer
description is done here.When user click on drawer button, then it displays
application logo with Profile, Booking History, Feedback, ESewa and Logout
button. If user want to view their profile then user click on Profile button which
display profile screen, if user want view booked parking slot then there is a button
i.e. Booking History which display booking history screen. Similarly, if user want to
send feedback to the parking there is a button of Feedback button which display
feedback screen. If users want online transaction, the user add their esewa id from
esewa screen which will display by pressing Add Esewa Id button. When user add
their esewa id then esewa id button will be replaced by payment or transaction
history button, from where user can view their transaction details. Thus, if user
press on home button it will display dashboard and if user want to logout from
system, then s/he can press logout button.

Figure 31: Wireframe of drawer of customer

Page | 73
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.2.1. Register Screen

This is the register screen for general public. If general public (any customer) want
to use the features of Digital Parking application, then at first, user must be
registered in this application by filling the given form. If customer is already
registered in this application the, s/he can go to login screen by pressing Already
Have Account button.

Figure 32: Wireframe of register screen for customer

Page | 74
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.2.2. Customer Dashboard Screen

In Customer Dashboard Screen, it displays the markers of parking location in
google map. When user click on markers, then it will display the location name with
its address and display the button of map and direction. If user want to navigate to
parking location through google map, then s/he can press on map button. Similarly,
if user click on marker location name then it will navigate to parking details screen.
Additionally, this dashboard contains drawer button.

Figure 33: Wireframe of Customer Dahsboard

Page | 75
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.2.3. Location Detail Screen (Details Tab Bar)

This screen contains tab bar i.e. Details and Parking Slot. By, default when user
enter to this screen detail of parking location will be displayed which included
location name, opening hour, closing hour and so on. Detail description of drawer
are already mentioned in note.

Figure 34: Wireframe of location details screen (selected tab bar i.e. Details)

Page | 76
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.2.4. Location Detail Screen (Parking Slot Tab Bar)

If parking slot tab bar is selected then, it will display the latest information of booked
and available parking slot of parking location. According to the user vehicle type,
s/he can press button either two or four-wheeler button, it will display the available
parking slot for book.

Figure 35: Wireframe of location detail screen (selected tab bar i.e. Parking Slot)

Page | 77
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.2.5. Two-Wheeler/ Four-Wheeler Available Parking Slot Screen

If user had pressed two-wheeler button, then it displays the available parking slot
of two-wheeler otherwise it displays the available parking slot of four-wheeler. User
can book multiple parking available slot, but at a time s/he can book only one
parking slot. When user press on book now button then it displays alert dialogue
screen. The first alert dialogue screen ask user to input their vehicle park time,
second dialogue screen ask user to input park end time, then after that it display
the dialogue to pay booking amount. If user had paid their amount, then booking
confirmation message will be displayed.

Figure 36: Wireframe of available two-wheeler parking slot to book

Page | 78
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

Figure 37: Wireframe of available four-wheeler parking slot to book

Figure 38: Wireframe of alert dialogue for booking confirmation i.e. two or four-wheeler

Page | 79
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.2.6. Feedback Screen

From feedback screen user can send feedback directly to the owner of parking
location/ developer regarding parking location or application issues.

Figure 39: Wireframe of feedback screen

Page | 80
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.2.7. Add eSewa Screen

Customer will register their eSewa Id from add eSewa screen for online
transaction.

Figure 40: Wireframe to register customer eSewa Id

Page | 81
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.2.8. Parking Slot Booked History Screen

From this screen user, can view their current booked parking slot of parking
location.

Figure 41: Wireframe of Parking Slot Booked History Screen

Page | 82
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.2.9. Transaction History Screen

From this screen, customer can view their transaction history of current 7 days in
graph as well as in text form.

Figure 42: Wireframe of Transaction History Screen

Page | 83
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.2.10. Customer Profile Screen

From customer profile screen, customer can view their information and as per
required they can update information by pressing on edit button.

Figure 43: Wireframe of customer profile screen

Page | 84
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.2.11. Edit Customer Profile Screen

From edit profile screen, customer can change their full name and can update their
password as per their required.

Figure 44: Wireframe of edit user profile screen

Page | 85
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.3. Wireframe of Android End User: Staff

7.3.3.1. Staff Dashboard Screen
From staff dashboard screen, staff can

i. View own profile using view profile button.

ii. Can view total transaction history of parking location through History
button.
iii. If any customer leave parking location, then that parking slot will be
made available by staff through Make Slot Available button.
iv. Through parking policy button staff can view, add and update parking
policy of parking location.
v. If offline customer came to park their vehicle, then according to their
vehicle type, staff will book the available parking slot using button either
2-Wheeler or 4-Wheeler offline lot booking button.

Figure 45: Wireframe of staff dashboard

Page | 86
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.3.2. Add Parking Policy Screen

Staff will update parking policy in pdf format through add parking policy screen.
Here, in app bar there is icon of home, when user press on it, it will display staff
dashboard.

Figure 46: Wireframe to add new parking policy

Page | 87
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.3.3. Staff Profile Screen

Staff personal and contract information are displayed in staff profile screen. From
this screen staff can change their login password by tapping change password
button. Similarly, user can go directly to dashboard by pressing home icon of app
bar.

Figure 47: Wireframe of staff profile screen

Page | 88
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.3.4. Change Password Screen

From change password screen user can change their login password by filling all
the field of given form. If user don’t want to change their password, the s/he can
press cancel button to go back to profile screen.

Figure 48: Wireframe of change profile screen

Page | 89
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.3.5. Two/Four-Wheeler Offline Booking Screen

This screen will display the available parking lot, staff book the available parking
slot for customer by pressing book now button. If user want to go back to
dashboard, then s/he can press on home icon button which in on app bar.

Figure 49: Wireframe of offline booking screen for staff

Page | 90
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.3.6. Offline Booking Form Screen

When staff press on book now button from offline booking screen i.e. 2/4-Wheeler,
then it navigates to offline booking screen. Here, staff fill the vehicle no. of customer
and select start time of park time and make booking by pressing of Confirm Booking
button.

Figure 50: Wireframe of offline booking form screen

Page | 91
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.3.7. Make Slot Available Screen

Before leaving parking location by customer, staff will make payment to customer
according to their booked slot by pressing Make IT available button. This screen
displays information of all booked slot.

Figure 51: Wireframe of make slot available screen

Page | 92
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.3.8. Transaction History

From this screen, staff can view total booked slot and total earn cost of per day
only. Staff can filter paid information of customer according to their email or
according to vehicle no. of customer. Similarly, staff can navigate directly to
dashboard by pressing home icon button.

Figure 52: Wireframe of transaction history of staff

Page | 93
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.4. Wireframe of Web Application End User: Admin

7.3.4.1. Login Page
Here, user fill their login information and press login button to logged in into the
system. Clear All button used to clear all text field of login form. Thus, this page
contains logo of Digital Parking application.

Figure 53: Wireframe of login page web application

Page | 94
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.4.2. Common sidebar for all web pages

In all web pages of admin panel, there is a common side bar which contains three
section i.e. View, Add and Manage. View section have two buttons i.e. Profile and
Feedback. When user press on profile button then it will display his/her personal
information from profile page. If user press on feedback button, then it will navigate
to feedback page and display all customer feedback. Similarly, add section also
contains two buttons i.e. New Staff. When admin press on New staff button then,
it will display staff registration form. If user press on manage parking location
button, then it displays parking location information with edit button. If user press
on manage staff button, then it displays all staff in a list with detail button. Admin
user can view all transaction and esewa details through Transaction and E-Sewa
button of manage section.

Figure 54: Common side bar for all web pages

Page | 95
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.4.3. Dashboard
When user logged in successfully, then Dashboard page will be displayed where
current transaction will displayed and total no. latest feedback, newly registered
user will be display.

Figure 55: Wireframe of admin dashboard in web application

Page | 96
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.4.4. User Profile Page

User Profile Page contains all the information of admin user. From this page user
can view their personal information by pressing personal info button and if user
want to view their account details then s/he can press on account info button.
Similarly, if admin user wants to change login password the s/he can simply press
on change password button and if user want to exit from the system then s/he can
press on logout button.

Figure 56: Wireframe of user profile personal info page in web application

Figure 57: Wireframe of user profile account info page in web application

Page | 97
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.4.5. Change Password Page

From this screen admin can change their login password by filling change
password form.

Figure 58: Wireframe of Change Password page in web application

7.3.4.6. Feedback Page

Current feedback of customer is displayed in this page. Admin can filter feedback
according to date or from user id.

Figure 59: Wireframe of Feedback page in web application

Page | 98
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.4.7. New Staff Page

From New Staff page, admin user can register new staff by filling all the information
of register form and that register staff can use the features of android application.

Figure 60: Wireframe to add new staff from web application

7.3.4.8. Manage Parking Location Page

Admin user can view and update the information of parking location as per required
from this page by pressing Update Parking Location.

Figure 61: Wireframe to manage registered parking location from web application

Page | 99
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.4.9. Update Parking Location Page

From update parking location page, admin user can update registered parking
location details by filling all the required field of update parking location form.

Figure 62: Wireframe to update registered parking location image from web application

7.3.4.10. Manage Staff Page

In this page, all registered staff information is displayed in a tabular format.
Admin user can view individual staff details by pressing detail button. Similarly,
admin user can filter staff according to staff name.

Figure 63: Wireframe of Manage Staff page in web application

Page | 100
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.4.11. Staff Profile Page

From staff profile page, admin user can view staff personal, contract and account
information. similarly, as per required admin user can update staff profile and
contract info by pressing Edit Profile and Edit Contract button.

Figure 65: Wireframe of staff profile, personal info page in web application

Figure 64: Wireframe of staff profile, contract info page in web application

Page | 101
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

Figure 66: Wireframe of staff profile, contract info page in web application

Page | 102
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.3.4.12. Manage Transaction Page

In this page all transaction is displayed per day. Admin user can filter transaction
according to date.

Figure 67: Wireframe of transaction page in web application

7.3.4.13. Manage ESewa Page

Here, all registered user eSewa Id are listed in a tabular form. Admin user can
remove or dis-registered eSewa Id as per required by pressing Delete button.
Similarly, admin user can load amount in customer eSewa Id.

Figure 68: Wireframe of manage eSewa page in web application

Page | 103
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.4. Entity Relationship Diagram

7.4.1. Possible entities
The possible entities of Digital Parking application are listed and summarized
below:

a) Parking Location
 To store information about parking location by Admin user and display
that stored information for Customer user.
b) Parking Policy
 To store parking policy of parking location. It will be added/uploaded by
the staff of that parking location. Similarly, this parking policy will be
viewed by Customer to make clear about their confusion.
c) User
 To store information of user who used this application. User may be
admin, staff or customer.
d) Staff
 To store information of user staff which included information like
contract, termination date and so on.
e) Feedback
 To store feedback of user i.e. customer. While storing feedback of user
it may hold the user information like user id, date, time and so on.
Feedback may be regarding the application or issues that found in
parking location.
f) eSewa
 To store the information of eSewa Id which will be unique for all user.
Here, information’s are included like eSewa Id (phone no), added date,
account balance and so on.
g) Slot Booking
 To store information of slot booking. It included information like user id,
staff id, start time, end time, slot no to identity which slot no. belong to
which user in what time.

Page | 104
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

h) Payment
 To store information about payment/ transaction that has been done by
general user i.e. Customer. This entity will be used to maintain and to
view transaction history.

7.4.2. Relationship Between Entities

a) Parking_Location and User

The relation between entity Parking_Location and User is one to many.

Parking location can have more than one user, but one user must belong to
one parking location.

Figure 69: Relationship between entity parking location and user

b) User and Staff

The relation between entity User and Staff in one and zero because one
User can be either only staff, admin or customer, but not all. Similarly, one
staff must be one user.

Figure 70: Relationship between entity User and Staff

c) Parking_Location and Parking_Policy

The relation between entity Parking_Location and Parking_Policy is one to

one because one Parking_Location must have one Parking_Policy. So that
customer can clear their confusion regarding parking policies.

Figure 71: Relationship between entity Parking_Location and Parking_Policy

Page | 105
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

d) Parking_Policy and Staff

The relation between entity Parking_Policy and Staff is zero and one
because one parking location may have more than one staff. Similarly, one
parking location have only one parking policy. So, here, one Parking_Policy
will be added by only one staff but not by all.

Figure 72: Relation between entity Parking Policy and Staff

e) User and Feedback

All user i.e. Customer may not send feedback regarding the issues of
parking location or regarding application. Due to this reason, the relation
between entity User and Feedback is One and Zero. Similarly, the relation
between entity User and Feedback is one to many because one user i.e.
Customer can send multiple feedback.

Figure 73: Relation between entity User and Feedback

f) User and eSewa

The relation between entity User i.e. Customer and eSewa is one to one or
one to many because one User i.e. Customer must have one eSewa Id for
online payment of slot booking. Similarly, one user can have more than one
eSewa Id. Thus, one eSewa Id will be belong to only one user.

Figure 74: Relation between entity User and eSewa

Page | 106
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

g) User and Slot_Booking

One user i.e. customer can book more than one parking slot through online
in a day but at a time one user i.e. customer can book only one parking slot.
Due to this reason, the relation between entity User i.e. customer and
Slot_Booking is one to one or one to many. Similarly, one parking slot can
be booked by multiple user i.e. customer but at a time only one user can
book parking slot for particular time or duration in a day. Due to this reason,
the relation between User and Slot_Booking is many to many.

Figure 75: Relation between entity User and Slot_Booking

h) Staff and Slot_Booking

One staff may book multiple parking slot in a day for multiple offline
customer, but at a time one staff can book only one parking slot for offline
user i.e. customer. Due to this reason the relation between entity Staff and
Slot_Booking is one and many. Similarly, if staff is not in duty then that staff
will not book particular slot. So, here the relation between staff and
Slot_booking entity is one and zero.

Figure 76: Relation between entity Staff and Slot_Booking

Page | 107
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

i) Staff and Payment

One staff can make payment for more than one offline and online customer
of booked parking slot before leaving parking location. Due to these
reasons, the relation between entity Staff and Payment is one to many or
many to one.

Figure 77: Relation between entity Staff and Payment

j) eSewa and Payment

One payment may belong to one or multiple eSewa Id, but one eSewa Id
can make one or more payment. Due to these reasons, the relation between
eSewa and Payment is one and many or many to many.

Figure 78: Relation between entity eSewa and Payment

Page | 108
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.4.3. Data Dictionary

a) Parking_Location

SN. Attributes Name Data Type Others

1. loc_id int (11) PRIMARY KEY, AUTO
INCREMENT
2. loc_name varchar (50) UNIQUE
3. latitude double
4. longitude double
5. two_wheeler_slot int (11) Default 0
6. four_wheeler_slot int (11) Default 0
7. loc_image varchar (100)
Table 42: Data dictionary of entity Parking_Location

Page | 109
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

b) User

SN. Attributes Name Data Type Others

1. user_id int (11) PRIMARY KEY, AUTO
INCREMENT
2. loc_id int (11) FOREIGN KEY,
parking_location (loc_id)
3. full_name varchar (30)
4. email varchar (50) UNIQUE
5. password varchar (30)
6. user_type varchar (10)
7. is_active tinyint (1) Default 1
8. is_staff tinyint (1) Default 0
9. is_superuser tinyint (1) Default 0
10. is_verified tinyint (1) Default 0
11. created_at datetime
12. gender varchar (1)
13. dob date
14. address varchar (50)
15. phone varchar (50)
16. profile_pic varchar (100)
17. last_login datetime
Table 43: Data dictionary of entity user

c) Staff

SN. Attributes Name Data Type Others

1. staff_id int (11) PRIMARY KEY, AUTO
INCREMENT
2. user_id int (11) FOREIGN KEY, user
(user_id)
3. appointed_date date
4. termination_date date
5. citizenship_photo varchar (100)
Table 44: Data dictionary of entity staff

Page | 110
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

d) Parking_Policy

SN. Attributes Name Data Type Others

1. policy_id int (11) PRIMARY KEY, AUTO
INCREMENT
2. staff_id int (11) FOREIGN KEY, staff
(staff_id)
3. loc_id int (11) FOREIGN KEY,
parking_location (loc_id)
4. added_at date
5. pdf_file varchar (100)
Table 45: Data dictionary of entity parking_policy

e) Feedback

SN. Attributes Name Data Type Others

1. feedback_id int (11) PRIMARY KEY, AUTO
INCREMENT
2. user_id int (11) FOREIGN KEY, user
(user_id)
3. subject varchar (150)
4. description varchar (500)
5. created_at datetime (6)
Table 46: Data dictionary of entity feedback

f) eSewa

SN. Attributes Name Data Type Others

1. eId int (11) PRIMARY KEY, AUTO
INCREMENT
2. user_id int (11) FOREIGN KEY, user
(user_id)
3. eSewa_Id varchar (15)
4. eSewa_added_date datetime (6)
5. eSewa_amount double Default 5000
Table 47: Data dictionary of entity esewa

Page | 111
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

g) Slot_Booking

SN. Attributes Name Data Type Others

1. slot_booking_id int (11) PRIMARY KEY, AUTO
INCREMENT
2. staff_id int (11) FOREIGN KEY, staff
(staff_id)
3. user_id int (11) FOREIGN KEY, user
(user_id)
4. vehicle_type varchar (15)
5. vehicle_no varchar (20)
6. slot_no varchar (15)
7. book_date date
8. book_time datetime (6)
9. park_star_time datetime (6)
10. park_end_time datetime (6)
11. park_extended_time datetime (6)
12. extended_time_amount double Default 0
13. advance_paid_amount double Default 0
14. total_amount double Default 0
Table 48: Data dictionary of entity slot_booking

Page | 112
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

h) Payment

SN. Attributes Name Data Type Others

1. payment_id int (11) PRIMARY KEY, AUTO
INCREMENT
2. staff_id int (11) FOREIGN KEY, staff
(staff_id)
3. slot_booking_id int (11) FOREIGN KEY,
slot_booking
(slot_booking_id)
4. eid int (11) FOREIGN KEY, eSewa
(eId)
5. payment_type varchar (10)
6. payment_date date
7. payment_time datetime (6)
8. paid_amount double Default 0
Table 49: Data dictionary of entity payment

Page | 113
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

7.5. Project as a solution

This project will help to overcome the above problem statement by following ways:

a) With the help of this application people (end users) will be able to book
available parking lot before they reach to their destination which saves the
precious time of people and makes free from frustrating process to search
parking lot in their daily life.
b) Similarly, this application helps to systematize the parking location. How?
Before using this application, the owner of parking location most declared
their total available parking lot for two-wheeler i.e. bike, scooter and four-
wheeler like car and most declare parking cost on hourly basis. Due to these
reasons it helps to minimize fear of people regarding vehicle scratch, stollen
of vehicle from the parking location.
c) According to the parking location their policies, rules, regulation and their
parking price may be different from one another. So, with the help of this
application people can read the parking location policies, parking lot price
before they book available parking lot which helps to minimize confusion in
people regarding the parking policies and price of parking lot in hourly basis
of parking locations.
d) This application helps to minimize the problem in traffic congestion. How?
People will not stop in traffic lane and do not wait for parking space to park
their vehicle because with the use of this application people book available
parking lot before they reach to their destination.

Page | 114
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

7.6. Revision of Milestone

Figure 79: Revision of Project Milestone

✓ Milestone 1: Project Start (1st Nov 2020 – 27th Nov 2020)

In milestone 1, requirement will be gathered, similar application will be

finding, project scope will be determined, and resource estimation will be
done.

✓ Milestone 2: Develop Use Case (27th Nov 2020 – 13th Dec 2020)

In milestone 2, from the gathered requirement use cases will be drawn.

✓ Milestone 3: Designing System Architecture (13th Dec 2020 – 1st Jan 2021)

In milestone 3, whole system architecture will be design which included

wireframe design, class and UML diagram will be drawn.

✓ Milestone 4: System Development (1st Jan 2021 – 1st Mar 2021)

In milestone 4, system development process begins on the base of

designed wireframes.

✓ Milestone 5: Testing (1st Mar 2021 – 23rd Mar 2021)

In milestone 5, test cases will be prepared, testing of the system like white
box testing, black box testing will be done according to the test cases and
user manual will be developed.

Page | 115
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

✓ Milestone 6: Report Writing (1st Apr 2021 – 25th Apr 2021)

In milestone 6, proper documentation will be written and finalized and ready

for submission.

✓ Milestone 7: Project Submitted to RTE (26th Apr 2021)

In milestone 7, project is reviewed for the final time and submitted to the
RTE.

Page | 116
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.7. Revison of Project Gantt Chart

Figure 80: Revision of Project Gantt Chart

Page | 117
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

7.8. Considered Methodology

7.8.1. Waterfall Model
Waterfall model is a linear and sequential process of project management where,
at initial phase of software development, requirements were gathered from
stakeholders and customer then the sequential project plan is created to meet
those requirements. (ProjectManager.com, Inc., 2020) Thus, the phases of
waterfall model follow in sequential order and to begin the next phases of waterfall
model, first previous phases must be completed. (ProjectManager.com, Inc., 2020)
The main drawbacks of this model are it cannot accommodate the changing
requirements. (Rouse, 2019)

Figure 81: Phases of Waterfall Model (Jones & Waddell, 2019)

Page | 118
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

7.8.2. Unified Process

Unified Process is an iterative, use case driven, architecture centric and
incremental software development process frameworks which can be customized
for specific project or specific organization. (Techopedia Inc., 2011) In Unified
Process or Unified Software Development Process, for documentation and design
UML is used. Example of Unified Process are Rational Unified Process (RUP),
Open Unified Process (OUP) and Agile Unified Process (AUP). (MacIsaac & Kroll,
2006)

Figure 82: Unified Process (anuragmbst, 2013)

7.8.3. Agile Methodology

In agile methodology requirements and solutions are gathered from the teams and
client through collaborative effort. This methodology is based on iterative and
incremental methods for software development. So due to iterative development,
it encourages frequent inspection and adaption which helps to produce high quality
software. Thus, this methodology is developed for those project and products
which required flexibility and rapid delivery of high-quality software. (Rigby, et al.,
2016)

Figure 83: Agile Methodology (Chauhan, 2019)

Page | 119
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

7.9. Selected Methodology

7.9.1. Rational Unified Process (RUP)
Rational Unified Process (RUP) is an object-oriented methodology created by
Rational Software Corporation. (ANWAR, 2014) This methodology is an iterative
software development process which provides framework for defining vast
spectrum of different size,
complexities and considerations of
project. (Javed, et al., 2012) The main
purpose of this methodology is to
produce high quality of software by
fulfilling the requirements of its end
users, within a predictable schedule
and budget. (ANWAR, 2014) Thus,
RUP methodology consists of four Figure 84: Phases of RUP (ang, 2012)

phases which are shown in figure and

explained below:

1. Inception:

This is the first phases of RUP methodology which focuses on project launch.
(ANWAR, 2014) In this phase following things are done:

a. Scope of project will be identified. (ANWAR, 2014)

b. Initial risk assessment and cost estimation of project will be identified. (ANWAR,
2014)
c. Vision of document will be prepared after the discussions with supervisor.
d. Basic use case model will be prepared (10% - 20%). (ANWAR, 2014)
2. Elaboration:

Elaboration is the second phases of RUP methodology where the major technical
risk of the project will be identified and develop the basic architecture of the system
so that it will identify the question of technical. (ANWAR, 2014) In this phase
following things are done:

a. Resources and cost are reevaluated and finalized here.

b. Revision of business cases and risk. (ANWAR, 2014)

Page | 120
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

c. Possible uses cases will be identified. (Javed, et al., 2012)

d. Identify the actors. (ANWAR, 2014)
e. Develop the plan for overall project. (Javed, et al., 2012)
f. Class diagram, UML diagram and wireframes are made. (ANWAR, 2014)
3. Construction

In construction phases it focuses on developing operational system by using the

executable basic system architecture which was created in elaboration phases.
(ANWAR, 2014) In this phase following things are done:

a. Develop application component and features. (ANWAR, 2014)

b. Coding and testing will be done. (ANWAR, 2014)
c. User manual of the system will be developed. (Javed, et al., 2012)
d. Beta version of the system should be ready for evaluation. (Javed, et al., 2012)
4. Transition

Transition is the last phases of RUP methodology which focuses on transitioning

the system from the development stage to actual production. (ANWAR, 2014) In
this phase following this will be done:

a. Developed system will be evaluated and refined it on the base of user’s

feedback. (ANWAR, 2014)
b. Check the system quality standard meet or not that were set on inception phase
and deployment of product. (ANWAR, 2014)

Page | 121
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

7.10. Survey at Parking Location

7.10.1. Buddha Mall - Machhapokhari

Page | 122
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

Page | 123
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

Page | 124
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

Page | 125
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.10.2. BG Mall – Gongabu

They have not started their parking spot formally.

Page | 126
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

7.10.3. Biswa Joyti Mall – Jamal

Page | 127
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

Page | 128
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

Page | 129
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

Page | 130
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.10.4. Rising Mall – Durbar Marg

Page | 131
NP01CP4A180002 | Jagaran Maharjan December 25, 2020
CS6P05NI Final Year Project

Page | 132
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

Page | 133
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

Page | 134
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.10.5. City Center – Kamal Pokhari

They don’t want any survey and said us there was not any problem in their parking
location.

Page | 135
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.10.6. World Trade Center

Page | 136
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

Page | 137
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

Page | 138
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

Page | 139
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.12.9. What kind of features would you like to suggest in developing

parking applications?

Figure 94: Suggested features for developing application by people

Out of 102 people, suggested common feature are listed below:

a) Based on GPS
b) Online Payment
c) Online Parking Lot Booking, Updating and Cancelling [Must give parking slot
number]
d) Time extension
e) Reminder of start and end time / 15min before [Smart Alert]
f) Available Parking Spots should be mentioned for booking parking slot
g) Parking Policy like guarantee of not getting scratches in vehicle
h) Profile of Parker
i) Booking History
j) App must be responsive

Page | 160
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.13. Dart code written in Android Studio for android application

Figure 96: Screenshot of dependency used for android application development

Figure 95: Screenshot of location model

Page | 161
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

Figure 97: Screenshot of location provider

Page | 162
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

Figure 98: Screenshot of local API used in android application

Figure 99: Screenshot of user model

Page | 163
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.14. Git log of android studio code pushed at GitHub

Figure 100: Screenshot of git log of android code

Page | 164
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

7.15. Python code written in PyCharm for web application

Figure 102: Screenshot of Customizing User Model

Figure 101: Screenshot of creating user serializer

Page | 165
NP01CP4A180002 | December 25, 2020
CS6P05NI Final Year Project

Figure 103: Screenshot of path URL to navigate pages

7.16. Git log of web application code pushed at GitHub

Figure 104: Screenshot of git log of web code pushed at GitHub

Page | 166
NP01CP4A180002 | December 25, 2020