Final Year Report 114

ONLINE VEHICULAR SERVICES FINDER
DANISH KHAN
MUHAMMAD MAHTAB
DEPARTMENT OF COMPUTER SCIENCES
COMSATS UNIVERSITY ISLAMABAD, WAH CAMPUS

PAKISTAN
SESSION 2015-2019
ONLINE VEHICULAR SERVICES FINDER
Undertaken By:
DANISH KHAN
REG. NO. CIIT/FA15-BS(SE)-56/WAH
MUHAMMAD MAHTAB
REG. NO. CIIT/FA15-BS(SE)-89/WAH
Supervised By:
Ms. Anam javaid
A DISSERTATION SUBMITTED AS A PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF BACHELOR’S
IN COMPUTER SCIENCE
DEPARTMENT OF COMPUTER SCIENCES

COMSATS UNIVERSITY ISLAMABAD, WAH CAMPUS
PAKISTAN
SESSION 2015-2019
ii
Online vehicular services finder
FINAL APPROVAL
Certified that we have read this project report submitted by Mr. Danish Khan and Mr.
Muhammad Mahtab it is in our judgment of sufficient standard to warrant its acceptance by
COMSATS Institute of Information Technology, Wah Cantt, for the bachelor’s degree in
software engineering.
Committee:
1. External Examiner ____________________________

(Examiner Name)
Designation
University Name
2. Supervisor ____________________________
(Ms. Anam javaid )
3. HOD ____________________________
(Dr. M. Wasif Nisar)
iii
In the Name Of
Allah
The Most Beneficent
And
The Most Merciful
iv
DEDICATION
After being thankful to Almighty Allah, by whose grace and help we are now able to stand at
this point, we would like to dedicate it to our parents who is a boon to us and their love is a
great blessing I pray that “God bless these parents, for all the tears and heartaches and for all
the special work they’ve done”
Also dedicated to thousands of people who aspire high but couldn’t due to lack of resources
and their circumstances.
Danish Khan
Muhammad Mahtab
v
ACKNOWLEDGEMENT
We are thankful to Almighty Allah for his countless bounties and for enabling us to accomplish
this project. We would like to show our deep gratitude to our supervisor Ms. Anam javaid for
his consistent assistance, advices and support during the development period of this project.
We are also thankful to our parents who brought us to this destination and acted as a backbone
behind our accomplishment. And last but not least we express heartiest gratitude to our friends
and all those who helped us in the accomplishment of this project and project report.
vi
PROJECT BRIEF
PROJECT NAME ONLINE VEHICULAR SERVICES FINDER

