Higher Nationals in Computing

Unit 43: Internet Of Things

ASSIGNMENT 1

Assessor name: PHAN MINH TAM

Learner’s name: PHAN NGUYEN THANH TUNG

ID: GCS17645
Class:GCS0701B
Subject code: 1690

Assignment due: Assignment submitted:

 ASSIGNMENT 1 FRONT SHEET

Qualification TEC Level 5 HND Diploma in Computing

Unit number and title Unit 43: Internet of Things

Submission date Date Received 1st submission

Re-submission Date Date Received 2nd submission

PHAN NGUYEN THANH

Student Name Student ID GCS17645
TUNG

Class 0701B Assessor name Phan Minh Tam

Student declaration
I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I understand that
making a false declaration is a form of malpractice.

Student’s signature

Grading grid

P1 P2 P3 P4 M1 M2 M3 M4 D1
❒ Summative Feedback: ❒ Resubmission Feedback:

Grade: Assessor Signature: Date:

Signature & Date:

 ASSIGNMENT 1 BRIEF

Qualification BTEC Level 5 HND Diploma in Computing

Unit number Unit 43: Internet of Things

Assignment title

Academic Year

Unit Tutor Phan Minh Tam

Issue date Submission date

IV name and date

Submission Format:
Format: This assignment is an Individual assignment and specifically including 1 document:
You must use font Calibri size 12, set number of the pages and use multiple line spacing at
1.3. Margins must be: left: 1.25 cm; right: 1 cm; top: 1 cm and bottom: 1 cm. The reference
follows Harvard referencing system. The recommended word limit is 2.000-2.500 words.
You will not be penalized for exceeding the total word limit. The cover page of the report
has to be the Assignment front sheet 1.
Submission Students are compulsory to submit the assignment in due date and in a way requested by
the Tutors. The form of submission will be a soft copy posted on
http://cms.greenwich.edu.vn/
Note: The Assignment must be your own work, and not copied by or from another student or from
books etc. If you use ideas, quotes or data (such as diagrams) from books, journals or other sources, you
must reference your sources, using the Harvard style. Make sure that you know how to reference
properly, and that understand the guidelines on plagiarism. If you do not, you definitely get fail

Unit Learning Outcomes:

LO1 Analyse what aspects of IoT are necessary and appropriate when designing software applications
LO2 Outline a plan for an appropriate IoT application using common architecture, frameworks, tools, hardware
and APIs
LO3 Develop an IoT application using any combination of hardware, software, data, platforms and services.
LO4 Evaluate your IoT application and detail the problem your IoT application solves, the potential impact on
people, business, society and the end user and the problems it might encounter when integrating into the wider
IoT ecosystem
Assignment Brief and Guidance:

You currently work as a product developer for a new startup where you design IoT products for the
consumer, corporate, government and defence clients. As part of your role your manager has tasked you
to plan and develop a new IoT product, service or application for a potential client. You are required to
identify a target user and conduct tests with this user and include this feedback into multiple iterative
versions of your product.
Part 1 (Assignment 1):: For the first part, you must:

 Plan an IoT application for a specific target end user and the tests you intend to conduct with this
user. This plan will be in the form of a document and will include supporting evidence and
material, such as user personas and customer journey maps.
 Create multiple iterations of your application and modify each iteration with enhancements
gathered from user feedback and experimentation. This will follow the pathway outlined in your
plan.(log book,)

Part 2 (Assignment 2): For the first part, you must:

 Show evidence about Developed IoT application using any combination of hardware, software,
data, platforms and services (video or images of your IoT system with code snippet)
 Evaluate your IoT application and detail the problem your IoT application solves, the potential
impact on people, business, society and the end user and the problems it might encounter when
integrating into the wider IoT ecosystem
 Learning Outcomes and Assessment Criteria

Pass Merit Distinction

LO1 Analyse what aspects of IoT are necessary and appropriate when designing software
applications

P1 Explore various forms M1 Evaluate the impact of D1 Evaluate specific forms of

