American University of Sharjah

Department of Computer Science and Engineering

Smart Parking System

Senior Design Project Presented by:

Bassam Yousuf (ID: 55388)

Saad Khalid (ID:58363)

Ayush Maan (ID:60501)

Supervised by:

Dr. Tarik Ozkul

Date: 19-04-2018

ii

Abstract

The transportation industry is exponentially increasing with thousands of new automobiles

being manufactured every day. With new vehicles on the road every day, parking spots also

become an essential part of the transportation industry. Traffic is induced with the tremendous

amount of cars on the road trying to find parking spots. In order to reduce this traffic, a need for

smart parking system is vital. This smart parking system will allow vehicle users to easily locate

and reserve their parking spots in advance with the help of a mobile application. The system will

have sensors and parking stopper placed on every parking spot. The first attempt was implemented

using the WirelessHART which was then replaced by a cheaper alternative device. The smart

parking system network will be composed of the microcontroller Photons, proximity sensor and

parking stopper. One microcontroller photon will be placed along the parking spots and a

proximity sensor will connected to the photon. The photon will also be connected to the parking

stopper to control it.

iii

I dedicate this work to my parents, my brothers, my sisters and

my family.

Bassam yousuf

I dedicate this work to my parents and my future ambitions.

Saad Khalid

I dedicate this work to my parents and new plans of a start-up

company

Ayush Maan

iv

Acknowledgements

We would like to take this opportunity to thank everyone that has helped and guided us

throughout this design project. Firstly, we would like to thank Dr. Tarik Ozkul for granting us the

opportunity to work with the WirelessHART smart mesh network. In addition, we are also very

grateful to him for being our senior design advisor. Secondly, we would also like to highlight the

role that Dr. Raafat Abu Rukba has played throughout the serious design course. He has provided

us with very helpful strategies to get us started off with our senior design project. Moreover, we

would like to thank Mr Ahmed Nabulsi and Mr Hammam Orabi for taking out his time for

troubleshooting the problems relating to the implementation to our project.

v

Table of Contents

I. INTRODUCTION ............................................................................................................................................. 1

II. PROBLEM STATEMENT AND DESIGN OBJECTIVES .......................................................................................... 2

PROBLEM 1: TRAFFIC GRADUALLY INCREASING ..................................................................................................................... 2 PROBLEM 2: CARBON EMISSION INCREASED ........................................................................................................................ 2 PROBLEM 3: WIRED NETWORK SOLUTIONS ......................................................................................................................... 3 PROBLEM 4: MISMATCH WHILE INSTALLING DEVICES IN NETWORK ........................................................................................... 4 DESIGN OBJECTIVE ......................................................................................................................................................... 5

III. LITERATURE REVIEW ..................................................................................................................................... 8

SENSOR BASED TECHNIQUE FOR SMART PARKING SOLUTIONS: ................................................................................................. 8 RFID BASED SOLUTION FOR SMART PARKING: ...................................................................................................................... 9 SMART PHONE BASED APPLICATIONS FOR PARKING MANAGEMENT SYSTEMS: ............................................................................ 10

IV. SYSTEM/SUB-SYSTEM SPECIFICATIONS ................................................................................................... 12

FUNCTIONAL REQUIREMENTS ......................................................................................................................................... 12 NON-FUNCTIONAL REQUIREMENTS ................................................................................................................................. 13 USE-CASE: .................................................................................................................................................................. 15

V. TECHNICAL APPROACH AND DESIGN ALTERNATIVES ................................................................................... 16

PLANNED NETWORK SOLUTION (USING WIRELESS HART): ................................................................................................... 16 IMPLEMENTED ALTERNATIVE NETWORK SOLUTION (USING PHOTON): ................................................................................... 20 PREVIOUSLY PROPOSED SOLUTION: ................................................................................................................................. 30 IMPLEMENTED SOLUTION: ............................................................................................................................................. 33 APPLICATION OF NETWORK ............................................................................................................................................ 37 SOLUTION ALTERNATIVES:.............................................................................................................................................. 39 SYSTEM ARCHITECTURE ................................................................................................................................................. 40 CLIENT: ...................................................................................................................................................................... 41 MIDDLEWARE: ............................................................................................................................................................. 42 SENSOR NODE: DATA PROVIDER ...................................................................................................................................... 43 ALTERNATIVES: ........................................................................................................................................................ 47

VI. VALIDATION, VERIFICATION, AND PERFORMANCE ANALYSIS PLAN ........................................................ 52

VALIDATION ................................................................................................................................................................ 52 VERIFICATION .............................................................................................................................................................. 53 PERFORMANCE APPLICATION .......................................................................................................................................... 68

VII. PROJECT GLOBAL, ECONOMIC, SOCIETAL IMPACT ................................................................................... 69

VIII. PRELIMINARY COST ESTIMATES .............................................................................................................. 71

PRELIMINARY COST (PLANNED SOLUTION): ....................................................................................................................... 71 PRELIMINARY COST (IMPLEMENTED SOLUTION): ................................................................................................................ 71 DESIGN COST: ............................................................................................................................................................. 71

IX. PROJECT MANAGEMENT ............................................................................................................................. 72

SOFTWARE LIFE CYCLE MODEL ....................................................................................................................................... 72 PROJECT MANAGEMENT TASK SCHEDULER ........................................................................................................................ 73

vi

X. STANDARDS ................................................................................................................................................ 78

XI. LIST OF COMPONENTS ................................................................................................................................. 80

LTP5903CEN-WHR MANAGER .................................................................................................................................... 80 INFRARED PROXIMITY SENSORS GP2Y0A02YK0F: ............................................................................................................ 81 PIR MOTION SENSOR ................................................................................................................................................... 82 PARKING LOCK ............................................................................................................................................................. 82 PHOTON ..................................................................................................................................................................... 82

XII. PROGRESS THIS SEMESTER ...................................................................................................................... 83

XIII. CONCLUSION ........................................................................................................................................... 84

vii

LIST OF FIGURES

FIGURE 1- CARBON EMISSION ........................................................................................................................................ 3 FIGURE 2-MISMATCH PROBLEMS. [5, P3] ........................................................................................................................ 4 FIGURE 3-HART MONITORING AND CONTROLLING ....................................................................................................... 5 FIGURE 4-MANAGER ...................................................................................................................................................... 6 FIGURE 5- USE CASE .................................................................................................................................................... 15 FIGURE 6- MANAGER EXTERIOR .......................................................................................................................................... 16 FIGURE 7-MOTE EXTERIOR ................................................................................................................................................. 18 FIGURE 8- MOTE PINS CONFIGURATION ....................................................................................................................... 19 FIGURE 9- SPARKFUN PHOTON ............................................................................................................................................ 21 FIGURE 10- PHOTON SPECS ................................................................................................................................................ 22 FIGURE 11 - PHOTON PIN MARKINGS .................................................................................................................................... 24 FIGURE 12- PHOTON LED AND CIRCUIT DIAGRAM .................................................................................................................. 29 FIGURE 13- PHOTON MODES .............................................................................................................................................. 30 FIGURE 14- SOLUTION OVERVIEW................................................................................................................................ 30 FIGURE 15- NODE (MOTE) JOINING ............................................................................................................................... 32 FIGURE 16- SYSTEM OVERVIEW ........................................................................................................................................... 33 FIGURE 17-PHOTON CLOUD OVERVIEW................................................................................................................................. 34 FIGURE 18- APPLICATION INTERACTION WITH CLOUD .............................................................................................................. 35 FIGURE 19- CLOUD TO STOPPER .......................................................................................................................................... 35 FIGURE 20 - PHOTON WITH PROXIMITY SENSOR ...................................................................................................................... 36 FIGURE 21- RELAY WITH STOPPER ........................................................................................................................................ 36 FIGURE 22- MOBILE APP INTERFACE ............................................................................................................................ 38 FIGURE 23- PARKING STOPPER ..................................................................................................................................... 39 FIGURE 24 - SYSTEM ARCHITECTURE ........................................................................................................................... 40 FIGURE 25- CLIENT ARCHITECTURE ............................................................................................................................. 41 FIGURE 26- MIDDLEWARE OVERVIEW ......................................................................................................................... 43 FIGURE 27- SENSOR AND DATA PROVIDER NODE OF THE PARKING SYSTEM ................................................................. 44 FIGURE 28- THE DETAILED ARCHITECTURE .................................................................................................................. 45 FIGURE 29- THE PHOTON TO CLOUD CONNECTION WIRELESSLY ................................................................................... 45 FIGURE 30- MOBILE APPLICATION WITH THE NETWORK ............................................................................................... 46 FIGURE 31- INTEGRATED SMART PARKING SYSTEM ARCHITECTURE ............................................................................. 46 FIGURE 32- ISA ARCHITECTURE ................................................................................................................................... 48 FIGURE 33 - MANAGER CONNECTION .................................................................................................................................... 54 FIGURE 34- MOTE CONNECTION .......................................................................................................................................... 55 FIGURE 35- MOTE SEARCHING FOR NETWORK ........................................................................................................................ 55 FIGURE 36- MOTE PHASES ................................................................................................................................................. 56 FIGURE 37- ACTIVE MOTE CONNECTED TO NETWORK ............................................................................................................... 57 FIGURE 38- NETWORK TOPOLOGY ........................................................................................................................................ 58 FIGURE 39- DEVICE MALFUNCTIONS ..................................................................................................................................... 58 FIGURE 40- PING MOTE ..................................................................................................................................................... 59 FIGURE 41- CONNECTED MOTES .......................................................................................................................................... 60 FIGURE 42 -MALFUNCTION IN NETWORK SETUP ...................................................................................................................... 61 FIGURE 43- MOBILE APP .................................................................................................................................................... 62 FIGURE 44- MOBILE APP RESERVATION ................................................................................................................................. 63 FIGURE 45- PARKING RESERVED ........................................................................................................................................... 63

viii