OBJECTIVE DEVELOP ANDROID APPLICATION WHICH
HELPS PEOPLE TO TRAVEL EASILY AROUND
AND DON’T FIND DIFFICULTIES DURING THEIR
JOURNEY
UNDERTAKEN BY MUHAMMADMAHTAB, DANISH KHAN
SUPERVISED BY Ms. ANAM JAVAID
LECTURER AT CIIT WAH CAMPUS
STARTED ON NOVEMBER 16, 2018
COMPLETED ON JUNE 10, 2019
COMPUTER USED HP-CORE i5
SOURCE LANGUAGE JAVA, XML
OPERATING WINDOWS 10
SYSTEM
TOOL USED ANDRIOD STUDIO 1.3.2
vii
ABSTRACT
Online parking booking is very useful in our daily life because it is a very big problem which
people are facing in their daily life. Now people have their own vehicles that increase the
number of vehicles but in past, their number are less because they were using the public
transport. Now a day, parking is a big problem for the citizen in the big cities and during the
travel to other cities which are not familiar to them, educational institutions and at many other
places. So using this app it will be very easy to the users to find their nearest parking in their
surroundings.
viii
TABLE OF CONTENTS
1. Introduction ............................................................................................................................................. 2
1.1. Purpose of this document ................................................................................................................ 2
1.2. Scope of this document.................................................................................................................... 2
1.3. Overview ......................................................................................................................................... 2
1.4. Business Context ............................................................................................................................. 3
1.5. Intended audience ............................................................................................................................ 3
2. General Description ................................................................................................................................ 5
2.1. Product function .............................................................................................................................. 5
2.2. Similar System Information............................................................................................................. 5
2.3. User Characteristics ......................................................................................................................... 5
2.4. User Problem Statement .................................................................................................................. 5
2.5. User Objectives................................................................................................................................ 6
2.6. General Constraints ......................................................................................................................... 6
3. Functional Requirements ........................................................................................................................ 8
3.1. Create parking: ................................................................................................................................ 8
3.3. Reserve parking: .............................................................................................................................. 9
4. Non-Functional Requirements .............................................................................................................. 11
4.1. Interface Requirements .................................................................................................................. 11
4.2. Performance Requirements............................................................................................................ 11
4.3. Design Constraints ......................................................................................................................... 11
4.4. Standards Compliance ................................................................................................................... 11
4.5. Hardware Limitations .................................................................................................................... 11
5. Non-Functional Attributes .................................................................................................................... 13
5.1. Security .......................................................................................................................................... 13
5.2. Binary Compatibility ..................................................................................................................... 13
5.3. Reliability ...................................................................................................................................... 13
5.4. Maintainability............................................................................................................................... 13
5.5. Portability ...................................................................................................................................... 13
5.6. Extensibility ................................................................................................................................... 13
5.7. Serviceability ................................................................................................................................. 13
6. Preliminary Object-Oriented Domain Analysis: ................................................................................... 15
6.1. Inheritance Relationships .............................................................................................................. 15
6.2. Use Case Diagram: ........................................................................................................................ 16
6.3. Class Diagram................................................................................................................................ 17
6.4. ER Diagram ................................................................................................................................... 18
ix
6.5. Activity Diagram ........................................................................................................................... 19
6.6. Sequence Diagram: ........................................................................................................................ 20
7. Implementation ..................................................................................................................................... 23
Detecting Internet Connection ..................................................................................................................... 23
7.1. Application User Interface: ........................................................................................................... 23
8. Testing................................................................................................................................................... 30
8.1. Testing strategies ........................................................................................................................... 30
8.2. Black Box Testing ......................................................................................................................... 30
8.3. White Box Testing ......................................................................................................................... 31
8.4. Unit Testing ................................................................................................................................... 31
8.5. Integration Testing ......................................................................................................................... 31
8.6. User acceptance Testing ................................................................................................................ 31
8.7. Test cases: ...................................................................................................................................... 32
8.8. Sign Up/ Register........................................................................................................................... 32
8.9. Search Near-by Parking ................................................................................................................. 33
8.10. Search Near-by Gas Stations ..................................................................................................... 34
9. Conclusions ........................................................................................................................................... 36
10. Appendices ........................................................................................................................................ 38
10.1. Definitions, Acronyms and Abbreviations ................................................................................ 38
10.2. References: ................................................................................................................................. 38
x
TABLE OF FIGURES
Figure 1 Inheritance Relationship ........................................................................................... 15

Figure 2 Use Case Diagram .................................................................................................... 16
Figure 3Class Diagram ............................................................................................................ 17
Figure 4 ER Diagram .............................................................................................................. 18
Figure 5 Activity Diagram ...................................................................................................... 19
Figure 6 Sequence Diagram for User ...................................................................................... 20
Figure 7 Sequence Diagram for Owner................................................................................... 21
xi
Introduction
Chapter 1
INTRODUCTION
1
Introduction
Online Vehicular Services Finder
1. Introduction
1.1. Purpose of this document
The purpose of this report is to fully document the specifications and requirements for application
online vehicular services finder. The audience of this report will be the technical professionals
developing the software.
The purpose of this application is as follow:
 To provide easy way of accessing parking place.
 To provide a way of creating a parking garage and show them to the audience.
 To provide better way to fuel their gas tanks.
1.2. Scope of this document
Online parking is for citizens and for the owners of the different busy points such as Shopping Malls
and many other places. Owner of the place can enter the number of slots in his parking. This android
app will registers different places of different cities and people give their location and after that, he can
see the parking places and he can book his parking place. The document is going to be helpful
throughout the development phases. Another purpose of the document is to set a milestone by defining
all requirements i.e. what to do. It specifies where the system is going to be used. Who will do and in
how much time taken to complete the task within a given limited budget?
1.3. Overview
Online parking is a need of the day because parking is the big problem now a day because of a big
number of vehicles increases. And if you go to other cities you don’t know where to park your car
safely and this will help them to park their vehicles safely. It saves time and it is a very easy way to
book and pay for parking. It’s also helpful to find near gas stations.
2
Introduction
1.4. Business Context
In business context this app will be widely used because every owner of the garage will be registered,
and users will have easy access to their garage. It saves time and it is a very easy way to book and find
for parking.
1.5. Intended audience
This report is intended for the developers, analyst, designer, coder, software engineer. So by the help
of this SRS we can understand what we are going to do in future and what we will make. It shows the
way to take the next step so we can say that it plays very important role in the software development.
In this SRS, first we are going to collect the requirements, then there will come a planning phase that
how we are going to develop the application and after that we will do analysis of this application and
in the result of this analysis we will get some specific requirements so after that we will document
those requirements. To some extent designing is also included in this document.
1.6. Primary schedule

 GANTT chart:
 Preliminary Budget