of IoT functionality. common IoT architecture, IoT architecture and justify
frameworks, tools, hardware their use when designing
and APIs in the software software applications.
P2 Review standard
development lifecycle.
architecture, frameworks,
tools, hardware and APIs
available for use in IoT M2 Review specific forms of
development. IoT architecture, frameworks,
tools, hardware and APIs for
different problem-solving
requirements.

LO2 Outline a plan for an appropriate IoT application using common architecture,
frameworks, tools, hardware and APIs

P3 Investigate M3 Select the most

architecture, frameworks, appropriate IoT architecture,
tools, hardware and API frameworks, tools, hardware
techniques available to and API techniques to include
develop IoT applications. in an application to solve this
problem.
P4 Determine a specific
problem to solve using IoT. M4 Apply your selected
techniques to create an IoT
application development plan.
 Table of Contents

Contents
Unit 43: Internet Of Things ASSIGNMENT 1.............................................................................................................1
P1: Explore various forms of IoT functionality.........................................................................................................1
P2: Review standard architecture, frameworks, tools, hardware and APIs available for use in IoT development..7
P3: Investigate architecture, frameworks, tools, hardware and API techniques available to develop IoT
applications.............................................................................................................................................................8
P4 : Determine a specific problem to solve using IoT............................................................................................14
REFERENCES..........................................................................................................................................................16
 ASSIGNMENT 1 ANSWERS

P1: Explore various forms of IoT functionality.

1.Overview:
IoT systems allow users to achieve deeper automation, analysis, and integration within a system. They improve
the reach of these areas and their accuracy. IoT utilizes existing and emerging technology for sensing,
networking, and robotics.

IoT exploits recent advances in software, falling hardware prices, and modern attitudes towards technology. Its
new and advanced elements bring major changes in the delivery of products, goods, and services; and the
social, economic, and political impact of those changes.

IoT − Key Features

The most important features of IoT include artificial intelligence, connectivity, sensors, active engagement, and
small device use. A brief review of these features is given below −

AI − IoT essentially makes virtually anything “smart”, meaning it enhances every aspect of life with the power of
data collection, artificial intelligence algorithms, and networks. This can mean something as simple as
enhancing your refrigerator and cabinets to detect when milk and your favorite cereal run low, and to then
place an order with your preferred grocer.

Connectivity − New enabling technologies for networking, and specifically IoT networking, mean networks are
no longer exclusively tied to major providers. Networks can exist on a much smaller and cheaper scale while still
being practical. IoT creates these small networks between its system devices.

Sensors − IoT loses its distinction without sensors. They act as defining instruments which transform IoT from a
standard passive network of devices into an active system capable of real-world integration.

Active Engagement − Much of today's interaction with connected technology happens through passive
engagement. IoT introduces a new paradigm for active content, product, or service engagement.

Small Devices − Devices, as predicted, have become smaller, cheaper, and more powerful over time. IoT exploits
purpose-built small devices to deliver its precision, scalability, and versatility.

2. IoT in software development

The actual components making up most IoT devices include tags, sensors, embedded computers and actuators
integrated into objects. While some IoT objects are “vertical specific”, others can find use in many areas.

Some, like tags or iBeacons, will be of the “deploy and forget” type. Others will be constantly reporting data
that is monitored and controlled via a web interface by the owner, or provided by companies that implement
IoT-as-a-service for customers, like Thingspeak.

The main driving forces behind IoT, and therefore shaping its future, are commoditisation and interoperability,
which in turn depend on:

Page |1
The development of embedded devices (low-power, reduced cost computers, most frequently based on the
ARM architecture).

Improved communications protocols (GSM, WiFi, Bluetooth variants and more specialized Zigbee, 6LowPAN,
Sigfox and so on.)

Software platforms like Thingworx, ioBridge, Sense and others.

Influential companies like Amazon, Google, Apple, IBM, and Microsoft are also playing a part as drivers of IoT.

3. IoT History

Page |2
Page |3
1969:

ARPANET, the precursor to the modern Internet, is developed and put into service by DARPA, the U.S Defense
Advanced Research Projects agency. This is foundational to the “Internet” part of the Internet of Things.