FIGURE 46- STOPPER BEING TURNED OFF............................................................................................................................... 64 FIGURE 47- TESTING SENSOR .............................................................................................................................................. 65 FIGURE 48- PARKING STOPPER DEMO ................................................................................................................................... 67 FIGURE 49- SDLC APPROACH ...................................................................................................................................... 72 FIGURE 50- MANAGER INTERFACES ............................................................................................................................. 80 FIGURE 51- WIRELESS HART MOTE CHIP .................................................................................................................... 81

ix

List of Tables

TABLE 1- MANAGER FEATURES [14, P3] ...................................................................................................................... 17 TABLE 2- MANAGER OPERATING CONDITIONS [14]. ...................................................................................................... 17 TABLE 3- MANAGER INTERFACES [15] .......................................................................................................................... 17 TABLE 4- SERIAL 1 PARAMETERS ................................................................................................................................. 18 TABLE 5- MOTE FEATURES ........................................................................................................................................... 18 TABLE 6- MOTE OPERATING CONDITIONS [16] ............................................................................................................. 20 TABLE 7- MOTE RADIO SPECS [16] .............................................................................................................................. 20 TABLE 8- SPECIFICATIONS OF PHOTON .................................................................................................................................. 24 TABLE 9- GPIO DETAILS..................................................................................................................................................... 24 TABLE 10 - PHOTON CURRENT AND VOLTAGES SPECS ............................................................................................................... 25 TABLE 11 -PHOTON INPUT CURRENT AND VOLTAGES SPECS ....................................................................................................... 25 TABLE 12- PHOTON WIFI SPECS .......................................................................................................................................... 26 TABLE 13- PIN OUT DIAGRAM ............................................................................................................................................. 26 TABLE 14- PIN OUT DIAGRAM ............................................................................................................................................. 27 TABLE 15- PIN OUT DIAGRAM ............................................................................................................................................. 27 TABLE 16- I/O SPECS ........................................................................................................................................................ 28 TABLE 17- PIN SPECS ......................................................................................................................................................... 29 TABLE 18 -CONTROLLING STOPPER ....................................................................................................................................... 37 TABLE 19- ISA AND HART COMPARISON .................................................................................................................... 50 TABLE 20- PRELIMINARY COST .................................................................................................................................... 71 TABLE 21 - COST OF IMPLEMENTED SOLUTION ........................................................................................................................ 71 TABLE 22- DESIGN COST .............................................................................................................................................. 71 TABLE 23- TASK SCHEDULER ....................................................................................................................................... 77

1

I. Introduction

Have you ever had to miss a class or an important meeting because you were looking for a

parking? Have you ever caused traffic jam while looking for parking? Parking is one of the biggest

issues in the UAE due to the enormous amount of cars. Drivers spend most of their time going

around parking lots looking for free parking which causes traffic jam and increases the amount of

CO2 emission into the air. A typical driver on average spends 3.5 to 14 minutes looking for parking.

Even though this time frame seems small, it adds up to a significant amount leading to a loss of

productivity of people who are generally busy. Moreover, circulating vehicles looking for parking

also cause traffic and might even lead to small accidents. It is calculated that 30 percent of cars at

any given time are looking for parking in major cities [1]. For example, if 1000 people are

traversing a relatively large parking lot and on average they spend 15 minutes looking for parking,

this would calculate 250 hours lost in a single parking lot. To overcome this issue, WirelessHART

technology was planned to be used to establish a wireless network that will be used to monitor and

reserve huge outdoor parking spots. However due to the lack of resources relating to the

WirelessHART technology, we faced problems in setting up the network. Once we were able to

setup the network, the next issue we faced was to communicate with the nodes (Motes) due to the

malfunctioning of the nodes (Motes) and the manager. We then implemented our system using a

wireless-based photon network.

2

II. Problem Statement and Design

Objectives

Transportation is one of the biggest concerns globally today. As the population of the world is

increasing exponentially, the transportation industry also needs to adapt to efficient and reliable

smart solutions. According to a study based in Los Angeles, it is said that 30 percent of urban

traffic is caused by motorists trying to look for parking. Locating parking spots is a very time-

consuming process due to the tremendous amount of vehicles on the road. Not being able to locate

a parking spot will further stress traffic situation in that area, therefore, there is an urgent need for

smart parking system.

Problem 1: Traffic gradually increasing

Civilians spend a lot of time on the road in trying to find vacant parking spots. Due to this

increased time they spend on the road, traffic gradually increases. Moreover, consequences of

traffic contributes towards loss in revenue which makes the transportation industry inefficient and

costly. It makes it inept because as traffic is generated, it causes hindrance to all other

transportation vehicles as well. In addition, due to this disruption the society also gets distressed

and the road rage increases in that society.

Problem 2: Carbon Emission Increased

“A study by UCLA economist and urban planner, Donald Shoup, found that in a 15-block

area of Westwood, cruising for parking generates 950,000 excess vehicle-miles of travel, wastes

47,000 gallons of gas, 100,000 hours and produces 730 tons of greenhouse gas carbon dioxide per

year” [2]. Due to the increase in traffic, a lot of motor vehicles are either static or are moving in

3

very slow speed on the road. Thus, traffic has caused an increase in the time the motorists spend

on the road. This increased time leads to more carbon emission which is one of the major causes

of global warming. According to EPA (United States environmental protection agency) estimates

that CO2 Emissions from a gallon of gasoline: 8,887 grams CO2/ gallon [3]. In addition, the figure

1 below shows that the road transport contributes to around 15.9% of the global warming.

Figure 1- Carbon Emission

Problem 3: Wired Network Solutions

Wired solutions means cabling and installing of the devices across several points within

the parking spots. This is a very time-consuming and an error-prone solution as it requires a lot of

effort in laying out wiring for every parking spots. When implementing these kind of wired systems,

on average about 70% of cost of the system comes from wiring [4]. Moreover, these solution

usually have a single point of failure, meaning that if the wire deteriorates or is cut due to some

4

unusual and unavoidable circumstances, the device connected to that wire will not be connected

to the network anymore.

Problem 4: Mismatch while installing devices in network

While installing and configuring devices (nodes) in the real-time network, some issues that

occur within the network are hard to detect. To provide a better understanding of the matter, let’s

assume a switch-switch connection being installed. In the situation when one switch is installed

and configured to operate in full-duplex mode while the other is configured to operate in half-

duplex mode, one switch sends information to the other switch, the other switch also transmits

data simultaneously. This will cause a collision in the network, thus making the network appear

slow.

Figure 2-Mismatch problems. [5, p3]

5

Design Objective

Highway Addressable Remote Transducer (HART) is a technology used to control smart

devices through analog and digital signals. This protocol is technically a hybrid of analog and

digital industrial automation [6]. Ever since the discovery of radio signals, the need to control,

measure and communicate through them has been the priority of the networking industries.

Previously, the controlling systems would use pure analog systems that would not be accurate.

However, the HART technology uses both analog and digital signals making the data received and

transmitted more accurate. This convenience of sending analog and digital signals has led to the

success of the HART technology making it a standard protocol. Since HART is a hybrid

technology, there is always an issue for interference between the analog and the digital signals.

However, the digital signals will not affect the analog signals because both signals are filtered

using a standard filtering technique making them independent of each other [7]. The figure 3 below

shows how a HART device is being used to control and monitor the I/O sensors.

Figure 3-HART Monitoring and controlling

The figure above show cases the wired HART solution. The second type is the wireless

HART, which is the latest technology in the industry because it enables the users to control and

monitor, signals wirelessly. Wireless HART is an advanced technology, which is compatible with

6

the current HART devices making the stepping up of the system easy and quickly to implement.

It is the first fully developed high robustness device that can be used under rough conditions and

harsh environment. The wireless HART technology offers many elements that can be used in the

real time smart parking networks. The main elements that are related to this project are field

devices, access points, motes (gateway) and a secured networking manager.

Since the world is moving towards smart cities, the team decided to implement smart mesh

wireless HART network to improve the parking system. The smart mesh network uses self-

forming high scalable wireless nodes that are called motes [8]. Motes are low powered devices

that are used to route, source and terminate data. The motes are controlled and navigated by the

highly secured manager device. The manager device is directly connected to a computer where it

will be given commands to control the network wirelessly. The vision of the team is to provide a

smart solution for parking that work under harsh conditions making this a step forward to a smart

city.

Figure 4-Manager

7

Due to complication being faced with the WirelessHART setup and lack of resources we moved to a

Photon based network. The particle photon is a microcontroller that has several GPIO. These GPIO can

take both Analog and digital inputs. The particle also capable of outputting a digital and analog signal. The

particle is equipped with 12 bit resolution ATD (Analog to digital converter). Since the particle has the

functionality to manipulate both analog and digital signals. We used the photon to implement the smart

parking system. Sensors and actuators are connected across the photon. These sensors will comprise of the

proximity sensor along with a parking stopper which will act as an actuator. A better understanding of the

detailed overview of the system is given in the technical approach. Section 5 of this report.

8

III. Literature Review

Sensor based technique for smart parking solutions:

Nowadays, everything is moving towards the smart technology and for a city to be smart

it should also have a smart parking system to reduce traffic. A sensor-based system would help in

building a program that would enable drivers to find parking easily. This technique works by first

sensing whether the space of the parking is available or not. The sensors are embedded on the

ground and the pressure exerted on the sensors detects the availability of space [9]. The sensors

were embedded in the ground so that they would be “immune from the drastic environmental

changes and less prone to damages caused by it” [10]. Once the sensor detects a movement it will

a signal through an LED light that would turn green to show for an empty space and will turn red

to show for an occupied parking space. Likewise, Mondal et al had a similar approach of making

a smart parking system [10]. They share the same point of view when it comes to making a smart

city. Mondal et al used wireless sensor networks (WSN) and small-embedded systems for

communication. Moreover, sensors play an important role in detecting readings, which highly