The budget for this project is approx. RS. 30,000.
3
General description
Chapter 2
GENERAL DESCRIPTION
4
General description
2. General Description
2.1. Product function
Describes Vehicles are increasing day by day in Pakistan. Especially in populous cities like Karachi,
Lahore, Peshawar and Faisalabad and there is not enough space for parking in commercial areas. On
other hand some people want to buy vehicles, but they don’t have their own space for parking. So,
parking space is not easily available in commercial areas particularly at peak hours and also in
residential areas. My proposed android application will allow people to search their nearby available
parking places at any time. And people can reserve their parking place by using this application and be
able to gain services offered by parking garages like car maintenance where they will be able to repair
minor issues of the cars. user will also be able to find near gas stations, so they will never run out of
gas on their way and reach their destinations easily.
2.2. Similar System Information
There are already some applications related to vehicle parking. Some of them are web based
applications and some of them are android based applications. But those applications gives some
functionality and ease.
Example Park me: Park me is one of android based application. This application is not so popular in
Pakistan. Park me is specially designed for commercial parking plazas.
2.3. User Characteristics

It is very easy to use. If anyone who can use mobile and uses social media such as Facebook, Skype
then it is not a big deal for him.
2.4. User Problem Statement

As population increased in Pakistan. The need for transportation means is also increased. Individuals
from everywhere throughout the Pakistan go to Karachi, Peshawar, Lahore and different crowded
urban areas for driving taxicabs and rickshaws. These people don’t have their own places for living
and also for vehicle parking. Therefore number of vehicles parked on roads increasing day by day in
major cities of Pakistan. It cause parking issues. There is also security problems in road parking like
theft. There is another aspect of all of this is when people goes to public places like Shopping plaza’s
parks and hotels in festival days. They face worst parking problems. They also not able to find near
gas stations to full their gas tank.
5
General description
2.5. User Objectives
The solution of this problem is the development of an android application in which place owner can
upload the location of their place which will be available for parking and other people can find their
nearby parking places by using that application. Customers can also reserve available parking places.
User can also describe all other facilities like maintenance available in their place.
2.6. General Constraints

this app only run on android phones so person with the IOS cannot use this App. this required internet
access to use the app.
6
Functional Requirements
Chapter 3
FUNCTIONAL REQUIREMENTS
7
3. Functional Requirements
It should register the different parking points of the cities. It shows parking slots for the user
and shows empty and booked spaces with their respective colors. The system provides
following features:
User Registration.
 Map based dynamic dashboard.

 Create parking place.
 Searching nearby parking places.
 Searching nearby gas stations.
 Reserve parking place.
 Feedback
3.1. Create parking:
 Description
A User (Owner) can create the garage or a parking spot where other users can see spot
on map and can book the garage.
 Criticality
It is critical that it can register the owner and that other can see the parking slot on their
map.
 Technical issues
Technically and with design perspective, this requirement must be in a way that its
design must be of such type that if it is required to be changed or extended, it must be
open for this purpose.
 Cost and schedule
Cost of this requirement is high in the form of the importance of this requirement.
Schedule for this is three weeks.
 Risks
This will require one month to be developed. The cost associated with it high in the
form of the value of the functionality.
 Dependencies with other requirements
8
No dependency.
3.3. Reserve parking:
 Description
A User can reserve the garage or a parking spot on the map of desired location. After
reservation user will notified of their actions.
 Criticality
without fulfilling this requirement user will be unable to use the system.
 Technical Issues
It must be closed for modifications but open for extension.
 Cost and schedule
Cost of this requirement is high in the form of the importance of this requirement.
Schedule for this is three weeks.
 Risks
This will require the accuracy so that user booked the parking place that he wanted.
System should accurately show and book parking according to user needs.
 Dependencies with other requirements