1980s:

ARPANET is opened up to the public by commercial providers, making it possible for people to connect things if
they want to.

1982:

Programmers at Carnegie Mellon University connect a Coca-Cola vending machine to the Internet, allowing
them to check if the machine has cold sodas before going to purchase one. This is often cited as one of the first
IoT devices.

1990:

John Romkey, in response to a challenge, connected a toaster to the Internet and was able to successfully turn
it on and off, bringing us even closer to what we think of as modern IoT devices.

1993:

Engineers at the University of Cambridge, upholding the now well-established tradition of combining the
Internet with appliances and food, develops a system that takes pictures of a coffee machine three times a
minute, allowing its status to be remotely monitored by workers. World’s first webcam!

1995:

The first version of the long-running GPS satellite program run by the U.S. government is finally completed, a
big step towards proving one of the most vital components for many IoT devices: location.

1998:

IPv6 becomes a draft standard, enabling more devices to connect to the internet than previously allowed by
IPv4. While 32-bit IPv4 only provides enough unique identifiers for around 4.3 billion devices, 128-bit IPv6 has
enough unique identifiers for up to 2^128, or 340 undecillion. (That’s 340 with 36 zeroes!)

1999:

This is a big year for IoT, since it’s when the phrase was probably first used. Kevin Ashton, the head of MIT’s
Auto-ID labs, included it in a presentation to Proctor & Gamble executives as a way to illustrate the potential of
RFID tracking technology.

2000:

LG announces what has become one of the quintessential IoT devices: the Internet refrigerator. It was an
interesting idea, complete with screens and trackers to help you keep track of what you had in your fridge, but
its $20,000+ USD price tag didn’t earn it a lot of love from consumers.

2004:

The phrase “Internet of Things” starts popping up in book titles and makes scattered media appearances.

2007:

Page |4
The first iPhone appears on the scene, offering a whole new way for the general public to interact with the
world and Internet-connected devices.

2008:

The first international IoT conference is held in Zurich, Switzerland. The year is fitting, since it’s also the first
year that the number of Internet-connected devices grew to surpass the number of humans on earth.

2009:

Google starts self-driving car tests, and St. Jude Medical Center releases Internet connected pacemakers. St.
Jude’s device will go on to make yet more history by being the first IoT medical device to suffer a major security
breach in 2016 (without casualties, fortunately). Also, Bitcoin starts operation, a precursor to blockchain
technologies that are likely to be a big part of IoT.

2010:

The Chinese government names IoT as a key technology and announces that it is part of their long-term
development plan. In the same year Nest releases a smart thermostat that learns your habits and adjusts your
home’s temperature automatically, putting the “smart home” concept in the spotlight.

2011:

Market research firm Gartner adds IoT to their “hype cycle,” which is a graph used to measure the popularity of
a technology versus its actual usefulness over time. As of 2018, IoT was just coming off of the peak of inflated
expectations and may be headed for a reality check in the trough of disillusionment before ultimately hitting
the plateau of productivity.

2013:

Google Glass is released – a revolutionary step in IoT and wearable technology but possibly ahead of its time. It
flops pretty hard.

2014:

Amazon releases the Echo, paving the way for a rush into the smart home hub market. In other news, an
Industrial IoT standards consortium form demonstrates the potential for IoT to change the way any number of
manufacturing and supply chain processes work.

2016:

General Motors, Lyft, Tesla, and Uber are all testing self-driving cars. Unfortunately, the first massive IoT
malware attack is also confirmed, with the Mirai botnet assaulting IoT devices with manufacturer-default logins,
taking them over, and using them to DDoS popular websites.

2017-2019:

IoT development gets cheaper, easier, and more broadly-accepted, leading to small waves of innovation all over
the industry. Self-driving cars continue to improve, blockchains and AI begin to be integrated into IoT platforms,
and increased smartphone/broadband penetration continues to make IoT an attractive proposition for the
future.

Page |5
4.Advantanges and disadvantages of using IoT
- Here are some advantages of IoT:

1. Data: The more the information, the easier it is to make the right decision. Knowing what to get from the
grocery while you are out, without having to check on your own, not only saves time but is convenient as well.

2. Tracking: The computers keep a track both on the quality and the viability of things at home. Knowing the
expiration date of products before one consumes them improves safety and quality of life. Also, you will never
run out of anything when you need it at the last moment.

3. Time: The amount of time saved in monitoring and the number of trips done otherwise would be
tremendous.

4. Money: The financial aspect is the best advantage. This technology could replace humans who are in charge
of monitoring and maintaining supplies.

- Here are some disadvantages of IoT:

1. Compatibility: As of now, there is no standard for tagging and monitoring with sensors. A uniform concept

Page |6
like the USB or Bluetooth is required which should not be that difficult to do.

2. Complexity: There are several opportunities for failure with complex systems. For example, both you and
your spouse may receive messages that the milk is over and both of you may end up buying the same. That
leaves you with double the quantity required. Or there is a software bug causing the printer to order ink
multiple times when it requires a single cartridge.

3. Privacy/Security: Privacy is a big issue with IoT. All the data must be encrypted so that data about your
financial status or how much milk you consume isn’t common knowledge at the work place or with your friends.

4. Safety: There is a chance that the software can be hacked and your personal information misused. The
possibilities are endless. Your prescription being changed or your account details being hacked could put you at
risk. Hence, all the safety risks become the consumer’s responsibility.

P2: Review standard architecture, frameworks,

tools, hardware and APIs available for use in IoT
development.
1.IoT architecture
In essence, IoT architecture is the system of numerous elements: sensors, protocols, actuators, cloud services,
and layers. Given its complexity, there exist 4 stages of IoT architecture. Such a number is chosen to steadily
include these various types of components into a sophisticated and unified network.

b.Advantages and disadvantages of IoT architecture

Advantages:

- Reduce the cost and complexity on the edge devices

- Gateway can act as the connector hub for things with different data standards and wireless - protocols
that provide an uniform face to the outside.
- Easy to monitor and control things as a whole rather than interface with each individual of them
- Gateway can control what data to be sent to Internet and provide security capability than things
- Convenient to link legacy equipment into the IoT

Disadvantages

- One more “Tier” adds complexity in terms of integration

- Resources still reside locally comparing with using cloud
- One extra point of failure

Page |7
2. IoT framework
For an IoT framework to be reliable and dependable, some minimal set of measures should be satisfied to
achieve integration and interoperability in IoT. These frameworks span across the IoT research communities
ranging from academic research to organisational research which focus on integrating things in IoT. Since IoT
paradigm itself is still in evolving state, we propose a set of minimal measures to be satisfied by IoT frameworks
for integration.

3. IoT Tools:
OT Tools stands for the Internet of Things Tools. It is a network or connection of devices, vehicles, equipment
applying embedded electronics, home appliances, buildings and many more. This helps in collecting and
exchanging different kinds of data. It also helps the user to control the devices remotely over a network.

4. IoT hardwares
IoT Hardware includes a wide range of devices such as devices for routing, bridges, sensors etc. These IoT
devices manage key tasks and functions such as system activation, security, action specifications,
communication, and detection of support-specific goals and actions.

5. IoT AIPs
An API is a set of routines, protocols, and tools for building software applications; It specifies how software
components should interact. APIs are tightly linked with IoT because they allow you to securely expose
connected devices to customers, go-to-market channels, and other applications in your IT infrastructure.
Because APIs connect important “things,” like cars, medical devices, smart grids, and thermostats, to your
ecosystem, more critical to deploy API management that is flexible, scalable, and secure.

P3: Investigate architecture, frameworks, tools,

hardware and API techniques available to develop
IoT applications.
1.IoT Architecture
Basically, there are three IoT architecture layers:

1. The client side (IoT Device Layer)

2. Operators on the server side (IoT Getaway Layer)

3. A pathway for connecting clients and operators (IoT Platform Layer)