impacts the smart parking system; however, it has its advantages and disadvantages.

Advantages:

Detecting of free parking spaces will reduce traffic and save the driver’s time as well as

fuel consumption of cars would dramatically decrease.

Businesses can use this technique to store the data of the occupied parking spaces for future

planning. Moreover, they can use the data for pricing of different car parking areas and can

increase their profits accordingly

9

According to Mondal et al, using the sensor based technique, the CO emission would drop

since cars will not be used much because the traffic and waiting time for searching parking

would decrease [11].

Disadvantages:

The driver will not be allowed to make a reservation so there might be issues if many

people see the same empty parking space

LEDs that will be used to show an empty space will fail in harsh conditions and will not

last throughout different weather conditions.

A very cheap method to implement such a system. Sensor and wire life will not last more

than two years

RFID based solution for smart parking:

Radio Frequency Identification (RFID) is used for tracking and monitoring devices in the

world of Internet of Things. Since RFID is used to identify specific IDs, this technique uses an

antenna to retrieve the IDs of cars from a microchip. Zhang et al define RFID to be a

communication method that can be used to locate objects with distinct IDs [12]. This research and

technique has its advantages but can only be used in small areas like compounds, universities and

offices. Users can submit the ID of their car to the administrator of the system and the ID will then

be stored on the microchip attached to the RFID tag. Once the drivers have their own RFID tags

they can use it to access the parking lot. This will help the system to monitor the amount of cars in

the parking lot and will know exactly how many car spots are free at any given time. This solution

is reliable but lags in time when reading the ID cards and updating the LEDs.

10

Active RFID tag: This type of tag has its own battery and ID, which can be detected from a

relatively long distance (10 meter). Zhang et al used these tags because it “allows flexibility in

applications such as asset supervision and management” [12].

Smart phone based applications for parking management systems:

Grazioli et al researched on managing parking systems using mobile and web applications,

which is related to the smart parking system [13]. This method was made to generate revenue and

make car parking more secure. The applications would allow users to reserve a parking spot and

they would be able to monitor their car from the application at any given time. Likewise, our

team’s idea will implement a mobile application that would allow user to reserve parking or look

for any available parking. However, it would not allow users to monitor their car since this smart

system should be applicable to large areas where monitoring using cameras would not be

economical.

Advantages:

Real time monitoring of cars at any given time

Reservation of available parking at any time of the day or night

Secured method where drivers will not spend time looking for car spaces and will feel

secure since they can check on their car at any time

Disadvantages:

Mobile applications alone are not enough since they lag and can have bugs that would cost

the drivers major issues

11

Not completely a smart system since it will use a person to monitor cars through CCTV

devices

This solutions durability is relatively inferior to the HART technology.

12

IV. System/Sub-System Specifications

Functional Requirements

FR 1. The system should use Photon to connect the sensors.

FR 1.1. The proximity sensors should be connected to the photon.

FR 1.2. The photon will be gathering data from the proximity sensor and uploading it

to the particle cloud

FR 1.3. The cloud should be accessible by the mobile application

FR 2. The mobile application should allow users to look at parking spots and reserve.

FR 2.1. The mobile app should show the user the map of the area.

FR 2.2. The mobile app should show in colour coding the available parking spaces in

an area.

FR 2.2.1. Green for vacant spots

FR 2.2.2. Red for taken/unavailable spots

FR 2.2.3. Grey for reserved spots

FR 2.2.4. Blue of handicap/emergency parking

FR 2.3. The user can search for available parking spaces in any particular area.

FR 2.3.1. The user should be able to view the parking spaces and its information such

as location.

FR 2.3.2. There should be 2 searching modes available for different types of users.

2.3.2.1 The user should be able to search through the text mode i.e. the areas

name via a text search.

13

2.3.2.2 The second one is through the map view mode, which is integrated with

the google maps.

FR 2.4. The user should be able to view the details of a selected parking area such as

the number, price per hour and available slots.

FR 2.5. The mobile application will notify you about any empty parking spot near the

end user if the service is turned on.

FR 2.6. The user should be able to reserve any available parking spots but at most one.

FR 2.6.1. The person should be able to reserve the parking for given number of

hours.

FR 2.6.2. The payment can be made at the entry of the parking or through the

application.

FR 2.6.3. The parking stopper on the associated parking is raised upon any

reservation made.

2.6.3.1 The parking stopper should open when the end user who reserved the

parking spot arrives at the parking location.

FR 2.6.4. The application should also notify through a message or notification when

the parking is going to expire.

Non-Functional Requirements

NFR 1. Performance

NFR 1.1. It should ensures uninterrupted data communication as the information is

very time-critical.

NFR 1.2. It should also work in environment with large signal interference.

14

NFR 1.2.1. It should find its way around and reconfigure to fix any temporary or

small obstacles.

NFR 1.3. There should be stable internet connection which is required to use the mobile

application and photon.

NFR 1.4. The application will provide a user enhanced interface such that the user

should be able to reserve the spot within 1 minute.

NFR 2. Security.

NFR 2.1. It should provide a very robust, multitier system which is not affected by

harsh environments.

NFR 2.2. It should provide a 128-bit AES encryption industry standard.

NFR 2.3. There is a unique encryption key for each message.

NFR 2.4. The system should provide data integrity and device authentication.

NFR 2.5. The encryption key should be rotated for high level of security.

NFR 2.6. It should change channels whenever needed or on a timely basis (Channel

hopping) for enhances security.

NFR 2.7. It should inform the system if any device not replying or communicating.

NFR 2.8. It should be very safe from Wi-Fi Internet attacks.

NFR 3. Availability.

NFR 3.1. The system should be available all the time with real time availability status.

NFR 3.2. The system should be easily available to the end users.

NFR 3.3. The server should be able to handle concurrent requests from multiple end

users at the same time.

15

NFR 4. The central repository or the server should not be dependent on any platform so that

it is easily accessible by any application.

Use-case:

Figure 5- Use Case

16

V. Technical Approach and Design

Alternatives

Planned Network Solution (Using Wireless Hart):

The network solution is going to consist of the following network devices

LTP5903-WHR SmartMesh WirelessHART Manager

DC9003A-C SmartMesh WirelessHART Evaluation/Development Mote

LTP5903-WHR SmartMesh WirelessHART Manager provides core networking functionality.

In addition it enables the network to achieve high reliability and scalability along with security

features. Moreover this device also acts as a gateway

that connects the network to the operator/user of the

network. The figure 6 displays the exterior of the

manager. The Table 1 is given below to further describe

the manager’s benefits and features.

Figure 6- Manager Exterior

17

Table 1- Manager Features [14, p3]

The table 2 below gives the normal operation conditions of the device.

Table 2- manager operating conditions [14].

The manager consist of the following hardware interfaces as shown in Table 3.

Table 3- manager interfaces [15]

The serial 1 interface has the following properties given in the table 4 below

18

Table 4- Serial 1 parameters

DC9003A-C SmartMesh Wireless HART Evaluation/Development Mote are wireless

nodes which have the capability to act as routers. These motes feature a highly integrated, low

power radio design by dust networks. The figure 7 given below shows how a mote looks like.

Moreover, the table 5 below shows some of features of the mote device.

Table 5- Mote features

Figure 7-Mote Exterior

19

The figure 8 below gives the pin layout for the mote [16]. This pin layout shows that the

mote can take several inputs at a time. The GPIO in the figure 8 are general purpose input and

output pins which are can take digital inputs. The AI_0 (15-19) only take analog inputs which are

read by the mote. Therefore, this mote can take any kind of sensor input type. Lastly the motes

shows that there are multiple communication interfaces as well.

Figure 8- Mote Pins configuration

20

The table 6 below gives the operating conditions for the mote.

Table 6- Mote operating conditions [16]

The table 7 below gives the radio specifications of the mote.

Table 7- Mote Radio Specs [16]

Implemented Alternative Network Solution (Using Photon):

The network solution consists of the following network device:

SparkFun Photon RedBoard - DEV-13321

The SparkFun Photon RedBoard is an over-the-air-programmable WiFi advancement board

that is integrated with the Particle cloud. At the core of the Photon RedBoard is the Particle's P1

module, which packs an ARM Cortex M3 processor and a Broadcom WiFi controller into a solitary

21

chip. The I/O, USB and power connectors are altogether broken out to a well-known Arduino

shape.

Beside the frame factor, the Photon RedBoard is almost indistinguishable to a Particle

Photon: same microchip, a RGB LED to show availability or different states, RESET and MODE

options to configure the chip.

The figure 9 below shows the SparkFun Photon RedBoard.

Figure 9- Sparkfun Photon

Major Features:

Particle PØ Wi-Fi module

o Broadcom BCM43362 Wi-Fi chip

o 802.11b/g/n Wi-Fi

o STM32F205RGY6 120Mhz ARM Cortex M3

o 1MB flash, 128KB RAM

On-board RGB status LED (ext. drive provided)

18 Mixed-signal GPIO and advanced peripherals

Open source design

22

Real-time operating system (FreeRTOS)

Soft AP setup

FCC, CE and IC certified

Particle Photon and the SparkFun RedBoard together make up the Photon RedBoard. The

figure 10 below shows each and every component on the board.

Figure 10- Photon specs

The major board components are discussed below:

External Supply: Power Supply Voltage between 4.5-15V.

LEDs

o Power: RED LED indicates power.

o RGB: LED displays the connection states of the Photon: connected, connecting,

or in breathing mode.

23

o D7: Photon’s D7 pin is attached to an inbuilt LED for debugging purposes.

Headers

o Power: GND, 3.3V, USB voltage (~4.8V), supply voltage (VIN).

o Analog: Six analog-to-digital (ADC) pins.

o 8-pin Digital: Digital pins D2-D7 (RX & TX).

o 10-pin Digital: Digital-to-analog output (DAC) – along with SPI and I2C

interfaces.

Buttons

o Reset: The reset button can be used to re-start the Photon module.