No dependency.
9
Non-Functional Requirements
Chapter 4
NON-FUNCTIONAL REQUIREMENTS
10
Non-Functional Requirements
4. Non-Functional Requirements
4.1. Interface Requirements
 User Interfaces
Each interface is logically related to the user. Every menu in the product is user-related or this product
is interfaced dependent. Interfaces are designed in such a way that user can easily communicate with
the system, they are user-friendly, easy to understand and interact. Interfaces include all kind of
standard buttons, functions, special screen layouts, confirm or error messages etc. It is easily accessible
and it easy to use for both user and owners. It should be working in such a way that people find is
attractive and one thing that it has that separation of concern that means that it should have different
interfaces for user and owner. It should not show irrelevant and extra things to both.
4.2. Performance Requirements

Performance requirements are of great importance. The system performance responds time must be
minimized so to increase the system functionality. We don’t use heavy images and videos on app that
makes our app slow. We should use design pattern to maximize our performance and other techniques.
The application should perform accurately under all circumstances except some loss or crash in the in
mobile or internet connection. We also make sure error handling that saves our user from a bad
experience.
4.3. Design Constraints

The design should be extended, and it must assure separation of concern. It should have high cohesion
and low coupling.
4.4. Standards Compliance

The app will be used by the owner of places, but its services can be achieved by other owners after
getting a signed agreement or registration.
4.5. Hardware Limitations

Android 5.0 or later, 3MB of free storage, Minimum 512 MB, recommended 1 GB, Minimum dual
core, recommended quad core
11
Non-Functional Attributes
Chapter 5
NON-FUNCTIONAL ATTRIBUTES
12
Non-Functional Attributes
5. Non-Functional Attributes
5.1. Security
Login should be required for an owner that provides security for his business. Security
requirement defines that the data in the system must be safe and secure. No data must
be visible to any third party or unauthenticated person. The data of the system is highly
sensitive, so it must be secured through authentication system of the user.
5.2. Binary Compatibility

If two or more persons are the same software, then they must run it without requiring
that the application is recompiled.
5.3. Reliability
The system must be reliable in terms of time, failure rate, customer usage and operating
environment. The system should never crash or hang, other than as the result of an
operating system error.
5.4. Maintainability
The system must be easy to maintain in case of any abruption.
5.5. Portability
The system must be easy to transfer from one computer to other for installation.
5.6. Extensibility
In future, it might be required to add a new module if required. The system must be of
such type that at adding new module or function, older one should not get disturbed.
The system must be open for extension in future without disturbing existing
functionality.
5.7. Serviceability
The system must be available 24/7.
This section presents a list of the fundamental objects that must be modelled within the
system to satisfy its requirements. The purpose is to provide an alternative, "structural"
view on the requirements stated above and how they might be satisfied in the system.
13
System design
Chapter 6
SYSTEM DESIGN
14
System design
6. Preliminary Object-Oriented Domain Analysis:

This section presents a list of the fundamental objects that must be modelled within the system
to satisfy its requirements. The purpose is to provide an alternative, "structural" view on the
requirements stated above and how they might be satisfied in the system.
6.1. Inheritance Relationships
Figure 1 Inheritance Relationship
15
System design
6.2. Use Case Diagram:
Figure 2 Use Case Diagram
16
System design
6.3. Class Diagram
Figure 3Class Diagram
17
System design
6.4. ER Diagram
Figure 4 Er Diagram
18
System design
6.5. Activity Diagram
Figure 5 Activity Diagram
19
System design
6.6. Sequence Diagram:
Figure 6 Sequence Diagram for User
20
System design
Figure 7 Sequence Diagram for Owner
21
Implementation
Chapter 7
IMPLEMENTATION
22
Implementation
7. Implementation
Implementation is the final and the most important phase. The most critical stage in achieving
a successful new system is giving the user confidence that the new system will work and be
effective. The system can be implemented only after through testing is done and if it is found
to be working according to user needs and full fill user expectation.
Detecting Internet Connection
First of all user must confirm that he/she is connected with some internet connection like his/her
laptop or pc is connected to any Wi-Fi connection or network connection because this App
requires internet connectivity else if won’t work. If there is no internet connection then the App
will not be able to open app.
7.1. Application User Interface:

Sign up page:
If user don’t have account, then he will need to sign up first
Figure 8 Sign up page
23
Implementation
Home screen:
After successful log in user will be directed to main home page
Figure 9 Home Screen
24
Implementation
Figure 10 Home screen
25
Implementation
Figure 11 Parking Map view
26
Implementation
Figure 12 parking Map view
Figure 13 Parking Garage Images
27
Implementation
Figure 14 parking Reviews
28
Testing
Chapter 8
TESTING
29
Testing
8. Testing
System testing of software or hardware is testing conducted on a complete, integrated system

to evaluate the system’s compliance with its specified requirements. System testing is the stage
of implementation, which insures the system working efficiently and accurately. Testing means
finding errors and missing operations and also a complete verification to determine whether
the objectives are met and the user requirements are satisfied. The ultimate aim is quality
assurance. There are different types of testing which perform on the system to find the working
of the software on different stages.
8.1. Testing strategies

The basic principles for distinct are:
 All test should be traceable to user requirement.
 Test should be planned long before testing begins.
 Testing should begin in the small and progress toward testing in the large.
Software testability is simply how easily a computer program can be tested. Testability
is used to be how adequately a particular set of test will cover the product. The
following set of characteristics needs to the testable software
 Operability
 Controllability
 Understandability
8.2. Black Box Testing

Black box testing is a method of software testing that tests the functionality of an
application as opposed to its internal structures or workings. Specific knowledge of the
application’s code/internal structure and programming knowledge in general is not
required. Black box testing attempts to find errors in the following categories
1. Incorrect or missing functions
2. Interface errors
3. Errors in data structures or external database access
4. Behavior or performance errors
5. Initialization and termination errors
30
Testing
So, for black box testing we checked the functions, interfaces, connection of database
is working properly and vice versa.
8.3. White Box Testing

White box testing uses internal description of the software, internal operations are
performing according to the specification and requirements of the end users. we have
tried our level best to adopt the above stated methodologies of white box testing i.e.
have run the modules several times, exercised all logical decisions and executed all
loops at their boundaries efficiently
.
8.4. Unit Testing

Unit testing is a method by which individual units of source code are tested to determine
if they are fit for use. A unit is a smallest testable part of an application. This enables,
to detect errors in coding and logic that are contained within each module. The various
controls are tested to ensure that each performs its action as required.
8.5. Integration Testing

Integration testing is a phase in software testing in which individual software modules
are combined and tested as a group. It occurs after unit testing and before system testing.
In integration testing we applied test on the call operations.
8.6. User acceptance Testing

User acceptance testing is very important factor for the success of this system. The
system under consideration is tested for user acceptance by constantly keeping in touch
with the system user at time of developing and making changes whenever required. The
user of my system are also satisfied because of the user friendly environment in which
they will work well.
31
Testing
8.7. Test cases:

Following are the Test Cases for our project (Online vehicular services finder):
8.8. Sign Up/ Register
TC1: Sign Up/register
Test Case ID: 1

Wrote By: Danish khan and mahtab
Test Type: Black box testing
Product Name: Online vehicular services finder
Test Item: Android App
Documented Date: 1/6/2019
Test case description: This test case is designed to successfully sign up
Operation procedure: 1. Open App
2. Click on the sign up/register
3. If you don’t have account, click register signup will
open a modal which allows options to sign up using
username and password
4. User will be directed to the main page
Pre-conditions: Internet is required, and Server must be up and running
Post-conditions: Access to the main page
32
Testing
8.9. Search Near-by Parking
TC2: Search Nearby Car Parking
Test Case ID: 2

Test case description: This test case is designed to successfully find nearby parking

2. Click on the car parking
3. Parking available are shown on the screen
4. User will select one and can see other information

Post-conditions: Access to car parking area
33
Testing
8.10. Search Near-by Gas Stations
TC3: search nearby Gas stations
Test Case ID: 3

Test case description: This test case is designed to successfully find nearby gas
stations
6. Click on the gas stations
7. Nearby gas stations are shown are shown on the
screen
8. User will select one and can see other information
Post-conditions: User can see gas stations of their choice
34
Conclusions
Chapter 9
CONCLUSIONS
35
Conclusions
9. Conclusions
In this project we have developed an Android app that provide a social platform where user
can easily get information and solution to their problems.
User can now have access to the car parking and other options at their ease. The objective of
our proposed system is to design a real-time social app in which we bring people together.
 Future Work
The work we did in this project presents many opportunities for future work. The
following is a list of ideas that can improve upon this project and provide a guideline
in this heading.
 Video Uploading