Page |8
In fact, addressing the needs of all these layers is crucial on all the stages of IoT architecture. Being the basis of
feasibility criterion, this consistency makes the result designed really work. In addition, the fundamental
features of sustainable IoT architecture include functionality, scalability, availability, and maintainability.
Without addressing these conditions, the result of IoT architecture is a failure.

Therefore, all the above-mentioned requirements are addressed in 4 stages of IoT architecture described here
— on each separate stage and after completing the overall building process

In simple terms, the 4 Stage IoT architecture consists of

1. Sensors and actuators

2. Internet getaways and Data Acquisition Systems

3. Edge IT

4. Data center and cloud.

The detailed presentation of these stages can be found on the diagram below.

To get the proper understanding of the main actions and the importance of each stage in this process, refer to
the detailed reviews presented below.

Stage 1. Networked things (wireless sensors and actuators)

The outstanding feature about sensors is their ability to convert the information obtained in the outer world
into data for analysis. In other words, it’s important to start with the inclusion of sensors in the 4 stages of an
IoT architecture framework to get information in an appearance that can be actually processed.

For actuators, the process goes even further — these devices are able to intervene the physical reality. For
example, they can switch off the light and adjust the temperature in a room.
Page |9
Because of this, sensing and actuating stage covers and adjusts everything needed in the physical world to gain
the necessary insights for further analysis.

Stage 2. Sensor data aggregation systems and analog-to-digital data conversion

Even though this stage of IoT architecture still means working in a close proximity with sensors and actuators,
Internet getaways and data acquisition systems (DAS) appear here too. Specifically, the later connect to the
sensor network and aggregate output, while Internet getaways work through Wi-Fi, wired LANs and perform
further processing.

The vital importance of this stage is to process the enormous amount of information collected on the previous
stage and squeeze it to the optimal size for further analysis. Besides, the necessary conversion in terms of
timing and structure happens here.

In short, Stage 2 makes data both digitalized and aggregated.

Stage 3. The appearance of edge IT systems

During this moment among the stages of IoT architecture, the prepared data is transferred to the IT world. In
particular, edge IT systems perform enhanced analytics and pre-processing here. For example, it refers to
machine learning and visualization technologies. At the same time, some additional processing may happen
here, prior to the stage of entering the data center.

Likewise, Stage 3 is closely linked to the previous phases in the building of an architecture of IoT. Because of
this, the location of edge IT systems is close to the one where sensors and actuators are situated, creating a
wiring closet. At the same time, the residing in remote offices is also possible.

Stage 4. Analysis, management, and storage of data

The main processes on the last stage of IoT architecture happen in data center or cloud. Precisely, it enables in-
depth processing, along with a follow-up revision for feedback. Here, the skills of both IT and OT (operational
technology) professionals are needed. In other words, the phase already includes the analytical skills of the
highest rank, both in digital and human worlds. Therefore, the data from other sources may be included here to
ensure an in-depth analysis.

After meeting all the quality standards and requirements, the information is brought back to the physical world
— but in a processed and precisely analyzed appearance already.

Stage 5 of IoT Architecture?

In fact, there is an option to extend the process of building a sustainable IoT architecture by introducing an
extra stage in it. It refers to initiating a user’s control over the structure — if only your result doesn’t include full
automation, of course. The main tasks here are visualization and management. After including Stage 5, the
system turns into a circle where a user sends commands to sensors/actuators (Stage 1) to perform some
actions.

And the process starts all over again..

2.IoT framework
For an IoT framework to be reliable and dependable, some minimal set of measures should be satisfied to
P a g e | 10
achieve integration and interoperability in IoT. These frameworks span across the IoT research communities
ranging from academic research to organisational research which focus on integrating things in IoT. Since IoT
paradigm itself is still in evolving state, we propose a set of minimal measures to be satisfied by IoT frameworks
for integration. These are:

• Contract decoupling: An IoT system contains heterogeneous devices with disparate communication protocols.
An integration framework should be competent enough to efficiently handle contract decoupling. Contract
decoupling is the ability of service consumers and service producers to 4 IoT Architectural Framework
independently evolve without terminating the contract between them [19]. For example, a service might be in a
JSON format and the service consumer needs an input in XML. The framework should provide support to
transform the message to the format that fulfils the contract between them.