o Mode: To switch between running, safe, listening, and breathing modes.

USB Connector: Used to power the Photon RedBoard. It can also be used as a serial data

interface.

JTAG Header: The 20-pin JTAG header.

The Memory mapping overview of the Photon is discussed below:

Bootloader (16 KB)

DCT1 (16 KB), stores Wi-Fi credentials, keys, mfg info, system flags, etc..

DCT2 (16 KB), swap area for DCT1

EEPROM emulation bank 1 (16 KB)

EEPROM emulation bank 2 (64 KB)

Device OS (512 KB) [256 KB Wi-Fi/comms + 256 KB hal/platform/services]

Factory backup, OTA backup and user application (384 KB) [3 x 128 KB]

24

The Physical Layout specifications are shown in the table 8 below:

Table 8- Specifications of photon

The table 9 below shows GPIO specifications including ADC & DAC ports.

Table 9- GPIO details

The figure 11 below shows the Pin markings of the Photon.

Figure 11 - Photon pin markings

25

The tables 10 & 11 below shows the absolute and recommended power operating conditions:

Table 10 - Photon current and voltages specs

Table 11 -Photon input current and voltages specs

26

The table 12 below shows the WI-Fi Specifications:

Table 12- Photon WIfi specs

The table 13, 14 and 15 below shows the PIN OUT diagrams for the Photon:

Table 13- Pin out diagram

27

Table 14- Pin out diagram

Table 15- Pin out diagram

28

The table 16 below shows the input output pin characteristics:

Table 16- I/O specs

The way some of the channels are multiplexed, some pins may have more than one

variable name that you can use in your code interchangeably. Input/Output Pins specification is

shown in the table 17 below:

29

Table 17- pin specs

The status of the photon LED (& its location) are shown in the figure 12 and 13 below:

Figure 12- Photon LED and Circuit diagram

30

Figure 13- Photon modes

Previously Proposed Solution:

This project is focusing to make reliable wireless sensor network that relays data across

every node in real-time. Each parking spot will be equipped with a sensor which checks for parking

space and a parking stopper. The figure 9 below gives a better demonstration of how the system

will work.

Figure 14- Solution Overview

31

Real-Time Network

A number of fieldbus techniques are already being used in several industries. Fieldbus is

one of the protocols which is used for real-time industrial networks. In our system, along with field

bus protocol we are using the HART protocol. HART uses both analog and digital transmission

coherently without any interference between the two making this protocol one of the best method

of communication in harsh and noisy conditions. HART protocol is very intelligent because

“HART is characterized not to interfere with the (4 ~ 20) mA analog signal while allowing two-

way digital communications” [17].

As mentioned before, while implementing Real-time industrial networks, 70% of the cost

lies with the wiring and cabling of the network. Thus to reduce this cost, a wireless HART protocol

can be employed with several wireless motion sensors that will exchange data real-time within the

network. By deploying this protocol/network, we will solve a major problem faced by wired

solutions. This project focuses on the Smart mesh wireless HART network which is a topology

that makes it very reliable and highly inter-connected. Smart mesh technology is a connection

layout in which motes are inter-connected to each other wireless. Moreover, all these motes acts

as routers that can transmit and receive simultaneously. WirelessHART protocol makes it very

easy to add new devices to the real-time industrial network. A representation of the wireless HART

network is given in the figure 10 below [18].

32

Figure 15- Node (mote) Joining

This further highlights the fact that a single point of failure network does not exist in

Wireless HART. The term smart is concatenated in smartmesh because motes self-configure

themselves whenever the mote detects some kind of hindrance. For example if any obstruction

such as noise signal interference affects the connection between the two motes, the motes will self-

configure themselves to a different frequency or they will route the data through the other motes

within the network.

Since the motes are a self-configuring, self-automated and optimized network devices the

mismatch issue is also solved by the network itself. Consequently, the uptime and throughput of

the network is optimized. This optimization makes the network very reliable and trustworthy.

33

Implemented Solution:

The microcontroller photon can be used to act as a manager in the smart parking system.

However, the photon can only accommodate 5-10 sensor readings at a time including input and

output. Thus for large parking lots, many photons will be required that will need to be inter-

connected to each other. The figure 16 below gives a better demonstration of how the system will

function.

Figure 16- system overview

Network Nodes

As a part of Internet of Things applications, Particle allows users to register Particle

“variables” and Particle “functions” which makes it possible to securely access and control photons

via HTTP requests. This also enables users to interface the Photon with other platforms that support

HTTP communication such as Raspberry Pi interface with the photon. Photon’s available variables

34

and functions are sent to Particle server through WiFi. Particle server registers Photon’s

information Such as the ID address & Access Token. User queries the server for Photon’s

variables, or controls Photon’s output through HTTP requests such as get or post using the URL

+ ID + Access Token of the photon.

Sensor Values to Particle Cloud:

The photon reads the digital value from the proximity sensor and updates it in the cloud using the

particle.variable () method.

Figure 17-Photon cloud overview

Particle Cloud to Mobile Application:

The main screen of the available parking spots retrieves the data from the particle cloud. It

uses the variable saved by the photon into the cloud using the particle.variable () method. The URL

is created by using the access code and device ID retrieves the value/result of the data from the

cloud.

Device ID: XXX

Variables: XXX

Particle Server

35

Figure 18- Application interaction with cloud

Mobile Application to Particle Cloud to Parking Stopper:

The mobile application publishes the value on to the cloud using the particle.function (). This

published the value on the parking stopper and hence activates the parking stopper to reserve the

parking.

Figure 19- Cloud to stopper

36

Proximity Sensor to Photon:

The proximity sensor is connected to the photon on the Digital Input port and the photon publishes

the same value on the cloud.

Figure 20 - photon with proximity sensor

Photon to Parking Stopper:

The digital output of the Photon is connected to the relay. The two digital output connected to the

relay are used as controller to supply 0, +6 and -6 Volts respectively.

Figure 21- relay with stopper

The table 18 below shows the controlling of the parking stopper:

37

D7 D6 Voltage

supplied

Motor Turning Direction

1 x 0 Stays in the same state

0 1 6 Motor turn parking stopper Down

0 0 -6 Motor turn parking stopper Up

Table 18 -controlling stopper

The control lines signals decide if the parking stopper should go up or down depending

upon the voltage supplied from the relay. The Photon used 5 V USB input while the Parking

stopper operates from +6, 0 & -6 Volts. The photon gives the control signals using the

particle.function () method initiated from the mobile application. The +6, 0 and -6 volts in the

connection shown below is supplied by the power supply but can be easily replaced by batteries.

Also, the power supply of 5V of the Photon can be easily replaced by a battery in a futuristic

solution.

Application of network

By implementing this real-time network of wireless HART or Photon, we plan to use this

network by connecting several wireless sensors deployed in every parking spot. Moreover, this

network will contain a manager that will also communicate, control and reconfigure any of the

wireless sensors (motes). These wireless sensors will provide a continuous flow of data to increase

efficiency, leading to reduced downtime and enhanced data integrity.

In addition, we also plan to use the above network to allow the driver to easily locate vacant

parking spot and reserve them if required. We plan to provide this functionality through the mobile

application. The figure 11 below gives a better understanding on how the application interface may

38

look like. The figure shows a green block with ‘7F’ which means 7F is vacant parking spot. Blue

means the that spot is filled and light grey means the parking spot has been reserved.

Figure 22- Mobile app Interface

The app will provide the driver to quickly locate empty parking spots. This will reduce the amount

of time the driver traditionally used to spend in trying to find a parking spot. Additionally, the

application will also allow drivers to reserve empty parking spots. Once a parking spot has been

reserved, a parking stopper will be erected which will not allow other cars to park in that spot. The

figure 23 below displays a kind of stopper that will be used.

39

Figure 23- Parking stopper

Lastly, this smart parking mechanism will reduce traffic that is generated due drivers trying to find

parking spots. Consequently, carbon emission will also be reduced along with the road rage.

Solution Alternatives:

Raspberry pi based approach: Using this approach, the microcomputer raspberry will act as the

network manager. Multiple sensors that are placed in the parking spots can be connected to the

raspberry pi, however, a single raspberry pi can only accommodate 17 sensors at a time.

Moreover, by using this approach we will have to use a wired approach which turns out to be

a very costly and time-consuming process. ZigBee protocol can be used with the raspberry pi

which will make it a wireless approach. ZigBee devices can be integrated with the raspberry

pi, however ZigBee devices do not have the capability to communicate in long distance

situations.

40

System Architecture

In our smart parking system, we have divided our complete project into 3 parts. The

architecture of the project is divided on the basis of key characteristics each component follows.

We have divided our architecture into following components:

The Client

The Middleware

The Parking service Node

Customers or end users have a view of just the client which is the mobile application. In this view

of the mobile application has to choose between options of viewing, searching or reserving the

parking. The client acts as a gateway between end users and the system. The figure 24 below shows

the design of out architecture from a high level view.

Figure 24 - System Architecture

41

Client:

The client of the system uses mobile phones as the easiest way to access this system. The

system is connected through internet which can be a 3G, 4G LTE network or by using the Wi-Fi.

Since, this is a mobile phone based application, the phone hardware manages all the capabilities

and functionalities of our app based on the design [19].

The client here as shown below is a mobile application which is android iOS based. The front

layout of the mobile application is based on the XML layout while the backend is designed using

the java programming language.

The client is connected to the firebase database, this is the component the mobile application uses

to retrieve all the information about the parking. The figure 25 below shows our client architecture.

Figure 25- Client architecture

42

Middleware:

This is the zone where the client interfaces with the database and the wireless sensors

integrate with the parking service providers. The database being used in our architecture is the

firebase database provided by google. We are using this database as it can be easily integrated with

our mobile application. As the software which we are using for the development of this project,

the android studio can be easily used with the firebase and is very easy to maintain.