A video of any parking place is uploaded in description, so anyone can easily
understand parking.
 Voice Call
This feature would allow users to call to each other.
36
Appendices
Chapter 10
APPENDICES
37
Appendices
10. Appendices
Specifies other useful information for understanding the requirements. All SRS documents
should include at least the following two appendices:
10.1. Definitions, Acronyms and Abbreviations

SRS: Software Requirement Specification document.
USER: User is the person who wants to book for parking.
OWNER: Owner is the person who is the owner of that parking point.
OOP: object-oriented programming
IOS: iPhone operating system
App: application
API: application programmable interface
10.2. References:
1) What is Android. Retrieved Nov 01, 2017, from
https://en.wikipedia.org/wiki/Android_(operating_system)
2) MS SQL Server, Retrieved Nov 01, 2017, from
https://en.wikipedia.org/wiki/Microsoft_SQL_Server
3) IIS. Retrieved Nov 01, 2017, from
https://en.wikipedia.org/wiki/Internet_Information_Services
4) Retrofit, Lars Vogel, Simon Scholz, David Weiser (c) 2012, 2017 vogella GmbH.
Retrieved Nov01,2017, from http://www.vogella.com/tutorials/Retrofit/article.html
5) Java. Retrieved Nov 01, 2017, from
https://en.wikipedia.org/wiki/Java_(programming_language)
6) Google Map Api. Retrieved Nov 01, 2017, from
https://www.w3schools.com/graphics/google_maps_overlays.asp
7) Erik Reitan, WCF (Windows Communication Foundation). Retrieved Nov 01, 2017,
from https://docs.microsoft.com/en-us/dotnet/framework/wcf/whats-wcf
8) GSON Libraray. Retrieved Nov 01, 2017, from https://github.com/google/gson
9) https://www.lucidchart.com/documents/edit/55c83e4a-da92-4672-ace6-
a6a7fede4975/0
10) https://creately.com/app/?tempID=i3b6yxgt1&login_type=demo#
38

Final Year Report 114

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Final Year Report 114

Uploaded by

Copyright:

Available Formats

ONLINE VEHICULAR SERVICES FINDER

DEPARTMENT OF COMPUTER SCIENCES

COMSATS UNIVERSITY ISLAMABAD, WAH CAMPUS

Ms. Anam javaid

DEPARTMENT OF COMPUTER SCIENCES

1. External Examiner ____________________________

The Most Beneficent

The Most Merciful

PROJECT NAME ONLINE VEHICULAR SERVICES FINDER

STARTED ON NOVEMBER 16, 2018

COMPLETED ON JUNE 10, 2019

COMPUTER USED HP-CORE i5

SOURCE LANGUAGE JAVA, XML

Figure 1 Inheritance Relationship ........................................................................................... 15

Online Vehicular Services Finder

1.2. Scope of this document

1.4. Business Context

1.5. Intended audience

1.6. Primary schedule

2.2. Similar System Information

2.3. User Characteristics

2.4. User Problem Statement

2.6. General Constraints

 Map based dynamic dashboard.

3.1. Create parking:

3.3. Reserve parking:

4.1. Interface Requirements

4.2. Performance Requirements

4.3. Design Constraints

4.4. Standards Compliance

4.5. Hardware Limitations

5.2. Binary Compatibility

6. Preliminary Object-Oriented Domain Analysis:

6.1. Inheritance Relationships

Figure 1 Inheritance Relationship

6.2. Use Case Diagram:

Figure 2 Use Case Diagram

6.3. Class Diagram

Figure 3Class Diagram

6.5. Activity Diagram

Figure 5 Activity Diagram

6.6. Sequence Diagram:

Figure 6 Sequence Diagram for User

Figure 7 Sequence Diagram for Owner

Detecting Internet Connection

7.1. Application User Interface:

Figure 8 Sign up page

Figure 9 Home Screen

Figure 10 Home screen

Figure 11 Parking Map view

Figure 12 parking Map view

Figure 13 Parking Garage Images

Figure 14 parking Reviews

System testing of software or hardware is testing conducted on a complete, integrated system

8.1. Testing strategies

8.2. Black Box Testing

8.3. White Box Testing

8.4. Unit Testing

8.5. Integration Testing

8.6. User acceptance Testing

8.7. Test cases:

8.8. Sign Up/ Register

TC1: Sign Up/register

Test Case ID: 1