• Scalability: Given the evolving nature of IoT and the predictions and calculations by [3] and [2], an efficient
integration framework should be scalable and evolvable enough to support the billions of things soon to be
connected to the internet.

• Ease of testing: An integration framework should support ease of testing and debugging. It should provide
support for debugging defects and failures, integration testing, component testing, system testing, compatibility
testing, installation test, functional and non-functional testing, performance testing and security testing.

• Ease of development: An IoT integration framework should provide a means of easy development for
developers. The framework should exclude all complexities and provide proper documentation for non-
developers and developers with basic programming knowledge to easily understand the internals of the
framework.

• Fault tolerance: An IoT system has to be dependable and resilient. An intelligent integration framework
should effectively handle faults as IoT devices can eventually toggle between offline and online states. The
framework should provide self-healing mechanisms for transient faults (network faults, node level faults, etc.),
unauthorised access error, server crash failure, omission failure (when the server does not receive incoming
requests from client), timing fault, etc.

• Lightweight implementation: Integration frameworks should have a lightweight overhead both in its
development and deployment stage. It should be lightweight and easy to install, uninstall, activate, deactivate,
update, versioning and adaptable.

• Service coordination: Service coordination is the orchestration and choreography of services. Service
orchestration is the coordination of multiple services by a mediator acting as a centralized component. Service
choreography on the other hand, is the chaining of services together to execute a particular transaction.
Integration frameworks should support at least either or both to achieve reliability.

• Inter domain operability: The framework should further be extensible to support inter domain
communication. For example, in a smart car domain, an integration framework should also provide support for
communication and interaction with traffic lights, road closure, etc. belonging to a smart city domain.

Regardless of the research community or disparity in research, they all aim to achieve extensibility, flexibility,
scalability, design reuse and implementation reuse. The next sub-sections will present an overview of some IoT
frameworks.

3.IoT Tools
P a g e | 11
1. Tessel 2

It is used to build basic IoT prototypes and applications. It helps through its numerous modules and sensors.
Using Tessel 2 board, a developer can avail Ethernet connectivity, Wi-Fi connectivity, two USB ports, a micro
USB port, 32MB of Flash, 64MB of RAM. Additional modules can also be integrated like cameras,
accelerometers, RFID, GPS, etc.

Tessel 2 can support Node.JS and can use libraries of Node.JS. It contains two processors, its hardware uses
48MHz Atmel SAMD21 and 580.

MHz MediaTek MT7620n coprocessor. One processor can help to run firmware applications at high speed and
the other one helps in the efficient management of power and in exercising good input/output control.