All the data being used in this project is being easily synchronized using the middleware, and

whenever needed more components can be added. The integration would be very easy if in future

we plan to make a website for the same project. The figure 26 below shows our middleware

architecture.

The main purpose of using the middleware design is to increase reusability and ensure quality of

the data. The middleware component in itself provides us with many beneficial features such as:

Multiple hardware components can be connected to the middleware.

Different hardware component can perform different functionalities and have different

features.

We can interface our middleware with different applications at the same time.

Makes integration easier with new or changes hardware components.

It makes processing of the data from the components easier and follows similar protocols

for all communications.

43

Figure 26- Middleware Overview

Sensor node: Data provider

The sensor node and the provider is the crucial part of this project. These are the sensors

which are placed on the site and collect data about the availability of the parking site. These sensors

which are connected to the photon read the data and pass it on to the photon. The photon transmits

the data to the particle cloud wirelessly which forwards the data to the server which is connected

to the database.

44

The figure 27 below shows the architecture for our node.

Figure 27- Sensor and Data provider node of the parking system

Our sensor and data provider node consists of following parts:

Many Sensors (proximity sensor)

Photons

Particle photon cloud server

The figure below shows the detailed architecture of the sensor nodes. We can connect all the

photons and sensors as shown in the figure 28 below.

45

Figure 28- The detailed architecture

The figure below shows how a photon can be connected to the same particle cloud [15]. This kind of a setup

requires the use of an internet connection to be connected to the cloud. The microcontroller takes the sensor

values and transmit it wirelessly from the photon to other photons if need be through the particle cloud.

Figure 29- The photon to cloud connection wirelessly

46

The figure 30 below shows how the photon gets the value from the sensor and gives it to the cloud

and the mobile application also receives it in real time. The mobile application can also modify the value

in the cloud.

Figure 30- Mobile application with the network

The figure below show the whole system integrated together and gives the real life view of the planned

architecture [20]. The webserver and database in the figure below will be our particle cloud.

Figure 31- Integrated smart parking system architecture

47

ALTERNATIVES:

Networking design alternatives:

Technology advancement has forced developers to develop other smart devices that can be

used to decrease the overall cost that is wasted while searching for parking. Wireless HART being

the team’s priority has other competitors too with their own specifications. The competitors are

listed below with their advantages and disadvantages and why the team selected to choose the

wireless HART.

ISA 100.11a:

ISA 100.11a is developed by the well-known company called International Society of

Automation. The ISA technology is based on a wireless network that uses routers, control system,

system manager, security manager and gateways. The ISA network supports the IPv6 protocol that

can be used in many important topologies like star, mesh, star-mesh topology. The protocol used

with the ISA technology only provides the users with the tools of constructing an interface;

however, it does not specify a process automation interface to an existing protocol [21]. The figure

32 below shows the architecture of ISA 100.11a.

48

Figure 32- ISA architecture

OSI Layer Functions of ISA 100.11a Functions of Wireless

HART

Application Layer ISA 100.11a has no

process control application

layer to work with.

Uses the HART

application layer. It has a

reliable management and a

host system

Transport Layer End to End security

Follows UDP’s

connectionless

service

Reliable

connectionless

service

Can ask the

transmitter to

49

Enhanced message

integrity check

retransmit lost

packets

End to end security

Network Layer IPv6 is used for

end-to-end routing

Forwards the data

packets to

destination

according to the

DLL header (mesh

under)

Provides end-to-

end data integrity

Moving the packets

within end-to-end

in the wireless

network

Route tables are

used to choose the

best data paths for

communication

Data Link Layer Supports the

creation,

maintenance and

the forwarding of

packets

Recovery of loss

packets

Channel hopping

Uses Graph routing

that provides

Synchronized

frequency hoping

Time division

multiple access that

provides no

collisions during

communication

Super frame that is

used to group

consecutive frames

50

different data paths

for different type of

network traffic.

Uses a configurable

time slot for

transmitting data

during given time

slots

Offers the idea of

blacklisting

channels that have

a lot of interference

Uses a 10 ms slot

time

Physical Layer The physical layer is based

on the IEEE 802.15.4-

2006 2.4 GHz DSSS

The physical layer is based

on the IEEE 802.15.4-

2006 2.4 GHz DSSS.

Additional physical layers

can be added with the

evolution of the radio

communication technology

Table 19- ISA and HART comparison

The table above shows the functionalities of both Wireless HART and ISA 100.11a at every

layer. As shown above, the ISA 100.11a has no application layer; however, wireless HART

provides its own application layer to the user called the HART 7 for a user-friendly interaction.

The biggest win of wireless HART over ISA 100.11a was the idea of creating super frame. The

concept of super frame is basically the grouping of consecutive time slot packets in to a big frame.

Wireless HART technology also has a channel-blacklisting format that black lists all the channels

that had interference previously and tries to reduce the usage of those channels to make the

51

communication on the network error-free. Furthermore, users can build upon the wireless HART

physical layer, which gives them more options with different methods of low level communication.

ZigBee:

ZigBee is a standard of the ZigBee Alliance that is an organization that maintains and

supports advanced radio communication protocols. ZigBee is a low budget and low power

consumption wireless communication protocol that is normally used for home automation. It

provides the users with a secured and scalable network over small distances; however, the battery

life of ZigBee is only up to two years, which already makes it somewhat useless in the automation

of parking system since that would need a system with a long battery life. ZigBee provides a

secured solution for automation but fails when it comes to large automation since a parking system

will be based on a tremendous number of parking spaces thus being at an economic loss by the

reliability of the protocol. ZigBee has a low level of robustness, which is one of the main factors

in the smart parking system since it would be connected in rough conditions. Moreover, it has a

high power consumption which compared to wireless HART is an issue since this project is related

to using a low power consumption solution at making a smart industry. The biggest issue faced

after the power consumption would be using a secured network. Wireless HART provides security

of data in the transport and the data link layer. However, ZigBee does not have a mandatory

security. Lenvall et al. say that the “MAC layer security available through 802.15.4 is not explicitly

addressed in the ZigBee standard, and its use might break interoperability between different

vendor’s products” [22]. These factors led the team to choose wireless HART over the ZigBee

protocol.

52

VI. Validation, Verification, and

Performance Analysis Plan

Validation

Validation in any system that is under development is key in order to make sure that the

system meets the user’s requirements. We plan to interview several drivers in the UAE that face

the problem of finding parking spots. These interviews will be very helpful as it will aid us during

development of the mobile application. We want the mobile application to be very user friendly in

the process of locating and reserving a parking spot.

User Acceptance testing:

The team has decided to conduct a user acceptance testing on the smart parking system.

This will be done in order to get real feedback from the end users of the system. We will be

measuring the user acceptance test on following parameters

1. Performance

2. Correct functionality

3. Usability

4. Scalability

53

Verification

Black-Box testing:

Black-box testing is testing method that test the high level functionalities of the application

without focusing or paying attention to the internal structure of the system. Black-box testing is a

kind of verification testing in which the team can determine if the system actually performs what

it is supposed to perform. We will be conducting a survey after the system has been developed.

The survey will be handed out to beta-testers who will evaluate the system. The survey will be

composed of questions based on the high-level functionalities of the system.

White-Box Testing:

In white box testing we will be testing the internal structure of the system. White-box is

another kind of verification testing. In this testing we will be performing several test cases to make

sure that the internal system is functioning and giving the correct output from the required devices.

An example of the test case will be testing the sensor output of the parking spots. We will be

examining those outputs to determine whether those are the desired outputs or not. We will also

be doing creating flow-charts and be conducting algorithmic testing on the mobile application

program.

54

Testing:

Figure 33 - manager connection

As shown in the figure 33 above, we are trying to connect to the manager through the serial

port COM38 and we fail since there are random values shown on the screen. These are one of the

many malfunctions we faced during working with the WirelessHART device.

55

Figure 34- mote connection

In the figure 43 above, we are trying to connect a mote to the manager. To do this, the mote

sends a join command asking to join the network. Once the mote sends such a request, it goes in

to the idle state and starts searching for the network.

Figure 35- mote searching for network

Mote is searching for the network as shown in the figure 35 above.

56

Figure 36- Mote phases

Once the searching step is completed, the mote moves to the negotiating phase and then the

connected phase. Finally once the mote is ready to operate, it moves to the operational phase.

57

Figure 37- Active mote connected to network

As you can see in the figure above, the mote is active and is connected to the network. The

manager can now send data to the motes and vice versa.

58

Figure 38- network topology

The topology viewer shows us how the motes are connected to the manager and currently

the diagram shows that two motes are actively connected to the manager thus creating a

WirelessHART network.

Figure 39- device malfunctions

As you can see the device starts malfunctioning once you try to connect to receive data

through the manager. Once you try to receive data from the manager, the system does not allow a

connection.

59

Figure 40- ping mote

In the figure 40 above, we are trying to ping a mote in the network using the manager and

as you can see we were successful in pinging the active mote which shows that the mote is alive

in the network.

60

Figure 41- connected motes

The above figure 41 shows the connected motes in the network and currently two motes were

operational excluding the manager thus this testing of checking the connected motes is successful.

61

Figure 42 -malfunction in network setup

At one point, we also failed to setup a network. The figure above shows how even though

everything is green and working the system is malfunctioning and not setting up a network.

62

Testing the mobile application:

Figure 43- mobile app

The green spot shows available parking and the red spaces show taken parking. Once the user

selects the green parking it will take the user to the next page and will ask the user to select a

reserving option of the parking, which will reserve a parking for the user by enabling a parking

stopper.

63

Figure 44- mobile app reservation

Using this activity, the user can select the option to enable or disable the parking stopper and once

the user selects to turn it on (to reserve the parking), it will reserve the parking for that user until

the user comes and parks there.

Figure 45- parking reserved

64

The image above shows that the parking is reserved.

Figure 46- stopper being turned off

Once the user reaches the parking it can choose to disable the parking stopper so that the user can