2. Eclipse IoT
This tool or instrument allows the user to develop, adopt and promote open source IoT technologies. It is best
suited to build IoT devices, Cloud platforms, and gateways. Eclipse supports various projects related to IoT.
These projects include open source implementations of IoT protocols, application frameworks and services, and
tools for using Lua programming language which is promoted as the best-suited programming language for IoT.
3. Arduino
Arduino is an Italy based IT company that builds interactive objects and microcontroller boards. It is an open
source prototyping platform that offers both IoT hardware and software. Hardware specifications can be
applied to interactive electronics and software includes Integrated Development Environment (IDE). It is the
most preferable IDEs in all IoT development tools. This platform is easy and simple to use.
4. Platform IoT
It is a cross-platform IoT IDE. It comes with the integrated debugger. It is the best for mobile app development
and developers can use a friendly IoT environment for development. A developer can port the IDE on Atom
editor or it can install it as a plugin. It is compatible with more than 400 embedded boards and has more than
20 development frameworks and platforms. It offers a remarkable interface and is easy to use.
5. M2M Labs Mainspring
It is an IoT platform and an open source application framework. It is used to build a machine to machine
applications (M2M) which can be used in fields of remote monitoring and fleet management. It supports much
functionality like validation and normalization of data, device configuration, data retrieval processes and flexible
modeling of devices. It is based on Apache, Cassandra, NoSQL database and Java.
6. Kinoma
It is a Marvell semiconductor hardware prototyping platform. It enables three different projects. To support
these projects two products are available Kinoma Create and Element Board. Kinoma Create is a hardware kit
for prototyping electronic and IoT enabled devices. Kit contains supporting essentials like Bluetooth Low Energy
(BLE), integrated Wi-Fi, speaker, microphone and touch screen. Element Board is the smallest JavaScript-
powered IoT product platform.
7. Device- Hive
It is based on Data Art’s AllJoyn. It is a free open source M2M i.e. machine to machine communication
framework. It was launched in 2012 and considered the most preferable IoT app development platform. It has
cloud-based API which can be controlled remotely irrespective of network configuration. Its libraries, protocols,
and management portal are controlled in a similar manner. It is best suited for applications related to smart
home tech, security, automation, and sensors.
8. Kaax
It provides end to end support for IoT devices connected across the cloud. Due to its multi-purpose middleware,
it allows users to build connected applications, IoT applications, and many smart products. Open source kit is
P a g e | 12
described as ‘hardware agnostic’ by Kaax i.e. it can interface with any hardware like sensors, gateways, and
other devices. It helps developers to distribute firmware updates remotely, and to enable cross-platform
interoperability.
9. Home Assistant
It is an open source tool mostly used for functions based on the Python coding system and home automation.
Desktop and mobile browsers help to control their IoT system. It is easy to set up and is famous for its smooth
operations, privacy standards, and security. It can support systems running on Python 3.
10. Net
It is an integrated solution for developers of IoT. It offers services like cloud integration and business
intelligence to provide both web technologies and hardware. Its development kit is delivered as a platform as a
service i.e. PaaS which allows the developers to efficiently utilize its power for development purpose.
11. Raspbian

This IDE is created for Raspberry Pi board. It has more than 35000 packages and with the help of precompiled
software, it allows rapid installation. It was not created by the parent organization but by the IoT tech
enthusiasts. For working with Raspberry Pi, this is the most suitable IDE available.

4. IoT Hardware
IoT Hardware components can vary from low-power boards; single-board processors like the Arduino Uno
which are basically smaller boards that are plugged into mainboards to improve and increase its functionality by
bringing out specific functions or features (such as GPS, light and heat sensors, or interactive displays). A
programmer specifies a board’s input and output, then creates a circuit design to illustrate the interaction of
these inputs and outputs.
Another well-known IoT platform is Raspberry Pi 2, which is a very affordable and tiny computer that can
incorporate an entire web server. Often called “RasPi,” it has enough processing power and memory to run
Windows 10 on it as well as IoT Core. RasPi exhibits great processing capabilities, especially when using the
Python programming language.

BeagleBoard is a single-board computer with a Linux-based OS that uses an ARM processor, capable of more
powerful processing than RasPi. Tech giant Intel’s Galileo and Edison boards are other options, both great for
larger scale production, and Qualcomm has manufactured an array of enterprise-level IoT technology for cars
and cameras to healthcare.

5.IoT AIPs
Example

Arduino Rest API is a mechanism to exchange data between Arduino and other external systems. Using Arduino
Rest API framework it is possible to control Arduino remotely. The convergence between API and IoT opens
new integration scenarios. The development of an API ecosystem is an interesting topic and the way we access
to IoT service, exposed by remote IoT boards, using API is a challenging aspect.

In more details, exploiting Arduino Rest API a client application reads or sends information to Arduino board. A
typical use case of Arduino Rest API is an external system or application that retrieves sensor values. Arduino
Rest API framework can be used in IoT projects when different systems and boards are connected together and
P a g e | 13
exchange information. Even IoT cloud platforms use Arduino Rest API mechanism. Generally speaking, this kind
of mechanism is useful when an external application (client) sends a request to Arduino and it replies with some
data. Arduino Rest API works over HTTP protocol so this kind of requests are synchronous.

P4 : Determine a specific problem to solve using IoT

Parking space is becoming a serious problem due to the day by day increase in number of vehicles on the road.
Particularly, in cities with large population, or in places where sports or artistic events are scheduled, looking for
parking space is a major problem and finding a parking spot can be a frustrating experience. In order to combat
this problem, some parking lots have introduced sensors to detect when a car enters or leaves a parking lot in
order to track capacity and alert drivers if they are full. This is a partial solution that allows drivers to determine
if a parking lot has open parking spots, but not the exact location of those spots. In this paper, we present a
prototype of smart parking system using wireless sensor technology and networks. Using a Wireless Sensor
Network , parking spot statuses are detected and transmitted to a database. This information then be accessed
by users through website or mobile app) to receive real-time updates. This system should provide users with
near instantaneous updates of available parking spots while the WSN allows for flexibility of sensor placement.
With the successful implementation of smart parking, the economical and time costs associated with traffic
jams, cost associated with wasted gas fuel, and time looking for an empty parking space that are caused by
inefficient parking will be significant reduced.

TASK NAME START END DURATION(days) WORK(days) RESOURCE NAME

DATE DATE
Requirement 1-Dec 17-Dec 16 19
Analysis the Smart 1-Dec 10-Dec 9 6 Iron Man
Parking
Brainstorming 3-Dec 10-Dec 7 4 Thor
Feasibility test 5-Dec 17-Dec 12 9 Captain American
System Design 17-Dec 31-Dec 14 11
Logical design 17-Dec 20-Dec 3 1 Hulk
Physical design 18-Dec 24-Dec 6 3 Black Widow
Document 23-Dec 31-Dec 8 7 Hawkeye
Implementation 1-Jan 16-Jan 15 9
Code 1-Jan 8-Jan 7 5 Loki
Integrate the code 8-Jan 13-Jan 5 2 Spider Man
Unit testing 13-Jan 16-Jan 3 2 Ant Man
System Testing 16-Jan 30-Jan 14 13
Integrate the unit 16-Jan 21-Jan 5 5 Thanor
tested code
Perform all the testing 18-Jan 26-Jan 8 3 Stephen Strange
activities
Tracking progress 16-Jan 26-Jan 10 5 Black Panther
Report Smart Parking 28-Jan 30-Jan 2 1 Captain Marvel
system testing
P a g e | 14
System Deployment 1-Feb 17-Feb 16 8
Ensure environment 1-Feb 5-Feb 4 2 Hulk
for Smart Parking
Test exit criteria are 1-Feb 9-Feb 8 4 Groot
met
Deploy the Smart 9-Feb 13-Feb 4 2 Rocket
Parking
Perform a sanity 9-Feb 17-Feb 8 5 Winter Sodier
check
System Maintenance 18-Feb 30-Feb 12 7
Ensure the Smart 18-Feb 20-Feb 2 1 Falcon
Parking is stability
Fix the issues faced 18-Feb 25-Feb 7 5 Gamora
Updated code 25-Feb 27-Feb 2 1 Star Lord
Update the 27-Feb 30-Feb 3 1 Drax
environment

P a g e | 15
 REFERENCES

- Ieeexplore.ieee.org,(2016). IEEE Xplore Digital Library. [online] Available at:

https://ieeexplore.ieee.org/abstract/document/7506721 [Accessed 11 Jul. 2016].
- Mark Richards (2016): Microservices vs. service-oriented architecture. O’Reilly Media.

- Gartner Says 6.4 Billion Connected. Available at:

http://www.gartner.com/newsroom/id/3165317

- The Internet of Things Needs Openness and Industry Collaboration to Succeed, Says Samsung
Electronics CEO BK Yoon. Available at http://www.samsung.com/uk/news/local/the-internet-
of-things-needs-opennessand-industry-collaboration-to-succeed-says-samsung-electronics-
ceo-bk-yoon.

- Saxena, P. (2016). “The advantages and disadvantages of Internet Of Things. [online] e27.
Available at: https://e27.co/advantages-disadvantages-internet-things-20160615/

P a g e | 16