safely park in the reservation area.

Code to read the value from the proximity sensor:

int x=0 ;

int led2 = D7;

int sens =D6;

void setup() {

pinMode(sens, INPUT);

65

pinMode(led2, OUTPUT);

particle.variable(“car”,sens);

}

void loop() {

x=digitalRead(sens);

digitalWrite(led2, x);

}

Figure 47- testing sensor

The figures above show that once there’s no car the LED is off and once there’s a car in the

parking, it will turn the blue LED on and send the sensor value to the cloud so that the mobile

application can retrieve the value and use it accordingly.

Once the proximity sensor gives a value it will send it to the mobile application through

the cloud:

66

if(colorid==-10053376)

{

Intent i=new Intent(getApplicationContext(),reserve.class);

startActivity(i);

}

Code to read the value and control the parking stopper accordingly:

int d7 = D7;

int d6 = D6;

void setup() {

pinMode(d6, OUTPUT);

pinMode(d7, OUTPUT);

Particle.function("online", local);

}

void loop() {}

int local(String command)

{

if(command == "on")

{

digitalWrite(d7, LOW);

digitalWrite(d6, LOW);

delay(2500);

67

digitalWrite(d7, HIGH);

return 1;

}

else if (command == "off")

{

digitalWrite(d7, LOW);

digitalWrite(d6, HIGH);

delay(2500);

digitalWrite(d7, HIGH);

return 0;

}

else {return -1;}

}

Figure 48- parking stopper demo

68

The figure 48 above show how the parking stoppers work according to the reservation

methods selected by the users through the mobile application.

Performance Application

In order to test the performance of the smart parking system, we asked random people from

AUS to come and use our system. We told them the basics of the system and what it allows the

users to do. Like mentioned previously in the senior 1 report, we managed to ask 10 people to use

the system and reserve parking spots (theoretically) and they all managed to do so with no issues

at all. The Smart parking system is just a three click reservation system where the user can reserve

a parking in just three clicks. Performance wise the application that we created is fast and the test

users had no issues using it.

69

VII. Project Global, Economic, Societal

Impact

Smart Parking system developed using the wireless HART network would have a great

impact on developed cities that have a high numbers of cars. A research conducted by Dowling et

al showed that in Los Angeles on a 15-block district, 8000 cars were serviced and spent 470-1870

hours looking for parking [23]. Cruising around the block while looking for parking not only

frustrates drivers but also has a huge impact on the transportation system of the city. Dowling et

al also reported that 20% of the drivers got in to heated arguments over parking spaces. Arguments

can lead to physical violence and this can highly impact the world that we live in. Since the parking

system we propose allows drivers to reserve their parking spot, this will allow zero arguments to

occur thus having a positive impact on the environment. The smart parking system will not only

improve the transportation system but will reduce the congestion that the process of finding an

empty parking causes.

The smart parking system that is being developed by team is costly but will last for a

decade or more. Corner in his research reported that the annual cost of searching for parking in 30

major cities of the US is 95.7 billion dollars [24]. In the UK, the annual cost of searching for

parking is 31.2 billion euros and this alone is the cost of the major cities [24]. With undeveloped

countries still starving and not getting the average human rights, this is a lot of money. The smart

parking system would enable the drivers to find a parking in less time thus reducing the average

cost and time wasted.

70

The purpose of this system is to contribute to the idea of smart cities around the world.

Corner also reported that 20% of the drivers in the US would go home late because it would take

them less time to search for a parking [24]. This wastes a lot of time and would also affect the time

that drivers spend with their loved ones after coming home being frustrated. The proposed system

would have a great positive societal impact reducing the stress levels and bringing people together.

71

VIII. Preliminary Cost Estimates

Preliminary Cost (Planned Solution):

Item Cost

Wireless HART Kit $1014

Extra Parking Motes $50 each

Infrared Proximity Sensors

GP2Y0A02YK0F

$15

PIR Motion Sensor: $8

Firebase Database Zero

Android Studio Zero

CLI network manager software Zero

Server (Any computer) Zero Table 20- Preliminary cost

Preliminary Cost (Implemented Solution):

Item Cost

Turbo Lock Parking Stopper $130

SparkFun Photon RedBoard $30

2-Relay Module $50 each

Infrared Proximity Sensors

GP2Y0A02YK0F

$15

Batteries $10

Particle Cloud Zero

Android Studio Zero Table 21 - cost of implemented solution

Design Cost:

Entry Cost

Working Hours (per team member) 92 Hours

Advising Hours 10 Hours Table 22- Design Cost

72

IX. Project Management

Software Life Cycle Model

The team is following the scrum agile life cycle model to fulfil the requirements of this

project and to develop a smart automation network. This model allows the team to produce quality

results in a timely manner and has increased the productivity of each team member, which has led

to a better planning, and execution of past and future deadlines. This model is an iterative cycle

that allows the developers to correct any errors on any given stage. Moreover, it provides the users

with an end product at every stage so that the user can test the product for any future corrections.

The main advantage of this model is that it allows communication, planning and analysis in an

iterative manner, which helps the team to reduce any errors and to deliver a quality product within

the given time frame [25].

Figure 49- SDLC approach

73

Project Management task Scheduler

I

D

Ac

tiv

e

Task

Mode

Name Dur

atio

n

Start Finish Predec

essors

1 Ye

s

Manually

Scheduled

Decide on Senior Design team 6

days

8/27/17

8:00 AM

9/1/17

5:00 PM

2 Ye

s

Auto

Scheduled

Find people 3

days

8/27/17

8:00 AM

8/29/17

5:00 PM

3 Ye

s

Auto

Scheduled

Find people from different major 3

days

8/30/17

8:00 AM

9/1/17

5:00 PM

2

4 Ye

s

Auto

Scheduled

Finalize team 2

days

8/27/17

8:00 AM

8/28/17

5:00 PM

5 Ye

s

Auto

Scheduled

Decide on project Idea 15

days

8/29/17

8:00 AM

9/18/17

5:00 PM

4

6 Ye

s

Auto

Scheduled

Brainstorm ideas 3

days

8/29/17

8:00 AM

8/31/17

5:00 PM

7 Ye

s

Auto

Scheduled

Check pros and cons of each idea 3

days

9/1/17

8:00 AM

9/5/17

5:00 PM

6

8 Ye

s

Auto

Scheduled

Analyze each idea 3

days

9/6/17

8:00 AM

9/8/17

5:00 PM

7

9 Ye

s

Auto

Scheduled

Choose the best idea 3

days

9/11/17

8:00 AM

9/13/17

5:00 PM

8

74

10 Ye

s

Auto

Scheduled

Finalize the idea 3

days

9/14/17

8:00 AM

9/18/17

5:00 PM

9

11 Ye

s

Auto

Scheduled

Decide and Finalize advisor 3

days

9/19/17

8:00 AM

9/21/17

5:00 PM

10

12 Ye

s

Auto

Scheduled

Search for advisor related to this

field

2

days

9/19/17

8:00 AM

9/20/17

5:00 PM

13 Ye

s

Auto

Scheduled

Finalize the idea with advisor 3

days

9/19/17

8:00 AM

9/21/17

5:00 PM

14 Ye

s

Auto

Scheduled

Research 7

days

9/22/17

8:00 AM

10/2/17

5:00 PM

13

15 Ye

s

Auto

Scheduled

Explore existing projects related to

wireless hart

4

days

9/25/17

8:00 AM

9/28/17

5:00 PM

16 Ye

s

Auto

Scheduled

Find what is wireless hart 7

days

9/22/17

8:00 AM

10/2/17

5:00 PM

17 Ye

s

Auto

Scheduled

Check HART protocol 6

days

9/22/17

8:00 AM

9/29/17

5:00 PM

18 Ye

s

Auto

Scheduled

Check Fieldbus Protocol 6

days

9/22/17

8:00 AM

9/29/17

5:00 PM

19 Ye

s

Auto

Scheduled

Check wired hart projects 5

days

9/22/17

8:00 AM

9/28/17

5:00 PM

20 Ye

s

Auto

Scheduled

Read more about wireless

communication

5

days

9/22/17

8:00 AM

9/28/17

5:00 PM

21 Ye

s

Auto

Scheduled

Read about network

communication

6

days

9/22/17

8:00 AM

9/29/17

5:00 PM

75

22 Ye

s

Auto

Scheduled

Read about routing protocols 5

days

9/22/17

8:00 AM

9/28/17

5:00 PM

23 Ye

s

Auto

Scheduled

Read about project specification 4

days

9/22/17

8:00 AM

9/27/17

5:00 PM

24 Ye

s

Auto

Scheduled

Read about evolved standards 4

days

9/22/17

8:00 AM

9/27/17

5:00 PM

25 Ye

s

Auto

Scheduled

Implementation 151

days

9/28/17

8:00 AM

4/26/18

5:00 PM

24

26 Ye

s

Auto

Scheduled

Read how to configure the manager 3

days

9/28/17

8:00 AM

10/2/17

5:00 PM

27 Ye

s

Auto

Scheduled

Learn about related software’s 4

days

10/3/17

8:00 AM

10/6/17

5:00 PM

26

28 Ye

s

Auto

Scheduled

Learn the command style of the

manager

5

days

10/9/17

8:00 AM

10/13/17

5:00 PM

27

29 Ye

s

Auto

Scheduled

Read more about Linux coding 5

days

10/16/17

8:00 AM

10/20/17

5:00 PM

28

30 Ye

s

Auto

Scheduled

Do some initial commands 3

days

10/23/17

8:00 AM

10/25/17

5:00 PM

29

31 Ye

s

Auto

Scheduled

Finalize the commands 7

days

10/26/17

8:00 AM

11/3/17

5:00 PM

30

32 Ye

s

Auto

Scheduled

Prepare scripts related to our project 8

days

11/6/17

8:00 AM

11/15/17

5:00 PM

31

33 Ye

s

Auto

Scheduled

Run the script on the manager 2

days

11/16/17

8:00 AM

11/17/17

5:00 PM

32

76

34 Ye

s

Auto

Scheduled

Configure the motes 8

days

11/20/17

8:00 AM

11/29/17

5:00 PM

33

35 Ye

s

Auto

Scheduled

Design the layout for mobile app 12

days

11/30/17

8:00 AM

12/15/17

5:00 PM

34

36 Ye

s

Auto

Scheduled

Design the architecture for mobile

application

5

days

12/18/17

8:00 AM

12/22/17

5:00 PM

35

37 Ye

s

Auto

Scheduled

Code the mobile app 15

days

12/25/17

8:00 AM

1/12/18

5:00 PM

36

38 Ye

s

Auto

Scheduled

Prepare the database 16

days

1/15/18

8:00 AM

2/5/18

5:00 PM

37

39 Ye

s

Auto

Scheduled

Learn about the integration of

mobile application with database

7

days

2/6/18

8:00 AM

2/14/18

5:00 PM

38

40 Ye

s

Auto

Scheduled

Integrate mobile app to the database 9

days

2/15/18

8:00 AM

2/27/18

5:00 PM

39

41 Ye

s

Auto

Scheduled

Connect the manager to the

database

12

days

2/28/18

8:00 AM

3/15/18

5:00 PM

40

42 Ye

s

Auto

Scheduled

Integrate the whole system 10

days

3/16/18

8:00 AM

3/29/18

5:00 PM

41

43 Ye

s

Auto

Scheduled

Test the whole system 10

days

3/30/18

8:00 AM

4/12/18

5:00 PM

42

44 Ye

s

Auto

Scheduled

Run multiple use cases 10

days

4/13/18

8:00 AM

4/26/18

5:00 PM

43

45 Ye

s

Auto

Scheduled

Do Report 44

days

9/28/17

8:00 AM

11/28/17

5:00 PM

24

77

46 Ye

s

Auto

Scheduled

Write introduction 3

days

9/28/17

8:00 AM

10/2/17

5:00 PM

47 Ye

s

Auto

Scheduled

Write abstract 2

days

10/3/17

8:00 AM

10/4/17

5:00 PM

46

48 Ye

s

Auto

Scheduled

Write acknowledgement 6

days

10/5/17

8:00 AM

10/12/17

5:00 PM

47

49 Ye

s

Auto

Scheduled

Write literature review 9

days

10/13/17

8:00 AM

10/25/17

5:00 PM

48

50 Ye

s

Auto

Scheduled

Write design objective 8

days

10/26/17

8:00 AM

11/6/17

5:00 PM

49

51 Ye

s

Auto

Scheduled

Write design analysis 8

days

11/7/17

8:00 AM

11/16/17

5:00 PM

50

52 Ye

s

Auto

Scheduled

Write conclusion 6

days

11/17/17

8:00 AM

11/24/17

5:00 PM

51

53 Ye

s

Auto

Scheduled

Write references 6

days

10/13/17

8:00 AM

10/20/17

5:00 PM

48

54 Ye

s

Auto

Scheduled

Write abstract 8

days

9/28/17

8:00 AM

10/9/17

5:00 PM

55 Ye

s

Auto

Scheduled

Compile report 18

days

10/23/17

8:00 AM

11/15/17

5:00 PM

53

56 Ye

s

Auto

Scheduled

Prepare for presentation 9

days

11/16/17

8:00 AM

11/28/17

5:00 PM

55

Table 23- Task Scheduler

78

X. Standards

Standards are documents that specify procedures and add value to the material or services

people use every day. Wireless HART is an open- standard technology that communicates

wirelessly over the 2.4 GHz ISM band. The standards below show the most important standards

that the team’s project should comply with by making the services of the project reliable.

IEEE 802.15.4 Basics

This standard is the most important standard in the project since it allows the lower layer

networks to accommodate wireless personal area network (WPAN) [26]. This standard provides

communication with no underlying infrastructure.

IEEE 802.15.4-2006

The 2006 version of the standard allows increase in data rates on the lower frequency bands

[27]. It allows a time synchronized, self-organizing, and self-configuring mesh architecture.

ISO/IEC/IEEE 26531:2015

This standard focuses on the building and developing of software [28]. It focuses on the

management of the software, the life cycle, the user and the services it offers.

ISO/IEC/IEEE 29119 Software Testing

This standard is well known when it comes to the testing of software in the software

development cycle. It provides guidelines on how to test software in an optimum method so that

it would allow developers to find most errors [29].

79

ISO/IEC 11581-10:2010

This standard realizes that icons are more than just symbols since they are not just pictures but

also interact with the users through the user interface [30]. This standard provides guidance for

developers for creating icons by standardizing icons. This standard basically describes how to

create an interactive and informative user interface.

80

XI. List of Components

LTP5903CEN-WHR Manager

The manager is the device that controls the network and will receive the data packets from

the motes. The manager offers a user interface to the users called HART [15]. It will also allow

users to change the network topologies in to anything they want. The users can control all the

motes using the manager and can turn on and off any mote at any given time using the manager.

Figure 50- Manager Interfaces

DC9003A-C Mote: The mote is responsible for maintaining the synchronization in the

network and forwarding data to the manager. It will also connect directly to sensors to receive the

81

data and pass it on to the network. Motes will be highly connected to each other and also offer to

find loss path connection [16].

Figure 51- Wireless HART Mote chip

Infrared Proximity Sensors GP2Y0A02YK0F:

This sensor will be used to detect the cars since it can detect any presence of nearby objects

up to 150 cm. It has an output voltage of 2.8V to 0.4V with a supply voltage of 4.5-5.5 V. The

sensor also contains a JST that is a Japanese Solderless Terminal.

A proximity sensor is type of sensor that can detect physical presence of close by objects

without any physical contact. It detects the physical presence of objects by emitting

electromagnetic radiation, which in our case is using infrared. After emitting the radiation, it looks

82

for changes in the field or the return signal to detect the proximity of the object. The object which

is being sensed with our proximity sensor is called the ‘proximity sensor’s target.

PIR Motion Sensor

This motion sensor will be used to sense any movement around it, when a car enters the parking

it will sense it and send signal to the manager through the mote.

PIR based motion detector that is also called PID sometimes and stands for passive infrared

detector. This sensor is used for motion detection or in simple words movements of people, animals

or any objects. The commonly used application of the PIR motion sensor is to automatically turn

on light, set burglar alarms, etc. It works by emitting infrared radiations and detecting changes in

its field characteristics like temperature and other surface features. Therefore, the temperature rises

when an object is in the close proximity causing change in the field and the output voltage and

turning back, which shows detection.

Parking Lock

A parking lock would be laid on the ground that be enabled and would come up when a

parking is reserved. This will help reserve parking and making sure that people do not argue over

parking spaces.

Photon

A single photon will be placed for six parking spots which will further connect to six

parking spots.

83

XII. Progress this semester

We were able to setup the WirelessHART network. Furthermore we needed to use this network

to implement the smart parking system however due to lack of resources and malfunctioning of

some devices (motes and manager) we were unable to carry on with this equipment. We then

moved on to the new device which was the ESP 8266. We were able to configure the ESP 8266

and get the value from the device and upload it onto a MQTT server. We then faced an issue

retrieving that value from the MQTT server. Due to lack of time, we considered moving to a photon

based solution since we were already familiar on how to store and retrieve values from the photon

cloud and were using it to control the parking stopper as well.

84

XIII. Conclusion

The Smart Parking System would solve many major issues in big cities of developed

countries. The main aim of smart cities is to make better use of the services offered to citizens and

improve the standard of living for the community [11]. The system that the team has worked on

will contribute heavily towards a smart city. In this report, we have discussed the design of the

system that we have implemented. In the near future, the team would like to find investors to invest

in our idea making this system applicable to large parking lots thus reducing problems discussed

in this report. The team is also interested in finding techniques that would improve our system and

would offer an even smarter solution. This semester we were able to develop to implement a

working prototype of the desired system. Finally, senior design was very helpful in deepening our

understating of the development of systems and how to execute the development practical project.

85

Appendix A (Gant Chart)

86

87

88

89

Appendix B (Use Case description)

Use-Case ID: 1

Use-Case Name: Store Data

Actors: Wireless Sensor (Mote), Database Server

Description: The wireless sensor data gets updated to database server

Preconditions: 1. Sensors are active and transmitting data

2. The Manager is active and awake for reception

Postconditions: The parking space data is updated in real time.

Normal Flow 1.0: 1. The data is sent from sensors to manager.

2. The manager receives the data through different routes.

3. The manager forwards data to the database.

Includes: N/A

Assumptions: The network connection is established between mote to manager and manager to

database

Use-Case ID: 2

Use-Case Name: View Available Parking

Actors: End User, Mobile Application

Description: This is when the user views the available parking spots

90

Preconditions: 1. The mobile application is connected to the internet

2. The mobile application is connected to the database

3. The wireless sensors are updating data in real time to database

Postconditions: The user could view the vacant parking space and is given option to reserve

Normal Flow 1.0: 1. The user can see the location he is in

2. The user can choose the available parking areas

3. The user can view the parking in any available area

Includes: N/A

Assumptions: The mobile application retrieves data from the database

Use-Case ID: 3

Use-Case Name: Search Available Parking

Actors: End User, Mobile Application

Description: This is when the user searches for the available parking spots

Preconditions: 1. The mobile application is connected to the internet

2. The mobile application is connected to the database

3. The wireless sensors are updating data in real time to database

Postconditions: The user could view the vacant parking space and is given option to reserve

Normal Flow 1.0: 1. The user can see the location he is in

2. The user can search for any new location

91

3. The user can search while typing the location for any particular

address

4. The user can search for locations directly on the map

5. The user can then view any parking available in the searched area

Includes: N/A

Assumptions: The mobile application retrieves data from the database

Use-Case ID: 4

Use-Case Name: Reserve Parking

Actors: End User, Mobile Application

Description: This is when the user reserves the available parking spots

Preconditions: 1. The mobile application is connected to the internet

2. The mobile application is connected to the database

3. The wireless sensors are updating data in real time to database

Postconditions: The user would be notified for the reserved parking

Normal Flow 1.0: 1. The user can see the available parking

2. The user can select any parking spot

3. The user can view the rates and details for that specific parking

location

4. The user can then reserve the parking spot

92

Includes: Payement

Assumptions: The mobile application retrieves data from the database

Use-Case ID: 5

Use-Case Name: Payment

Actors: End User, Mobile Application

Description: This is included for user to make payment for the parking

Preconditions: 1. The mobile application is connected to the internet

2. The mobile application is connected to the database

3. The wireless sensors are updating data in real time to database

Postconditions: The parking space is blocked for that user

Normal Flow 1.0: 1. The user chooses from the options of payment

2. The user enters payment details

3. The user receives confirmation of the payment

Includes: N/A

Assumptions: The mobile application retrieves data from the database

93

Use-Case ID: 6

Use-Case Name: Retrieve all Data

Actors: Database Server, Mobile Application

Description: This is when the mobile application tried to retrieve any type of data from the

database

Preconditions: 1. The mobile application is connected to the internet

2. The mobile application is connected to the database

3. The wireless sensors are updating data in real time to database

Postconditions: The parking space is blocked for that user

Normal Flow 1.0: 1. The mobile application requests for the data from the database

2. The mobile application sends queries

3. The result of the queries is processed depending upon users request

4. The processed result is the displayed to user along with available

options for that data

Includes: N/A

Assumptions: The mobile application retrieves data from the database

94

Glossary

HART Highway Addressable

Remote Transducer

Fieldbus Industrial network

protocol

Raspberry pi Micro Computer

Photon Micro Controller

Node Sensor router

Mote Sensor router

IEEE Institute of Electrical

and Electronics

Engineers

95

Bibliography

[1]How Much Urban Traffic is Searching for Parking?. Chase Dowling, Tanner Fiez, Lillian

Ratliff, Baosen Zhang, 2017, pp. 3-6.

[2]"Greenhouse Gas Emissions from a Typical Passenger Vehicle | US EPA", US EPA, 2017.

[Online]. Available: https://www.epa.gov/greenvehicles/greenhouse-gas-emissions-

typical-passenger-vehicle-0. [Accessed: 24- Nov- 2017].

[3]"Climate Change & CO2 | OICA", Oica.net, 2017. [Online]. Available:

http://www.oica.net/category/climate-change-and-co2/. [Accessed: 24- Oct- 2017].

[4]Troubleshooting Your Industrial Network. Fluke Networks, 2017, pp. 3-4.

[5]"Chapter 9 Ethernet – Part 2 - ppt video online download", Slideplayer.com, 2017. [Online].

Available: http://slideplayer.com/slide/7297386/. [Accessed: 25- Nov- 2017].

[6]N. Kehtarnavaz, N. Fourikis and T. Rouphael, "The Benefits of HART Protocol

Communication in Smart Instrumentation Systems | Telecommunication |

Instrumentation", Scribd, 2017. [Online]. Available:

https://www.scribd.com/document/51020284/The-Benefits-of-HART-Protocol-

Communication-in-Smart-Instrumentation-Systems. [Accessed: 12- Nov- 2017].

[7]"HART Communication Networks Are Improved by Small, Flexible, Low-Power Modem ICs

| Analog Devices", Analog.com, 2017. [Online]. Available:

http://www.analog.com/en/analog-dialogue/articles/hart-communication-networks.html.

[Accessed: 30- Oct- 2017].

[8]SmartMesh Wireless Mesh for Tough Industrial IoT Applications. Linear Technology, 2017, pp.

5-7.

[9] S R, B. (2015). Automatic Smart Parking System using Internet of Things (IOT). [ebook]

International Journal of Scientific and Research Publications, p.1. Available at:

http://www.ijsrp.org/research-paper-1215/ijsrp-p4898.pdf [Accessed 26 OCT. 2017].

[10] Amith, B. (2013). Fiber Bragg Grating sensor instrumentation for parking space occupancy

management - IEEE Conference Publication. [online] Ieeexplore.ieee.org. Available at:

http://ieeexplore.ieee.org/document/6409571/?tp=&arnumber=6409571 [Accessed 9 Oct.

2017].

[11] Mondal, R. and Zulfi, T. (2017). Internet of Things and Wireless Sensor Network for Smart

Cities. [ebook] IJCSI International Journal of Computer Science Issues. Available at:

http://ijcsi.org/papers/IJCSI-14-5-50-55.pdf [Accessed 26 Oct. 2017].

[12] Zhang, D. (2014). Real-Time Locating Systems Using Active RFID for Internet of Things -

IEEE Journals & Magazine. [online] Ieeexplore.ieee.org. Available at:

http://ieeexplore.ieee.org/document/6891174/ [Accessed 21 Oct. 2017].

96

[13] Grazioli, A. and Picone, M. (2013). Collaborative Mobile Application and Advanced

Services for Smart Parking - IEEE Conference Publication. [online] Ieeexplore.ieee.org.

Available at: http://ieeexplore.ieee.org/xpls/icp.jsp?arnumber=6569060 [Accessed 18

Nov. 2017].

[14] Anon, (2014). [ebook] Dust Networks. Available at: http://cds.linear.com/docs/en/product-

info/2PB_DC9007fb.pdf [Accessed 5 Oct. 2017].

[15] SmartMesh WirelessHART Network Manager Wireless Embedded Network Manager.

(2014). [ebook] Dust Networks. Available at:

http://cds.linear.com/docs/en/datasheet/5903whrf.pdf [Accessed 12 Nov. 2017].

[16] SmartMesh WirelessHART Node Wireless Mote. (2014). [ebook] Dust Networks. Available

at: http://cds.linear.com/docs/en/datasheet/5800whmfa.pdf [Accessed 9 Nov. 2017].

[17] Li, Y. (2015). Design of communication system in intelligent instrument based on HART

protocol - IEEE Conference Publication. [online] Ieeexplore.ieee.org. Available at:

http://ieeexplore.ieee.org/xpls/icp.jsp?arnumber=7237510 [Accessed 7 Nov. 2017].

[18] SmartMesh WirelessHART User's Guide. (2014). [ebook] Dust Networks. Available at:

http://cds.linear.com/docs/en/user-guide/SmartMesh_WirelessHART_User_s_Guide.pdf

[Accessed 5 Nov. 2017].

[19] Mohammad Baitalmal, A. (2015). Mobile Application Based Parking Reservation System -

PDF. [online] Docplayer.net. Available at: http://docplayer.net/43806912-Mobile-

application-based-parking-reservation-system.html [Accessed 1 Nov. 2017].

[20] Grodi, R. (2016). Smart parking: Parking occupancy monitoring and visualization system

for smart cities - IEEE Conference Publication. [online] Ieeexplore.ieee.org. Available

at: http://ieeexplore.ieee.org/document/7506721/ [Accessed 8 Nov. 2017].

[21] Nixon, M. (2012). A Comparison of WirelessHART™ and ISA100.11a. [ebook] Emerson

Process Management. Available at:

http://www2.emersonprocess.com/siteadmincenter/PM%20Central%20Web%20Docume

nts/WirelessHART-vs-isa-WP.pdf [Accessed 3 Nov. 2017].

[22] Lennvall, T. and Svensson, S. (2008). A Comparison of WirelessHART and ZigBee for

Industrial Applications. [ebook] IEEE. Available at:

https://library.e.abb.com/public/8043193f45e3cc6a85257bc6006366c8/A%20Compariso

n%20of%20WirelessHART%20and%20ZigBee%20for%20Industrial%20Applications.p

df [Accessed 13 Nov. 2017].

[23] Dowling, C., Fiez, T. and Ratlif, L. (2017). How Much Urban Traffic is Searching for

Parking?. [ebook] pp.11-12. Available at: https://arxiv.org/pdf/1702.06156.pdf

[Accessed 16 Oct. 2017].

[24] Corner, S. (2017). Why smart parking could save millions. [online] IoT Hub. Available at:

https://www.iothub.com.au/news/smart-parking-could-save-millions-469996 [Accessed

16 Nov. 2017].

97

[25] QAT Global. (n.d.). Agile Scrum Methodology - QAT Global. [online] Available at:

https://www.qat.com/agile-scrum-methodology/ [Accessed 6 Oct. 2017].

[26] IEEE Standard for Information technology-- Local and metropolitan area networks--

Specific requirements-- Part 15.4: Wireless Medium Access Control (MAC) and Physical

Layer (PHY) Specifications for Low Rate Wireless Personal Area Networks (WPANs).

(n.d.). [online] Available at: http://ieeexplore.ieee.org/document/1700009/ [Accessed 6

Oct. 2017].

[27] ISO/IEC/IEEE International Standard for Systems and software engineering -- Content

management for product life-cycle, user, and service management documentation. (n.d.).

[online] Available at: http://ieeexplore.ieee.org/document/7106441/ [Accessed 13 Nov.

2017].

[28]J. Adams, An Introduction to IEEE STD 802.15.4. Freescale Semiconductor, Inc., 2017, p. 2

[29] 29119-1:2013, "ISO/IEC/IEEE 29119-1:2013 - Software and systems engineering --

Software testing -- Part 1: Concepts and definitions", Iso.org, 2017. [Online]. Available:

https://www.iso.org/standard/45142.html. [Accessed: 18- Nov- 2017].

[30] I. 11581-10:2010, "ISO/IEC 11581-10:2010 - Information technology -- User interface

icons -- Part 10: Framework and general guidance", Iso.org, 2010. [Online]. Available:

https://www.iso.org/standard/46445.html. [Accessed: 16- Nov- 2017].