lOMoARcPSD|42842578

6482-1705912518969-Unit 45 Internet of Things 22

HND In Computing (ESOFT Metro Campus)

Scan to open on Studocu

Studocu is not sponsored or endorsed by any college or university

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)
 lOMoARcPSD|42842578

Higher Nationals - Summative Assignment Feedback Form

Student Name/ID

Unit Title 45: Internet of Things

Assignment Number 1 Assessor

Date Received
Submission Date 1st submission
Date Received 2nd
Re-submission Date submission
Assessor Feedback:
LO1 Analyse what aspects of IoT are necessary and appropriate when designing software
applications

Pass, Merit & Distinction P1 P2 M1 M2 D1

Descripts

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

Pass, Merit & Distinction P3 P4 M3 M4

Descripts
LO3
LO3 Develop an IoT application using any combination of hardware, software, data, platforms Develop an
and services IoT
application
Pass, Merit & Distinction P5 P6 M5 D2 using any
Descripts combinatio
n of
hardware,
LO 4 Evaluate your IoT application and the problems it might encounter when integrating into the wider IoT
ecosystem software,
Pass, Merit & Distinction P7 P8 M6 D3 data,
Descripts platforms
and services

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Assessor Feedback:

Grade: Assessor Signature: Date:

Resubmission Feedback:
*Please note resubmission feedback is focussed only on the resubmitted work

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

* Please note that grade decisions are provisional. They are only confirmed once internal and external moderation has taken place and
grades decisions have been agreed at the assessment board.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Pearson Higher Nationals in

Computing
45: Internet of Things
Assignment 01 of 01

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

General Guidelines

1. A Cover page or title page – You should always attach a title page to your assignment. Use the
previous page as your cover sheet and make sure all the details are accurately filled.
2. Attach this brief as the first section of your assignment.
3. All the assignments should be prepared using word processing software.
4. All the assignments should be printed on A4-sized papers. Use single-sided printing.
5. Allow 1” for the top, bottom, and right margins and 1.25” for the left margin of each page.

Word Processing Rules

1. The font size should be 12 points and should be in the style of Time New Roman.
2. Use 1.5 line spacing. Left justify all paragraphs.
3. Ensure that all the headings are consistent in terms of font size and font style.
4. Use the footer function in the word processor to insert Your Name, Subject, Assignment No,
and Page Number on each page. This is useful if individual sheets become detached for any
reason.
5. Use word processing applications spell check and grammar check functions to help edit your
assignment.

Important Points:

1. It is strictly prohibited to use textboxes to add texts to the assignments, except for the
compulsory information. eg: Figures, tables of comparison, etc. Adding text boxes in the body
except for the before mentioned compulsory information will result in the rejection of your
work.
2. Avoid using page borders in your assignment body.
3. Carefully check the hand-in date and the instructions given in the assignment. Late submissions
will not be accepted.
4. Ensure that you give yourself enough time to complete the assignment by the due date.
5. Excuses of any nature will not be accepted for failure to hand in the work on time.
6. You must take responsibility for managing your own time effectively.
7. If you are unable to hand in your assignment on time and have valid reasons such as illness, you
may apply (in writing) for an extension.
8. Failure to achieve at least PASS criteria will result in a REFERRAL grade.
9. Non-submission of work without valid reasons will lead to an automatic RE FERRAL. You will
then be asked to complete an alternative assignment.
10. If you use other people’s work or ideas in your assignment, reference them properly using the
HARVARD referencing system to avoid plagiarism. You have to provide both in-text citations
and a reference list.
11. If you are proven to be guilty of plagiarism or any academic misconduct, your grade could be
reduced to A REFERRAL, or at worst you could be expelled from the course.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

STUDENT ASSESSMENT SUBMISSION AND DECLARATION

When submitÝng evidence for assessment, each student must sign a declaration confirming
that the work is their own.
Student name: Assessor name:

Issue date: Submission date: Submitted on:

Programme:

Unit:
Assignment number and title:

Plagiarism
Plagiarism is a particular form of cheating. Plagiarism must be avoided at all costs and students
who break the rules, however innocently, may be penalised. It is your responsibility to ensure
that you understand correct referencing practices. As a university level student, you are
expected to use appropriate references throughout and keep carefully detailed notes of all your
sources of materials for material you have used in your work, including any material
downloaded from the Internet. Please consult the relevant unit lecturer or your course tutor if
you need any further advice.

Guidelines for incorporating AI-generated content into assignments:

The use of AI-generated tools to enhance intellectual development is permitted; nevertheless,
submitted work must be original. It is not acceptable to pass off AI-generated work as your
own.

Student Declaration
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 signature: Date:

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Higher National Diploma in Business

Assignment Brief
Student Name /ID Number

Unit Number and Title 45: Internet of Things

Academic Year 2022/2023

Unit Tutor

Assignment Title Researching and building an IoT application

Issue Date

Submission Date

IV Name & Date

Submission format

The assignment submission is in the form of:

• a case study on a positive example of an Internet of things (IoT) implementation with a
recommended word limit of 1,000–1,500 words, written in a concise style, although you will not be
penalised for going under, or exceeding, the total word limit
• a project plan and development report on the development of an appropriate IoT application
with a recommended word limit of 2,000–2,500 words, written in a concise style, although you will
not be penalised for going under, or exceeding, the total word limit
• a project report evaluating the success of your final IoT product with a recommended word limit
of 1,000–1,500 words, written in a concise style, although you will not be penalised for going
under, or exceeding, the total word limit.

You are required to make use of headings, paragraphs, and sub-sections as appropriate, and all
work must be supported with research and referenced using the Harvard referencing system (or an
alternative system). You will also need to provide a bibliography using the Harvard referencing
system (or an alternative system). Inaccurate use of referencing may lead to issues of plagiarism if
not applied correctly.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Unit Learning Outcomes:

LO1 - Analyze 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 the problems it might encounter when integrating into
the wider IoT ecosystem.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Assignment Brief and Guidance:

Scenario

‘ChannelCert (PVT) Ltd’ is a leading research and consultancy firm researching new market
trends In the IT industry and IoT applications for corporate clients and the consumer market.
You currently work as a junior infrastructure architect for ’ChannelCert (PVT) Ltd’. As part of
your role, your manager has tasked you to conduct research on Internet of Things applications
and technologies in order to enlighten a new intake of probationary apprentices in
understanding the business, particularly IoT technologies, frameworks, and architecture, as
most probationary apprentices have not covered these topics in their studies.
As a part of this assignment, you then have to select an organization of your choice to plan and
develop a small IoT application to address an existing problem and to achieve the organization’s
goals.

Activity 1 - Case study

Your manager has asked you to help produce a handbook that introduces the fundamental
concepts of IoT to new apprentices during their orientation. As part of the handbook, you have
been asked to contribute a case study that looks at which aspects of IoT are necessary and
appropriate when designing software applications. You should use a range of real-world case
studies to demonstrate the different IoT architectures and frameworks. A case study involves an
up-close, in-depth, and detailed investigation of a topic and aims to bring the understanding of a
complex issue or topic within a given context, so bear this in mind when devising the case study.
The case study should provide a positive example of an IoT implementation by giving an
overview of the Internet of things concept by evaluating IoT architecture and justifying that it
can be used in designing software applications. As part of the case study, you should include:

• An exploration of different types of IoT functionality

• A review of the standard IoT architecture, frameworks, tools, hardware, and APIs (AFTHA)
used in development.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

• An analysis of the impact that the use of common IoT AFTHA techniques has in the software
development life cycle (SDLC)
• An examination of specific forms of AFTHA techniques used for different problem-solving
requirements
• An evaluation and justification of the specific forms of IoT architecture used when designing
software applications. As this is a case study format, you should use ‘real-world’ examples from
your research to illustrate the IoT architectures you are discussing.

Activity 2 - Project plan and development report

Your manager would like you to outline a plan and then develop an appropriate IoT application
to achieve the aims of the chosen organization. Before you plan and develop the product, you
will need to identify specifically what problem needs to be solved. You will then use your
research to identify a range of IoT AFTHA techniques and determine which are suitable for
solving this problem and why. You will employ the SDLC and produce evidentiary
documentation in keeping with best practices (software requirements specification, data
distribution service, etc.) to iteratively design and develop an IoT application that meets the
client’s brief. Your project plan should include:
• an investigation of the AFTHA used in the development of IoT applications
• a discussion of the specific problem that the chosen organization wishes to solve using IoT
devices
• a plan for the most appropriate AFTHA to include in the solution to the problem
• the application of the selected techniques to the IoT development plan. You should then
develop the IoT application, using any combination of hardware, software, data, platforms and
services you feel necessary to solve the organization’s problem.

Your development report should include:

• A demonstration of the selection of a set of appropriate tools to turn the development plan
into an IoT application

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

• A set of end-user experiments on the application, with feedback

• An examination and evaluation of the end-user feedback
• A determination of the advantages and disadvantages of the chosen IoT techniques based on
end-user feedback
• A clear demonstration of how user feedback has been used to create multiple Iterations of the
IoT application
• A description of how each Iteration has been modified to provide enhancements based on
user feedback and experimentation.

Activity 3 - Project report

Finally, you will write an accompanying report, with your evidentiary documentation appended,
for your manager, evaluating the success of your final product. The evaluation report must
include:
• A review of the developed IoT application with a detailed description of the problems that it
solves
• An investigation of the potential problems that the IoT application might encounter when
integrating into the organization’s system
• A comparison of the final application with the original plan
• A critical evaluation of the overall success of the application, including the potential impact of
the IoT application on people, business and society, the end user.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Introduction
The Internet of Things (IoT) has become a game-changing technology that links people,
systems, and objects in a smooth network that lets them talk to each other and share data.
IoT helps companies automate chores, be more efficient, and solve tough problems by
linking the real and digital worlds. Because ChannelCert (PVT) Ltd is a top study and
advisory firm, it needs to know how to use IoT technologies to stay ahead in the fast-
paced IT world.

It is the goal of this job to give apprentices-to-be the basic information and skills they
need to understand how IoT works in the real world. By looking at IoT designs,
frameworks, and technologies, the job aims to connect what is learned in school with
what is used in the real world. In this job, you will learn about the functions of IoT, how it
impacts the software development process (SDLC), and how IoT can help businesses
solve problems.

Activity 01
What is IoT (Internet of Things)?

The Internet of Things (IoT) refers to the growing network of actual items or "things" that
are equipped with sensors, software, and other technologies, allowing them to receive and
share data over the internet. These gadgets can range from everyday home things like
freezers and light bulbs to complex industrial machines. Essentially, IoT allows these
things to "speak" to each other, share information, and even take steps automatically,
often without human action.

The main idea behind IoT is to create a better, more connected world where things can
work together and provide improved services or solutions. In an IoT-enabled world, data
is received in real-time, processed, and used to make decisions that improve the
usefulness of the goods and systems they are part of. Whether it's watching the weather in
your home, tracking your fitness goals, or handling tools in a factory, IoT technologies
are playing a significant role in automating processes, improving efficiency, and
enhancing decision-making.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

How IoT Works:

Sensors and Devices: IoT devices are equipped with sensors or controllers to watch the
real surroundings. These sensors can identify a wide range of information like
temperature, humidity, motion, sound, light, or even location. For instance, a smart
thermostat might watch the weather in your home and change the heating or cooling
properly.

Connectivity: Once data is received, it is sent via an internet link to a cloud-based system
or a central computer where it can be examined. IoT devices usually connect using
different types of networks, such as Wi-Fi, Bluetooth, Zigbee, or cellphone networks.
These connection methods guarantee that data is properly transferred across devices.

Data Processing and Analysis: The collected data is sent to a cloud-based website or edge
devices, where it is processed and analyzed. Advanced analytics are applied to turn raw
data into useful insights. For example, in a smart home system, the data could be used to
spot odd patterns of activity, such as unexpected temperature changes, or to learn from
the data to improve gadget performance over time.

Action: Based on the ideas drawn from the data, the system can make automatic choices
or start actions. For instance, if a smart thermostat knows that the room temperature has
fallen below a certain threshold, it can quickly turn on the heater. In other cases, such as
industrial IoT systems, the data might cause alerts or fix requests when gear is showing
signs of wear and tear.

Features of IoT

Interconnectivity: IoT devices are interconnected, meaning they can interact with each
other and share info seamlessly. This interconnectedness allows systems to work jointly,
improving efficiency and accuracy. For example, in a smart home, your refrigerator might
interact with your smartphone app to remember you to buy groceries.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Automation and Control: IoT offers automation by letting devices to work without
manual intervention. This automation can be planned or initiated by specific events. For
example, a smart watering system might automatically water your yard based on soil
moisture levels, saving time and resources.

Real-Time Monitoring and Data Collection: IoT devices constantly gather data from their
surroundings, allowing real-time monitoring. This feature allows companies and people to
track conditions or growth instantaneously. For example, in healthcare, IoT devices like
wearables track vital signs in real time and warn users or healthcare workers to possible
problems.

Remote Access and Management: With IoT, you can watch and handle devices afar using
smartphones, tablets, or computers. For instance, you can change the thermostat in your
home or check the state of your security cameras from anywhere in the world.

Scalability and Flexibility: IoT systems are scalable, meaning new devices or sensors can
be quickly added to the network as the need grows. Whether you're growing your smart
home or scaling up a corporate IoT network, the freedom of IoT makes it adaptable to
various situations.

Applications of IoT:
Smart Homes: IoT allows smart homes where gadgets such as lights, heaters, and security
systems connect to create a more comfy and efficient living environment. For example, a
smart home can instantly change lights depending on the time of day or the presence of
people in the room.

Healthcare: In the healthcare business, IoT allows online patient tracking, where wearable
devices track health measures like heart rate, blood pressure, and movement levels. This
data helps healthcare workers offer personalized treatment plans and early action when
necessary.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Industrial IoT (IIoT): In companies and businesses, IoT helps improve output processes.
Sensors and devices track machine health, product amounts, and energy usage, allowing
for forecast repair, energy saving, and more efficient operations.

Agriculture: IoT has changed agriculture by allowing smart farming methods, where
devices track soil wetness, weather, and crop health. Automated systems then change
watering or provide information to farms to improve yield and reduce waste.

Smart Cities: IoT is being used in urban management to improve traffic flow, track air
quality, control waste, and increase public safety. For example, IoT-enabled traffic lights
can change to real-time traffic conditions, improving traffic flow and cutting delays.

Benefits of IoT
Efficiency: IoT automates jobs and processes, lowering the need for human participation
and improving business efficiency. This leads to time and cost saves.

Improved Decision Making: Real-time data from IoT devices allows better decision-
making by giving insights into system performance, customer behavior, or outdoor
factors.

Enhanced Convenience: IoT devices lower daily work by giving remote control and
automation. For example, smart thermostats learn your likes and change home
temperature for comfort and energy saves.

Cost Savings: IoT helps businesses improve processes, reduce energy waste, and extend
the lifespan of tools, finally saving money.

Better Resource Management: IoT allows better resource allocation by giving insights
into usage trends and helping businesses or people improve how resources like water,
energy, and materials are used.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Various Forms of IoT

The Internet of Things (IoT) can be categorized into several types or forms, depending on
the application, technology, and the environment in which it is deployed. IoT systems are
designed to meet various needs and operate across a wide range of industries. Below, we
explore some of the main forms of IoT.

Consumer IoT (CIoT)

Consumer IoT refers to products and systems that are mainly used by people for personal,
everyday use. These gadgets typically focus on enhancing ease, improving quality of life,
and adding automation to personal environments such as homes, cars, and personal
exercise.

Examples:

Smart Homes: Devices such as smart thermostats (e.g., Nest), lights (e.g., Philips Hue),
and security cameras (e.g., Ring) allow users to handle home settings afar.
Wearables: Fitness trackers (e.g., Fitbit, Apple Watch) record physical movement, health
data, and sleep habits.
Smart Appliances: Devices like freezers, washing machines, and coffee makers that can
be handled remotely or can automatically perform tasks based on user preferences (e.g.,
LG Smart Appliances).
Functions:

Home automation
Personal health monitoring
Enhanced user experiences in daily life
2. Industrial IoT (IIoT)
Industrial IoT focuses on the use of IoT devices in industrial situations to improve
manufacturing processes, supply chain management, and equipment maintenance. IIoT

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

connects machines, sensors, and other industrial assets to allow real-time tracking,
predictive repair, and more efficient production systems.

Examples:

Smart Factories: IoT-enabled machines that watch their own performance, usage trends,
and repair needs (e.g., GE Predix platform).
Predictive Maintenance: Sensors put on machines to spot wear and tear, reducing
downtime and stopping equipment breakdowns.
Supply Chain Tracking: IoT devices used for tracking raw materials, products, and things
across the supply chain in real time (e.g., RFID tags and GPS tracking systems).
Functions:

Equipment health monitoring

Predictive maintenance
Optimization of production processes
3. Commercial IoT (CIoT)
Commercial IoT refers to IoT systems applied in business environments to optimize
processes, improve customer experiences, and increase productivity. Commercial IoT
uses often include inventory control, smart selling, and asset tracking.

Examples:

Smart Retail: IoT-enabled shelves that automatically track inventory levels and reorder
goods when stock gets low.
Asset Tracking: IoT devices track and watch valuable goods in real time, improving
security and efficiency (e.g., RFID-based tracking in warehouses).
Smart Buildings: IoT monitors are used in office buildings to control lighting,
temperature, and energy consumption based on usage (e.g., intelligent HVAC systems).
Functions:

Inventory and asset control

Energy and cost economy in business buildings

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Customer experience improvement

4. Agriculture IoT (AgriIoT)
Agriculture IoT focuses on using IoT technologies to watch and improve agricultural
processes such as crop management, irrigation, animal tracking, and soil condition
monitoring. It helps farmers boost yields, reduce trash, and improve sustainability.

Examples:

Smart watering Systems: IoT-enabled sensors measure soil moisture and weather factors
to automate watering plans, saving water (e.g., CropX).
animals Monitoring: Wearable devices on animals to track health, exercise levels, and
location (e.g., Cowlar smart collars).
Crop Health Monitoring: Drones or sensors used to watch crops for diseases, pests, or
other problems and provide real-time data for better management.
Functions:

Crop and dirt tracking

Livestock health tracking
Automated watering and fertilization systems
5. Healthcare IoT (eHealth/IoMT)
Healthcare IoT, also known as the Internet of Medical Things (IoMT), refers to the use of
connected medical devices to track patient health, handle chronic conditions, and help
healthcare workers in providing personalized treatments. Healthcare IoT allows for
distant tracking, diagnosis, and data-driven decision-making.

Examples:

Wearable Health Devices: Devices like smartwatches or fitness trackers that measure
heart rate, sleep habits, and exercise levels in real-time (e.g., Apple Watch, Fitbit).
Remote Patient Monitoring: Devices that collect and send health data (e.g., blood
pressure monitors, glucose meters) to healthcare workers for remote evaluation and
follow-up.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Smart Hospital Equipment: Connected medical devices in hospitals that watch patient
vitals, track medical supplies, and support telemedicine (e.g., Medtronic's connected
devices).
Functions:

Continuous patient monitoring

Chronic disease management
Remote consults and telemedicine
6. Smart Cities IoT
Smart cities employ IoT technologies to improve urban life by improving infrastructure,
lowering energy consumption, optimizing traffic flow, and ensuring public safety. The
goal is to produce more sustainable, efficient, and livable towns.

Examples:

Smart Traffic Management: IoT sensors and cameras that watch traffic flow, change
traffic lights in real-time, and reduce congestion (e.g., Smart traffic systems in places like
Barcelona).
natural Monitoring: Sensors that sense pollution levels, monitor air quality, and track
natural factors such as noise or water quality.
Smart Street Lighting: IoT-enabled streetlights that change brightness based on time of
day or traffic, lowering energy consumption and improving safety (e.g., Philips
CityTouch).
Functions:

Traffic and transportation improvement

Environmental monitoring
Public safety and energy management
7. Automotive IoT (Connected Cars)
Automotive IoT works on putting IoT technologies into vehicles to improve driving
experiences, safety, and vehicle repair. Connected cars use IoT to provide real-time data
to both drivers and makers, allowing better transportation systems.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Examples:

Telematics Systems: IoT devices that track car data such as speed, fuel usage, engine
performance, and driver behavior.
Autonomous Vehicles: Self-driving cars that depend on IoT systems to interact with other
vehicles, traffic infrastructure, and sensors to make real-time choices.
Vehicle Tracking and Fleet Management: IoT-enabled GPS tracking devices for fleet
management, improving routes, and checking vehicle health.
Functions:

Real-time car performance monitoring

Enhanced safety through automatic methods
Route and fleet planning
8. Environmental IoT (EnvIoT)
Environmental IoT refers to the use of IoT technologies to track and control
environmental factors such as weather, pollution, water quality, and energy consumption.
These tools help in sustainability efforts by giving real-time data to make informed
choices regarding resource usage.

Examples:

Weather Stations: IoT devices that collect weather data such as temperature, humidity, air
pressure, and precipitation levels (e.g., Netatmo Weather Station).
Water Quality Monitoring: IoT monitors that measure pH, turbidity, and pollutant levels
in water bodies to ensure safety and comply with environmental standards.
Energy Management: Smart meters and sensors that track energy usage and improve
power consumption in homes and businesses.
Functions:

Pollution and water quality tracking

Energy usage management
Sustainable resource management

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Exploration of Different Types of IoT Functionality

IoT functionality refers to the diverse capabilities that allow linked devices and systems
to work efficiently, collect data, connect smoothly, process information, and respond
intelligently. These functions form the backbone of IoT communities, driving innovation
and efficiency across different businesses. Below is a full description of the main IoT
functionalities, their benefits, and uses.

1. Data Collection and Sensing

Data collection is a basic IoT trait, driven by sensors built into devices. These devices can
feel and record physical events such as temperature, light, motion, pressure, and chemical
properties. For instance, smart environmental devices track air quality by finding
pollution amounts. Devices such as devices in healthcare track heart rates and physical
activity, showing the varied uses of IoT sensors.

Advantages: Provides accurate and real-time info that improves decision-making and
automates processes.
Applications: Smart homes use motion sensors for security; farming uses soil moisture
sensors for precision watering; and industrial IoT systems deploy vibration sensors for
forecast maintenance.
2. Connectivity and Communication
IoT systems live on link, allowing objects to interact with each other and central systems.
Various communication systems, including Wi-Fi, Bluetooth, Zigbee, and LoRaWAN,
allow device-to-device (D2D) and device-to-cloud (D2C) transfers. Protocols such as
MQTT and CoAP allow lightweight and efficient transfer, especially for low-power
devices. This feature allows seamless interaction across IoT devices.

Advantages: Enables online tracking, fast data sharing, and system scaling.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Applications: Smart city projects use connected sensors for traffic management; transport
systems employ GPS-enabled devices for real-time tracking; and healthcare networks use
IoT devices for patient monitoring.
3. Data Processing and Analytics
After data is gathered, IoT systems handle and study it to draw useful insights. Edge
computing takes data processing closer to the source, cutting delay and rely on cloud
services. For more computationally heavy jobs, cloud systems such as AWS IoT Core and
Microsoft Azure IoT provide powerful data processing capabilities. Data analytics plays a
crucial part in changing raw data into useful information, helping in decision-making and
predictive insights.

Advantages: Enhances efficiency, lowers running costs, and gives predictive information
for proactive measures.
Applications: Predictive repair in production, real-time traffic pattern study in smart
cities, and individual advice in shopping.
4. Automation and Control
IoT allows the automation and remote control of devices through controllers, which turn
digital data into real actions. Automation reduces human participation by allowing
devices to respond freely to set conditions or AI-based decision algorithms. For example,
a smart irrigation system uses soil wetness data to handle watering plans, ensuring
resource economy.

Advantages: Increases working efficiency, reduces human error, and increases comfort.
Applications: Industrial robots, smart home goods (e.g., heaters, lights), and self-driving
cars.
5. Device and Network Security As IoT ecosystems grow, ensuring the security of
devices, data, and networks becomes important. IoT security features include login
methods, end-to-end encryption, safe start processes, and anomaly detection mechanisms.
Blockchain technology is also being adopted to build autonomous and tamper-proof
security systems. Effective security guards the dependability and safety of IoT systems.

Advantages: Protects private info, improves system stability, and stops cyberattacks.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Applications: Financial systems secure deals using protected IoT channels; healthcare
devices ensure data protection; and smart grids protect equipment from illegal access.
6. Energy Management
Energy efficiency is a big factor for IoT devices, especially in rural or resource-
constrained settings. Energy-saving technologies, such as low-power wireless protocols
(e.g., Zigbee, LoRaWAN) and better sleep cycles, help stretch battery life while keeping
value. Advanced IoT energy control systems can also improve energy usage in connected
settings, cutting waste.

Advantages: Reduces running costs, prolongs tool lives, and supports environmental
goals.
Applications: Wearable exercise devices improve battery usage; smart meters in homes
track and control energy consumption; and remote monitors in wildlife tracking rely on
energy-efficient designs.
IoT features combined allow the seamless operation of linked systems, changing
companies and improving quality of life. Each feature serves a unique purpose but adds to
the greater goal of connection, intelligence, and automation. By leveraging these skills,
organizations can create and build better, more efficient systems tailored to their unique
needs.

AFTHA Framework in Development

The AFTHA framework (Analysis, Feasibility, Technical Design, Hardware, and
Architecture) is an important method used in IoT development to ensure that every
crucial part of the system is well-defined and organized. This systematic method allows
for the creation of functional, efficient, and scalable IoT solutions, covering all
components from requirement gathering to hardware integration. Here is a description of
each step within the AFTHA framework:

Analysis
The Analysis phase is the first step in the creation of an IoT system, where the focus is on
knowing the unique needs and requirements of the end users. It includes getting thorough
information from stakeholders, understanding the problems the system aims to solve, and
describing the goals that the system must achieve. During this step, use cases are created,

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

which describe how the IoT system will be used in real-world scenarios. For instance, in
the context of a smart home system, the analysis step would decide the core requirements
such as the ability to handle lights, security systems, and HVAC online.

Feasibility
The Feasibility step studies whether the IoT solution is achievable under the constraints
of time, price, and existing technologies. This step ensures that the project is not only
technically good but also financially possible. In this phase, developers measure the
technical feasibility of the system by reviewing existing technologies, tools, and
platforms to meet the system’s requirements. They also assess financial feasibility,
assessing costs and the return on investment, and operating feasibility, considering things
like user adoption and ease of deployment. For a smart transportation solution, this step
would examine the cost of installing GPS devices and the connection with cloud services,
ensuring the project is realistic and sustainable.

Technical Design
The Technical Design phase is the heart of the system development process, where
thorough planning takes place to describe how different components will work together.
It includes creating the data flow, communication methods, and general interaction of the
system. Security features, data encryption methods, and data processing strategies are also
key factors during this time. For example, in the creation of a healthcare tracking IoT
system, the technical design would describe how the data received from wearable devices,
such as heart rate and oxygen levels, is transferred safely to cloud-based apps for analysis.

Hardware
The Hardware phase focuses on choosing and combining the actual devices and
components that will interact with the system to receive and send data. This step ensures
that the right sensors, actuators, and controllers are chosen based on the system’s unique
needs. Testing the hardware samples for stability, durability, and scalability is also a vital
part of this process. In the case of an industrial IoT system, the hardware step might
include choosing sensors for temperature and pressure tracking, along with actuators for
managing machines. Furthermore, it’s important that these hardware components are
suitable with the software systems in place, ensuring smooth operation.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Architecture
The Architecture step lays out the general framework and organization of the IoT system.
This part outlines how different system components communicate, how data flows across
the system, and what communication protocols are used. The architecture needs to be
built for scalability and performance, as IoT devices often handle large amounts of data.
This part also includes choosing suitable platforms for data processing, such as edge or
cloud computing solutions, based on the system's needs. For example, in an IoT-based
supply chain management system, the design might involve a cloud platform to handle
real-time tracking and analysis of inventory and logistics data.

Review of Standard Architecture, Frameworks, Tools, Hardware, and APIs

(AFTHA) in IoT Development
The Internet of Things (IoT) has transformed how devices connect with people. The
backbone of IoT programming lies in knowing and leveraging its design, frameworks,
tools, hardware, and APIs. Each of these components plays a critical part in ensuring IoT
systems' scalability, security, and efficiency. Below is an expanded and thorough
description of each element.

IoT Architecture IoT architecture gives the basic structure for making IoT systems. It
outlines how data flows between devices, networks, and applications, ensuring the system
runs quickly. The architecture for IoT can change based on complexity, ranging from
simple models to more advanced and layered designs that can handle complicated IoT
applications.

Three-Layer Architecture
The Three-Layer Architecture is a simple but efficient model for IoT systems. It separates
the system into three core layers:

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Perception Layer: This is the layer responsible for receiving data from the real world
through sensors and actuators. These devices connect directly with things in the real
world, such as temperature sensors, cameras, and GPS systems, to gather important data.
Network Layer: This layer allows the transmission of the data received from the
perception layer to cloud platforms or computers where further processing takes place.
This connection usually relies on wireless technologies such as Wi-Fi, Bluetooth, Zigbee,
or even cellular networks.
Application Layer: After the data enters the server or cloud, it is handled in the
application layer, where it is used to serve specific apps. For instance, in smart house
systems, it could be used for controlling gadgets like thermostats, lighting, and security
systems.
This model is widely used due to its simplicity and scalability, especially in apps that
don’t require sophisticated processing.

Five-Layer Architecture
The Five-Layer Architecture extends the Three-Layer model by adding two additional
layers that improve usefulness, especially for complicated systems that require more
detailed control over data processing and management.

Perception Layer: Same as the Three-Layer design, responsible for collecting info.
Network Layer: Similar to the Three-Layer model, it handles data transfer.
Edge Layer: In this extra layer, data can be processed closer to the source (i.e., edge
computing), which lowers latency and the load on cloud platforms by running simple
computations on the IoT devices themselves.
Processing Layer: Here, heavy data processing happens in centralized servers or cloud
settings. It includes complicated analysis, data storage, and AI-driven processes.
Application Layer: Serves the end-user applications, giving insights and actions based on
the data handled in the previous levels.
This design is more suitable for IoT systems that handle large amounts of data, such as
smart towns or industrial IoT applications, where delay and large-scale data processing
are important factors.

Fog Computing Architecture

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Fog computing moves the computing process closer to the IoT devices (in contrast to
cloud computing, where data is handled in centralized data centers). In this model, Fog
Nodes placed closer to the devices handle data processing and storing. This decentralized
approach lowers the amount of data that needs to be sent to the cloud, thus improving
system efficiency. The data is pre-processed on fog nodes before being sent to the cloud,
minimizing delay and cutting bandwidth usage.

Advantages of this design include:

Lower Latency: Reduces data processing time by running tasks locally.

Efficient Data Handling: Limits the need for high speed for real-time apps.
Fog computing is helpful in apps like autonomous vehicles or factory automation, where
real-time choices are important.

Service-Oriented Architecture (SOA)

Service-Oriented Architecture (SOA) in IoT focuses on building systems as a group of

independent services that engage through standardized interfaces and protocols. This
method promotes modularity, allowing IoT systems to integrate and grow easily. SOA
allows diverse devices and apps to work jointly while keeping independence. For
instance, in a smart city setup, SOA enables smooth interaction between traffic
management, garbage management, and public transport systems, ensuring efficient urban
operations.

Advantages

Interoperability: SOA lets products from different companies to work together through
standardized protocols, such as REST or SOAP.
Scalability: It allows easy integration of new devices or services without disrupting the
current system.
Reusability: Services can be reused across different applications, reducing development
costs and work.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

IoT Frameworks
IoT frameworks are common tools and services that provide the necessary components
for the building of IoT applications. They include important features like device
management, data storage, and real-time data processing, which ensure the application’s
usefulness.

Cloud Platforms
Cloud systems for IoT development, such as Microsoft Azure IoT, Google Cloud IoT,
and Amazon Web Services (AWS) IoT, provide the infrastructure needed for launching
IoT apps. These systems offer easy connection to IoT devices and cloud services like data
storage, analytics, and machine learning.

Microsoft Azure IoT: This platform gives a suite of services that help users connect,
monitor, and handle IoT devices. It enables features like predictive maintenance, gadget
lifecycle management, and real-time statistics.
Google Cloud IoT: Similar to Azure, Google’s cloud services offer flexible infrastructure
for IoT solutions, with a focus on ease of device control and real-time data processing.
AWS IoT: AWS provides a complete IoT platform with tools for device authentication,
data storage, and analytics, and works easily with other AWS services like Amazon
Kinesis for real-time data streaming.
These platforms are ideal for developers looking for reliable, scalable options that can
handle a vast amount of data and complex analytics.

Communication Platforms
Communication platforms like MQTT (Message Queuing Telemetry Transport) and
CoAP (Constrained Application Protocol) are important for the safe and efficient sharing
of data between devices and cloud platforms.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

MQTT is a lightweight messaging protocol used for small devices, widely used in settings
with low bandwidth and high-latency conditions, such as smart home applications.
CoAP is similar to HTTP but optimized for low-power and resource-constrained devices,
often used in situations where low energy usage is important.
These protocols allow seamless contact across devices in IoT systems, ensuring data is
transferred efficiently and safely.

Application Platforms Application platforms provide the tools needed for building user
interfaces and handling the data coming from IoT devices. For example:

IBM Watson IoT Platform allows users to monitor and control IoT devices in real-time
while offering data analysis and predictive maintenance features.
ThingSpeak is an open-source IoT tool that focuses on real-time data collection and
analysis, often used in research projects and prototypes.
These tools help developers quickly launch IoT applications without having to build the
infrastructure from scratch.

IoT Tools
IoT tools help the process of making, testing, and managing IoT devices and apps. These
tools help developers prototype devices, model environments, and launch solutions
effectively.

Hardware Prototyping Tools

Prototyping tools are important for quickly making IoT devices. Platforms like Arduino
and Raspberry Pi are popular picks for hardware development.

Arduino is an open-source computing platform built on easy-to-use hardware and

software. It’s widely used to build prototypes for IoT apps like home automation and
sensor tracking.
Raspberry Pi is a small, cheap computer often used for IoT projects. It is equipped with
wireless capabilities and supports different sensors and actuators, making it ideal for
testing linked devices.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

These tools allow developers to build prototypes without the need for detailed hardware
knowledge.

Cloud-Based IoT Platforms

Cloud-based systems like ThingSpeak and IBM Watson IoT provide settings for data
collecting, analysis, and storing. They often include pre-built APIs for connecting IoT
devices, handling large amounts of data, and giving insights to users.

ThingSpeak is often used for academic and study reasons to collect and visualize data
from IoT devices in real-time.
IBM Watson IoT combines IoT devices with the cloud to provide strong AI-driven
analytics and device control features.
These platforms are especially useful when building scalable IoT apps that require
advanced analytics and reliable data stores.

Simulators
Simulators are tools that mimic real-world IoT environments, allowing developers to test
and debug apps without having actual devices. Tools like IoTIFY and Cooja offer
modeling settings where developers can simulate sensor data and device interactions.

IoTIFY is a web-based simulator that helps mimic IoT systems and devices for testing
apps.
Cooja is an open-source IoT model that can simulate wifi networks for low-power
devices.
Simulators allow developers to test their applications in a virtual setting, ensuring they
work as expected before real release.

IoT Hardware
IoT hardware refers to the real components that form the base of an IoT system. These
components are responsible for gathering, processing, and sending info to other gadgets
or systems. The main IoT hardware parts include sensors, microcontrollers, motors, and
communication units. Let’s break these components down:

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Sensors: Sensors are devices that notice physical or environmental changes and turn them
into data that can be used by other devices or systems. Examples include temperature
sensors, motion trackers, light sensors, and humidity sensors. These devices are important
for getting the raw info from the surroundings.

Example: A temperature monitor tracks the ambient temperature in a smart thermostat

device.
Microcontrollers: Microcontrollers are small computing units that process sensor data and
control the IoT system's behavior. These devices often act as the brain of the IoT
hardware, taking input from sensors, processing the data, and causing actions through
motors.

Example: An Arduino board, which is one of the most popular microcontrollers, can be
used in different IoT projects, such as home management systems.
Actuators: Actuators are devices that make real actions in response to orders from the
microcontroller. These can include motors, solenoids, or LEDs. Actuators help IoT
devices to connect with the physical world.

Example: In a smart watering system, an actuator might handle the opening and stopping
of a water valve based on data from soil moisture monitors.
Communication Modules: These are devices that allow the IoT system to interact with
other devices or a cloud platform. Popular connecting methods include Wi-Fi, Bluetooth,
Zigbee, and LoRa. They are important for sending the data received by sensors to the
cloud or other linked devices.

Example: A Wi-Fi dongle lets an IoT gadget to connect to the internet and send data to a
cloud platform for analysis.
In essence, the physical components work together to sense, process, and send data,
allowing IoT systems to gather and act upon information from the surroundings.

IoT APIs

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

APIs (Application Programming Interfaces) are important in IoT systems because they
allow different software applications and hardware components to connect and share data.
In the context of IoT, APIs allow the merger of devices, networks, and cloud platforms by
giving a set of standards for interaction. Let’s look into how IoT APIs work and their
types:

RESTful APIs: These are the most popular type of APIs used in IoT apps. RESTful APIs
allow devices to share and receive data over HTTP using normal HTTP methods such as
GET, POST, PUT, and DELETE. RESTful APIs are lightweight, making them well-
suited for resource-constrained IoT devices.

Example: A smart thermostat may use a RESTful API to send temperature data to the
cloud for processing or to receive orders to change the temperature.
WebSocket APIs: WebSocket APIs support full-duplex communication, meaning they
allow data to move both ways (from client to server and server to client) in real time. This
is particularly useful for apps that require constant data changes or interactions, such as
smart home systems or industrial tracking.

Example: A real-time tracking system for an industrial IoT setup might use WebSocket
APIs to receive live sensor data without any delay.
MQTT (Message Queuing Telemetry Transport): MQTT is a lightweight message system
that’s built for small devices and low-bandwidth, high-latency networks. It is a popular
choice for IoT apps, especially when data needs to be transferred across unreliable or
low-bandwidth lines.

Example: A smoke alarm in a smart home may use MQTT to send a message to the user’s
phone whenever it detects smoke, even if the internet link is slow.
CoAP (limited Application system): CoAP is a system built especially for IoT devices
with limited resources, like low-power sensors. It is similar to HTTP but is more suitable
for the limited powers of IoT devices.

Example: CoAP can be used for communication between smart lightbulbs and their
computers in a low-energy smart lighting system.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

IoT APIs allow smooth contact between devices and cloud platforms, making it easier to
build complicated and scalable IoT apps. APIs act as the bridge that joins physical
components, data storage systems, and user interfaces, allowing data to move and be
acted upon easily.

AFTHA Framework in Development

The AFTHA framework (Analysis, Feasibility, Technical Design, Hardware, and
Architecture) is an important method used in IoT development to ensure that every
crucial part of the system is well-defined and organized. This systematic method allows
for the creation of functional, efficient, and scalable IoT solutions, covering all
components from requirement gathering to hardware integration. Here is a description of
each step within the AFTHA framework:

Analysis
The Analysis phase is the first step in the creation of an IoT system, where the focus is on
knowing the unique needs and requirements of the end users. It includes getting thorough
information from stakeholders, understanding the problems the system aims to solve, and
describing the goals that the system must achieve. During this step, use cases are created,
which describe how the IoT system will be used in real-world scenarios. For instance, in
the context of a smart home system, the analysis step would decide the core requirements
such as the ability to handle lights, security systems, and HVAC online.

Feasibility
The Feasibility step studies whether the IoT solution is achievable under the constraints
of time, price, and existing technologies. This step ensures that the project is not only
technically good but also financially possible. In this phase, developers measure the
technical feasibility of the system by reviewing existing technologies, tools, and
platforms to meet the system’s requirements. They also assess financial feasibility,
assessing costs and the return on investment, and operating feasibility, considering things
like user adoption and ease of deployment. For a smart transportation solution, this step
would examine the cost of installing GPS devices and the connection with cloud services,
ensuring the project is realistic and sustainable.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Technical Design
The Technical Design phase is the heart of the system development process, where
thorough planning takes place to describe how different components will work together.
It includes creating the data flow, communication methods, and general interaction of the
system. Security features, data encryption methods, and data processing strategies are also
key factors during this time. For example, in the creation of a healthcare tracking IoT
system, the technical design would describe how the data received from wearable devices,
such as heart rate and oxygen levels, is transferred safely to cloud-based apps for analysis.

Hardware
The Hardware phase focuses on choosing and combining the actual devices and
components that will interact with the system to receive and send data. This step ensures
that the right sensors, actuators, and controllers are chosen based on the system’s unique
needs. Testing the hardware samples for stability, durability, and scalability is also a vital
part of this process. In the case of an industrial IoT system, the hardware step might
include choosing sensors for temperature and pressure tracking, along with actuators for
managing machines. Furthermore, it’s important that these hardware components are
suitable with the software systems in place, ensuring smooth operation.

Architecture
The Architecture step lays out the general framework and organization of the IoT system.
This part outlines how different system components communicate, how data flows across
the system, and what communication protocols are used. The architecture needs to be
built for scalability and performance, as IoT devices often handle large amounts of data.
This part also includes choosing suitable platforms for data processing, such as edge or
cloud computing solutions, based on the system's needs. For example, in an IoT-based
supply chain management system, the design might involve a cloud platform to handle
real-time tracking and analysis of inventory and logistics data.

Analyse the impact of common IoT architecture, frameworks, tools, hardware, and APIs
in the software development lifecycle":
The Internet of Things (IoT) is a system of interconnected objects and networks that
allow contact and data sharing. The development of IoT apps includes numerous

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

components and steps that have a major effect on the software development lifecycle
(SDLC). These components include design, systems, tools, hardware, and APIs. Each of
these plays a critical role in shaping the design, development, operation, and support of
IoT systems.

1. IoT Architecture and Its Impact on SDLC

IoT design is the foundational structure that explains how all the components of an IoT
system work together, including the sensors, devices, networks, and cloud-based
platforms. It includes different types like Three-Layer Architecture, Five-Layer
Architecture, and Fog Computing Architecture.

Planning & Requirements Gathering: The design plays a key role in identifying the type
of IoT system that will be made, the devices and sensors needed, and how data will be
gathered, handled, and shared. For example, picking a cloud-based architecture or an edge
computing architecture can affect both the hardware needs and the software development
method.

Design & Development: In this step, the design changes how the system’s components
will interact. The Five-Layer Architecture, for instance, focuses on a more thorough
structure of handling data across multiple levels such as perception, network, edge,
processing, and application layers. This impacts how the software components are built
for each layer and how devices will be combined.

Testing & Validation: Depending on the chosen plan, testing methods will change. In Fog
Computing, where some processing is done at the network edge, testing will need to focus
on device touch, latency problems, and the security of edge devices. With cloud designs,
the testing will focus on cloud service interfaces and ensuring data goes easily from
devices to the cloud.

2. IoT Frameworks and Their Impact on SDLC

IoT systems like Google Cloud IoT, Microsoft Azure IoT, and AWS IoT provide ready-
made tools with built-in services that ease the development of IoT apps. These platforms

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

mix various components and take away much of the complexity involved in working with
IoT systems.

create & Development: IoT systems offer tools to create and develop apps more quickly.
They come with libraries, device control features, security standards, and data processing
capabilities, lowering the need for custom code. For example, Microsoft Azure IoT offers
services like device licensing, remote tracking, and cloud-based analytics, which can be
leveraged during development to speed up the development process.

Testing & Validation: Frameworks often come with testing tools built in, such as
simulations or models that can mimic device behavior. For instance, AWS IoT has a
testing setting that helps coders test the link between devices and cloud platforms. This
makes testing faster and more thorough.

Deployment & growth: One of the key perks of frameworks is their built-in growing
features. For instance, in Google Cloud IoT, auto-scaling is a tool that ensures the system
can handle increased device loads quickly. This is especially helpful during rollout, as it
lowers the effort needed to grow the system.

3. IoT Tools and Their Impact on SDLC

IoT creation tools like Raspberry Pi, Arduino, and ESP32 make it easy for makers to
build IoT systems. These tools provide easier sites for prototyping, allowing the
development of IoT apps in a more streamlined and efficient way.

Prototyping: IoT tools are particularly useful during the early stages of development when
trying ideas and concepts. For example, Raspberry Pi allows developers to try IoT
systems by linking sensors, motors, and making simple software systems. This quick
modeling lowers the time spent on starting development.

Development: These tools help in the hardware-software interaction by giving libraries

and models for linking sensors and other components. For instance, Arduino gives code
tools for a wide range of sensors and communication methods, helping writers speed up
the creation process.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Testing & Debugging: IoT tools often come with modeling features that allow developers
to test their applications live. This removes the need for real gadgets in the initial testing
step, making the process faster and more efficient. Tools like Tinkercad provide modeling
settings that mimic real-world scenarios.

4. IoT Hardware and Its Impact on SDLC

The technology used in IoT apps, such as sensors, microcontrollers, and link units, is
important for the general success of the system. Choosing the right hardware has a big
effect on the software creation process.

Planning & Requirements Gathering: The choice of hardware affects the data gathering
methods, power usage, and device compatibility. For instance, a low-power monitor may
require more complicated software methods to ensure data accuracy and transfer
efficiency. The hardware picked will affect the general system design and the software
needed to work with it.

Design & Development: Hardware choice affects the type of standards and software
interfaces needed. For example, when using Zigbee or LoRaWAN communication units,
the software must be built to work with the unique protocols these devices use, affecting
both the application and network layers of the software stack.

Testing & Deployment: Hardware also changes how testing is performed. Developers
need to ensure that the software works effectively with the hardware. Testing hardware
contacts, signal accuracy, power usage, and gadget lives will be part of the SDLC. For
instance, with battery-powered IoT devices, writers must ensure the software is designed
for energy economy.

5. IoT APIs and Their Impact on SDLC APIs (Application Programming Interfaces)
provide a way for different software systems to communicate. In IoT systems, APIs are
important for letting devices, apps, and cloud services to work together.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Design & Development: APIs show how software works with gadgets and services. IoT-
specific APIs, like those given by Twilio or Particle, ease the merger of sensors and
devices into the software. These APIs help coders access computer services, send and
receive data from tools, and perform various other tasks.

Testing & Validation: APIs help in the testing part by giving uniform ways for working
with IoT devices and services. For example, checking API answers for data accuracy,
response time, and security is important to ensure that the system works consistently.

combining & Scalability: APIs allow for easy blending of new services and devices. They
also allow growth, as adding new devices or services to an IoT system often involves just
setting new API addresses. With cloud-based APIs, like those from AWS or Azure, IoT
apps can easily grow to handle additional devices and data points.

This method studies how each component of the IoT system—architecture, frameworks,
tools, hardware, and APIs—affects the various steps of the software development
lifecycle. By learning the role of each of these parts, developers can improve the design,
testing, deployment, and upkeep of IoT apps.

Examine specific forms of IoT architecture, frameworks, tools, hardware and APIs
for different problem-solving requirements.

When building Internet of Things (IoT) solutions, different types of design, platforms,
tools, hardware, and APIs are leveraged to meet specific problem-solving requirements.
Each IoT application has unique needs, and choosing the proper technology can greatly
improve speed, scalability, and efficiency. Below is a study of specific types of IoT
design, frameworks, tools, hardware, and APIs, focused on how they meet particular
problems and requirements:

1. IoT Architecture for Specific Problems

a) Three-Layer Architecture (Perception, Network, Application)

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

The Three-Layer Architecture is widely used for simple IoT systems that involve basic
data collection and sharing. It is split into three layers:

Perception Layer: Responsible for data collection through sensors, motors, and other IoT
devices.
Network Layer: Manages data flow, ensuring that incoming data is sent to a centralized or
edge device for processing.
Application Layer: Encompasses the software systems that handle the data and make
decisions based on the collected information.
Use Case Example:
This design is ideal for smart home applications like temperature control systems, where
simple monitors collect temperature data and send it to a cloud application that changes
the home’s heating or cooling system.

b) Five-Layer Architecture
The Five-Layer Architecture is a more thorough model, often used in large-scale or
complex IoT systems. It breaks the IoT system into extra levels such as the Edge Layer
and Processing Layer, allowing for more refined data processing and lower delay.

Edge Layer: Devices at the edge (such as local ports) process data before sending it to the
cloud.
Processing Layer: Centralized data processing, often utilizing cloud computing or edge
computing tools for in-depth analysis.
Use Case Example: Industrial IoT (IIoT) apps, such as predicted repair for machines, gain
from this design. By processing data at the edge (near the machines) and running deep
analytics in the cloud, makers can predict equipment problems in real time and reduce
downtime.

c) Fog Computing Architecture

Fog computing offers a distributed computing approach, where processing is handled
closer to the data source, such as on edge devices or local networks, reducing the need for
constant cloud connection. This helps in cases where low delay and great dependability
are important.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Use Case Example: Autonomous cars use fog computing to study sensor data on the
vehicle itself (such as for object detection) rather than sending all data to the cloud,
ensuring fast decision-making for safety.
2. IoT Frameworks for Specific Requirements
a) Google Cloud IoT
Google Cloud IoT offers a set of tools for mixing IoT devices with Google Cloud’s data
and machine learning services. It is particularly useful for data-driven apps that require
real-time insights, scalability, and easy contact with other cloud services.

Use Case Example: A smart farm system that gets data from soil moisture sensors,
weather data, and irrigation systems can use Google Cloud IoT to process the data, run
machine learning models to predict water needs, and direct watering.
b) Microsoft Azure IoT
Microsoft Azure IoT is a popular framework for making enterprise-level IoT goods. It
gives cloud services for device control, data store, and analytics, along with strong
security features.

Use Case Example: A connected health system that gets patient data from personal health
monitors and sends it to the cloud for real-time analysis and tells healthcare experts about
odd trends.
c) AWS IoT
Amazon Web Services (AWS) IoT offers flexible, safe cloud-based services for handling
IoT devices and processing big amounts of data. It is great for systems needing high
flexibility and contact with other AWS services, like AWS Lambda or AWS Analytics.

Use Case Example: Smart city systems for traffic tracking can use AWS IoT for handling
thousands of sensors and cameras, processing data in real-time, and putting it into traffic
control systems to improve traffic flow.
3. IoT Tools for Prototyping and Development
a) Raspberry Pi

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Raspberry Pi is a cheap, low-power hardware tool used for IoT testing and creation. It
covers a wide range of sensors and gives major community help. Developers use it to
build proof-of-concept tools and try new IoT solutions.

Use Case Example: An IoT-based home management system, like controlling lights and
appliances through a smartphone app, can be quickly built and tried using a Raspberry Pi
board.
b) Arduino
Arduino is an open-source electronics tool used in IoT for fast development. It includes a
range of boards and shields for linking sensors, actuators, and communication units.

Use Case Example: A weather station that records temperature, humidity, and barometric
pressure data can be built using an Arduino board to collect data and link to the cloud for
distant tracking.
c) Particle.io
Particle.io is an IoT creation tool that offers both hardware and cloud services. It is
designed for fast setup, allowing easy connection with cloud APIs and scaling of devices.

Use Case Example: A fleet management system that uses GPS sensors to track car
movements and sends real-time changes to a cloud platform for study and reports.
4. IoT Hardware for Problem-Solving a) Sensors
Sensors are the core components of an IoT system, used for getting data from the
surroundings. Examples include temperature sensors, motion trackers, pressure sensors,
and light sensors.

Use Case Example: Environmental tracking systems use air quality devices to track
pollution levels and provide real-time data for health groups.
b) Actuators
Actuators are machines that make activities based on received data. They receive input
from IoT controllers and directly change the state of a machine.

Use Case Example: In smart home systems, smart locks act as motors that protect or open
doors based on orders from a mobile app or sensor inputs.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

c) contact Modules Communication modules like Wi-Fi, Bluetooth, LoRa, and Zigbee are
used to make touch between IoT devices. These units are important for sending data to
other devices, cloud systems, or websites.

Use Case Example: LoRaWAN is used in farm systems for long-range, low-power
communication between soil wetness monitors and cloud platforms in rural places.
5. IoT APIs for Integration a) Twilio IoT API
Twilio offers APIs that allow contact between IoT devices and apps. Its API can be used
for text, voice, and video features in IoT systems.

Use Case Example: A smart home security system using Twilio APIs to send SMS alerts
or make automatic phone calls when a security break is found.
b) Particle Cloud API
Particle Cloud API allows users to connect IoT devices to the cloud quickly, giving
features like device control, data storage, and analytics.

Use Case Example: A smart lighting system where devices connect via Particle’s API to a
cloud platform to allow remote control through mobile apps.
c) IBM Watson IoT API
IBM Watson offers a set of APIs built for mixing AI and analytics with IoT data. It can
handle big amounts of data and run machine learning models on real-time IoT inputs.

Use Case Example: A predictive maintenance system that analyzes data from industrial
tools and uses Watson’s API to predict problems before they show.
By knowing and choosing the proper IoT design, framework, tools, hardware, and APIs,
developers can build highly efficient and personalized IoT solutions for specific problem-
solving needs. Whether the goal is improving working efficiency, enhancing user
experience, or lowering costs, getting the right mix of these tools is crucial in achieving
ideal results.

Evaluate specific forms of IoT architecture and justify their use when designing
software applications.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

In the fast changing world of the Internet of Things (IoT), picking the right architecture is
important to the success of IoT-based software apps. The choice of design affects data
handling, scalability, delay, and total system efficiency. This review discusses the most
widely used IoT architectures and gives real-world cases to show their usefulness in
software development.

1. Three-Layer IoT Architecture

The Three-Layer IoT Architecture is the best and most widely used approach. It consists
of three main layers: the Perception Layer, the Network Layer, and the Application Layer.

Perception Layer: This layer includes all IoT devices such as sensors, actuators, and other
gear responsible for data gathering and touch with the real world. It turns physical factors
(e.g., temperature, humidity, movements) into computer messages.
Network Layer: The data collected by devices in the Perception Layer is transferred to
other devices, computers, or cloud platforms through communication networks. The
network layer handles technologies like Wi-Fi, Zigbee, Bluetooth, and LoRaWAN.
Application Layer: This layer handles the data received from the Perception and Network
layers, giving end users with useful information, such as through a mobile app or a web-
based monitor. It also includes the core processes and data tools that drive decision-
making.
Real-World Example: Smart Home Systems (e.g., Nest Thermostat)
A smart home system, such as Nest Thermostat, is a normal form of Three-Layer
Architecture. In this application:

The Perception Layer includes the smart thermostat's temperature and humidity devices.
The Network Layer uses Wi-Fi to send the info to the cloud or a centralized hub.
The Application Layer gives users with control through a mobile app, allowing remote
changes and energy-saving information.
Justification:

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

The Three-Layer Architecture is ideal for small-scale IoT apps that require simplicity and
efficiency, such as smart homes or simple environmental tracking systems. It allows easy
integration of IoT devices with cloud-based systems and provides a simple user
experience. However, its flexibility and usefulness for real-time data handling are limited
compared to more complicated systems.

2. Five-Layer IoT Architecture

The Five-Layer IoT Architecture builds on the Three-Layer approach by adding extra
layers for edge computing and centralized data processing. The layers in this model
include:

Perception Layer: Responsible for data collection.

Network Layer: Responsible for data transfer.
Edge Layer: Processes data closer to the source, using edge devices like ports to perform
initial data screening, gathering, and analysis.
Processing Layer: The cloud-based layer where more intense data processing, storage,
and advanced analytics are performed.
Application Layer: Provides the user experience and handles the processing data.
Real-World Example: Industrial IoT (IIoT) - GE Predix
General Electric’s Predix software for Industrial IoT (IIoT) is a great example of a Five-
Layer IoT Architecture:

The Perception Layer includes IoT devices put on industrial tools like engines and pumps.
The Network Layer handles data flow over industrial-grade transmission networks like
Ethernet or 5G.
The Edge Layer processes data locally on industrial ports to spot instant equipment flaws
and anomalies.
The Processing Layer in the cloud handles deep data analytics, predictive maintenance,
and operations optimization.
The Application Layer gives plant workers with screens for real-time tracking and
decision-making.
Justification:

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

The Five-Layer Architecture is great for Industrial IoT (IIoT) and other large-scale apps
that require real-time data processing and advanced analytics. The launch of the Edge
Layer lowers latency by handling data closer to the source, ensuring quick actions in
mission-critical systems. This system also allows for scalable cloud-based processing,
which is important for handling big amounts of data. However, it may raise system
complexity and cost due to the need for extra edge devices and more advanced
infrastructure.

3. Fog Computing Architecture

Fog Computing extends cloud computing by performing computation at the network's
edge, closer to IoT devices. Fog Computing offers a more distributed and independent
way to data handling. It lowers the pressure on the cloud by offloading work and data
saving to intermediate devices like gates, routers, or edge servers.

Real-World Example: Autonomous Vehicles (Tesla)

Tesla’s Autonomous Vehicles provide a great real-world example of Fog Computing:

The Perception Layer includes different devices (e.g., cameras, LIDAR, radar) that collect
real-time data on the vehicle's surroundings.
The Fog Layer handles this info directly on the car, making real-time choices (e.g.,
stopping, turning) to ensure safety.
The Cloud Layer saves the car data and regularly changes algorithms for long-term
learning and improvements.
Justification:
Fog Computing is particularly successful in apps where low delay and real-time decision-
making are important, such as driverless cars, smart healthcare, or industrial robots. By
handling data directly on edge devices, it lowers latency and improves speed. However,
setting up a fog computer system may increase original execution costs and complexity.

4. Cloud-Based IoT Architecture

Cloud-based IoT design focuses on the cloud for unified data storage, computing, and
analytics. This design is highly scalable and flexible, making it ideal for apps that need to
handle big amounts of data from various sources over long times.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Real-World Example: Smart Grid Systems (PG&E)

The Smart Grid system used by Pacific Gas and Electric (PG&E) is an example of Cloud-
based IoT architecture:

The Perception Layer consists of smart meters and gadgets that track energy usage and
grid health.
The Network Layer uses connectivity methods (e.g., 4G, LPWAN) to send info from
meters to the cloud.
The Cloud Layer handles the data, giving utilities with predictive analytics, demand
forecasts, and grid optimization.
Justification:
Cloud-based IoT is ideal for large-scale, data-intensive apps like smart grids, smart cities,
or logistics tracking. Its freedom makes it easy to handle vast amounts of data and people.
The cloud design also allows for advanced analytics, machine learning, and AI
interaction. However, its dependence on a stable internet link and cloud services can
result in higher running costs.

5. Service-Oriented Architecture (SOA)

In Service-Oriented Architecture (SOA), IoT devices and apps are viewed as individual
services that interact over standardized interfaces. Each service takes a specific job (e.g.,
data collecting, processing, or device control), making the system modular and scalable.

Real-World Example: Smart Buildings (Cisco IoT Solutions)

Cisco’s Smart Building Solutions are a real-world version of SOA:

The Perception Layer includes devices for lights, HVAC systems, and movement
tracking.
The Service Layer lets different IoT devices and services (lighting, energy management,
security) to connect with each other via APIs.
The Application Layer offers unified control for building managers, combining all the
services into a single user experience.
Justification:

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

SOA is ideal for big, complicated IoT systems that require connectivity across multiple
devices and services, such as smart buildings or enterprise-level IoT apps. Its flexible
method allows for easy growth and freedom in adding new services or devices. However,
choosing SOA requires careful planning to ensure interoperability between different
devices and services.

Conclusion
In conclusion, the choice of IoT platform greatly affects the design and performance of
IoT software applications. For simple uses like smart home systems, the Three-Layer
Architecture is ideal. Five-Layer Architecture and Fog Computing are better fit for
industrial IoT systems and apps needing real-time data handling. Cloud-based IoT excels
in large-scale, data-intensive apps, while SOA offers freedom and scalability for difficult,
combined IoT systems. By choosing the proper design, organizations can achieve their
IoT goals more effectively, whether it’s for enhancing user experiences, improving
business efficiency, or allowing innovation.
Activity 02
Investigate Architecture, Frameworks, Tools, Hardware, and API Techniques
Available to Develop IoT Applications.

To build IoT (Internet of Things) apps, a variety of designs, frameworks, tools, devices,
and APIs are available to ensure easy contact, data processing, and overall usefulness.
This study will explore these methods and technologies to determine the most suitable
ones for making effective and scalable IoT solutions.

1. IoT Architecture IoT frameworks provide the structural base for how gadgets,
networks, and apps link with each other. Here are the most famous IoT architectures:

Three-Layer Architecture:

Perception Layer: This is the actual layer that includes IoT devices (e.g., sensors, motors,
and smart devices). It gets real-time data such as temperature, humidity, or GPS location.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Network Layer: The data collected from the perception layer is passed through
communication networks (e.g., Wi-Fi, 4G/5G, Zigbee, LoRaWAN) to the next layer.
Application Layer: This layer handles the data and serves as the link for end-users. It is
where decision-making, research, and human contact happens. Examples include cloud-
based tools and apps that show insights from the collected data.
Five-Layer Architecture: An adaptation of the three-layer pattern with extra layers:

Perception Layer Network Layer

Edge Layer: Handles local data processing to reduce delay before sending the data to the
cloud.
Processing Layer: Processes data in real-time for analysis, often deploying cloud
computers and big data analytics.
Application Layer
This design is usually used for more complex IoT systems that require local computation
or edge processing.

2. IoT Frameworks
Frameworks are important for making IoT apps as they provide the necessary building
blocks for planning, developing, and scaling IoT solutions. Here are some widely-used
IoT frameworks:

AWS IoT:

Amazon Web Services (AWS) offers a full IoT framework that helps connect devices
safely, handle data, and run device fleets. AWS IoT works easily with other AWS
services like AWS Lambda for serverless computing, Amazon S3 for storage, and
Amazon SageMaker for machine learning.
Microsoft Azure IoT:

Azure IoT offers services for joining, tracking, and running IoT devices. It gives choices
such as Azure IoT Hub for device control, Azure Stream Analytics for real-time data
processing, and Azure Digital Twins for modeling IoT systems.
Google Cloud IoT:

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Google Cloud IoT offers a tool for safely connecting and handling IoT devices. It allows
tools like Google Cloud Pub/Sub for messaging, Google Cloud Functions for serverless
computing, and Google BigQuery for studying big datasets.
ThingSpeak:

ThingSpeak is an open-source IoT platform that allows users to receive, study, and show
data in real-time. It's built for small-scale IoT apps, ideal for data logging, sensor
readings, and easy analytics.
Kaa IoT:

Kaa is an open-source IoT platform that offers device control, data analytics, and real-
time contact. It can be paired with custom IoT systems and is highly adaptable for
different use cases.
3. IoT Tools Tools are important for making and handling IoT apps. They allow gadget
integration, data handling, and real-time processing:

Node-RED:

Node-RED is a visual programming tool that allows users to wire together hardware
devices, APIs, and online services. It is widely used in IoT apps for fast development and
device interaction. Node-RED offers a range of standards like MQTT, HTTP, and
WebSockets.
Eclipse IoT:

Eclipse IoT offers a set of open-source projects that help in the building of scalable IoT
solutions. Key tools include Eclipse Paho (for MQTT messages), Eclipse Kura (an IoT
gateway platform), and Eclipse Smarthome (for smart home control).
Mosquitto (MQTT Broker):

Mosquitto is an open-source MQTT broker that allows lightweight messages for small
devices and low-bandwidth conditions. It's used in IoT for sending info from gadgets to
central computers or cloud services.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Zetta:

Zetta is a Node.js-based tool for making API-driven IoT apps. It helps developers to build
RESTful APIs for IoT devices, which can be reached remotely by other apps.
4. IoT Hardware Hardware is the base of IoT systems, as gadgets need to gather and send
data. Some famous IoT hardware components include:

Raspberry Pi:

Raspberry Pi is a low-cost, high-performance single-board computer widely used for IoT

projects. It supports different computer languages, GPIO (General Purpose Input/Output)
pins for hardware connections, and Wi-Fi or Ethernet for communication.
Arduino:

Arduino is an open-source microprocessor platform used for making interactive electronic

toys. It can be paired with different sensors (temperature, humidity, motion, etc.) and tied
to the internet using Wi-Fi or Ethernet shields.
ESP8266 / ESP32:

These are low-cost computer boards with built-in Wi-Fi (ESP8266) or Wi-Fi/Bluetooth
(ESP32) features. They are widely used in small IoT apps due to their tiny size and low
power usage.
BeagleBone:

BeagleBone is a low-cost, open-source creation tool for IoT apps. It offers a range of
connection choices and high-speed processing, making it ideal for more challenging IoT
jobs.
Smart Sensors:

monitors such as temperature, pressure, light, and motion monitors are important
components of any IoT system. These gadgets collect real-time weather data and send it
to IoT systems for study.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

5. IoT APIs APIs (Application Programming Interfaces) allow different systems to

connect and share info. Several IoT APIs allow touch between gadgets, platforms, and
services:

Google Maps API:

Google Maps API offers tracking and mapping features for IoT apps. It can be used for
location tracking, route planning, and direction in IoT-based transportation systems, such
as fleet management.
Twilio API:

Twilio offers contact services for IoT apps, including SMS, email, and chat. For IoT
devices, it allows for information to be sent to users (e.g., low battery alerts, device state
changes).
IFTTT (If This Then That):

IFTTT is a service that allows users to build custom automatic rules between different
IoT devices and services. It can be used for connecting IoT apps with third-party services
(e.g., causing acts when specific conditions are met).
OpenWeatherMap API:

The OpenWeatherMap API offers weather data, which can be merged into IoT systems
for uses like smart home control, farming tracking, and environmental sensors.
Firebase Realtime Database:

Firebase offers a cloud-based real-time database that can be used to keep and share data
from IoT devices in real-time. It is widely used for mobile and web services needing fast
data sharing across devices.

Conclusion
When building IoT apps, a mix of design, frameworks, tools, hardware, and APIs is
needed to ensure the system works easily. The design outlines the flow of data, while
structures and tools help connect and handle devices, process data, and show results to

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

users. The hardware gets data, and APIs allow touch between the system components. By
picking the most suitable IoT frameworks and tools and pairing the right hardware and
APIs, developers can build robust, scalable, and efficient IoT solutions.

Discussion of the Specific Problem that the Chosen Organization Wishes to Solve
Using IoT Devices.

A Look at PickMe
PickMe is a company in Sri Lanka that makes rides and sends goods. Real-time
relationships between clients and drivers are what the company does best. PickMe is
having more and more problems running its business as it gets more customers. These
problems mostly come up when demand changes, when arranging rides efficiently, and
when making sure that trips happen on time.

These problems can slow things down, make customers and drivers angry, and hurt the
company's image and bottom line.

Problems and tasks that matter

1. Long wait times for customers
Right now, the system that gives rides can't match drivers and customers in the best way
possible in real time. This often leads to longer wait times, especially during peak hours
or in high-demand places.
Effect: Customers get annoyed when they have to wait a long time, and this can make
them switch to a different business.
Reduced customer happiness affects growth and business trust.
2. Inefficient Resource Utilization Current Situation: Drivers are often spread widely,
with some places having an excess while others face a lack.
Idle drivers in low-demand areas stay unutilized, while high-demand zones fight to meet
customer needs.
Impact: Increased running costs as cars waste time and fuel.
Less money for drivers because fewer rides are being taken.
3. Lack of Real-Time Insights

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Current Situation: The system needs better tools to track and predict ride demand and
supply in real-time.
Manual actions are often needed to transfer drivers, which are slow and costly.
Impact: Delays in responding to demand spikes, leading to missed income chances.
Limited ability to change routes automatically based on road conditions.
4. Poor Customer Experience
Current Situation: Delayed pickups and lack of rides during busy times result in frequent
customer complaints.
Limited touch with customers about expected wait times or different choices.
Impact: Negative reviews and comments hurt the company's image.
Customers may move to competitors offering faster and more reliable services.
How IoT Devices Can Solve These Problems
IoT (Internet of Things) technology offers a creative way to handle these problems by
mixing real-time data collection, processing, and decision-making into PickMe’s
operations. Below are the IoT-enabled choices for each listed problem:

1. GPS Trackers for Real-Time Driver Location Solution: Equip driver devices with IoT-
enabled GPS trackers.
Benefits: Provides real-time position info for all cars.
Enables the system to find the nearest available driver to a customer request fast.
Example: A customer books a ride in a busy area, and the system gives the closest driver
within seconds, cutting wait times greatly.
2. Demand Monitoring Sensors Solution: IoT demand sensors in high-traffic places like
airports, shops, and city centers.
Benefits: Tracks ride requests and demand jumps in real-time.
Allows proactive shifting of drivers to high-demand places before holes appear.
Example: When demand jumps at an airport due to a flight landing, the system sends
nearby cars to the spot.
3. Edge Computing Devices for Faster Processing Solution: Deploy edge computing
devices to handle data processing closer to the source (e.g., within regional hubs).
Benefits: Reduces delay in decision-making.
Ensures continued actions even if central computers face downtime.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Example: During peak hours, edge devices can process data locally to give rides faster
without counting solely on the cloud.
4. Predictive Analytics for Demand Forecasting Solution: Use IoT data mixed with
machine learning models saved on cloud platforms.
Benefits: Predicts market trends based on past data, weather, and events.
Pre-allocates cars to places likely to have high demand.
Example: On a rainy evening, the system predicts a boost in ride requests and tells drivers
to move to crowded areas in advance.
5. Connected Dashboards for Drivers and Administrators
Solution: IoT-enabled apps and screens for drivers and managers.
Benefits: Drivers receive real-time information about ride orders and better routes.
Administrators can watch the system's progress and make informed choices fast.
Example: Drivers get told about traffic jams and receive different paths to reach
customers faster.
Expected Outcomes of IoT Implementation
1. Reduced Customer Wait Times
By quickly distributing rides to the nearest available drivers, customers experience faster
pickups, even during busy times.
2. Enhanced Resource Utilization
Real-time tracking and smart redistribution ensure optimal use of drivers, cutting idle
times and improving pay.
3. Improved Operational Efficiency
Edge computing and predictive analytics ease processes and reduce dependency on
human actions.
4. Higher Customer Satisfaction
Faster reply times, open communication, and regular access of rides improve the entire
customer experience.
5. Competitive Advantage
By deploying IoT technology, PickMe can place itself as a star in the ride-hailing
business with better service quality.
Conclusion
Using IoT devices like GPS trackers, demand sensors, edge computing, and predictive
analytics, PickMe can solve its core problems of ride sharing mistakes and customer wait

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

times. This change not only boosts working efficiency but also improves customer
happiness, driver engagement, and long-term business growth.

Plan for the Most Appropriate AFTHA to Include in the Solution.

To solve the problems PickMe faces with inefficient ride sharing and long customer wait
times, we need to combine the right Architectures, Frameworks, Tools, Hardware, and
APIs (AFTHA). Here's a thorough plan on how each component can be applied to build
an effective IoT system.

1. IoT Architecture
Chosen Architecture: Three-Layer IoT Architecture A Three-Layer IoT Architecture is
well-suited for this use case as it is flexible, stable, and handles real-time data well. The
three layers are:

Perception Layer: The gadgets and sensors that gather real-time info.

Sensors: GPS trackers on drivers’ smartphones or cars will provide real-time location
info.
Demand Sensors: Installed in busy places (e.g., airports, malls) to sense customer demand
and send messages to the system.
Network Layer: Ensures the info moves from the perception layer to the computing units.

contact Protocols: Use cellphone networks (e.g., 4G/5G) or Wi-Fi for contact between
sensors, devices, and cloud services. This provides real-time transmission of location and
demand info.
Application Layer: This is the software tool that handles the info and makes choices.

Backend Servers (Cloud): Cloud platforms like AWS IoT or Google Cloud IoT handle
the large-scale data and analytics to improve ride sharing.
End-User Interface: A mobile program (for customers and drivers) that shows
information in real-time, such as available drivers and expected wait times.
2. Frameworks

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Frameworks provide set structures and tools to speed up development and ensure
accuracy.

Chosen Frameworks: Edge Computing Framework: Since latency is important in real-

time systems, we can use Edge Computing to process data closer to where it’s created. By
making calculations locally (on the driver’s device or nearby edge devices), we lower
response time and avoid delays in ride matching.

Cloud Computing Framework: Cloud platforms like AWS IoT Core or Google Cloud IoT
will be used to collect, evaluate, and handle data from all drivers and users. They will also
keep large amounts of historical data, which is crucial for predictive analytics and ride
demand forecasts.

Machine Learning Framework: To improve the distribution of rides, we can use machine
learning frameworks like TensorFlow or Scikit-Learn to build predictive models. These
models will predict areas of high demand and help change ride allocation constantly.

3. Tools Tools are the software solutions and platforms that will be used to create, build,
and monitor the IoT application.

Chosen Tools: ThingSpeak: An IoT control tool that allows real-time tracking of devices
and sensors. It can gather data from sensors and show it in real-time.

Power BI or Google Data Studio: These tools will show key data, like customer wait
times, driver availability, and demand forecasts. Real-time dashboards can help
management teams in decision-making.

IDEs for Development: Tools like Visual Studio Code or Eclipse will be used to write the
code for the mobile apps (for drivers and customers) and server systems. These
environments offer support for making cross-platform apps (Android, iOS).

4. Hardware The hardware involved will be used to capture data, track the state of
vehicles, and ensure that the system works in real-time.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Chosen Hardware: GPS Sensors/Devices: Each driver will have a GPS device on their
phone that constantly sends their position to the system. This will help in real-time
tracking and ride matching.

Demand Sensors: These sensors can be put in high-traffic areas (like airports, shopping
centers, and tourist locations) to detect when people are likely to need rides. This info will
feed into the system and help predict where more drivers will be needed.

Smartphones/Tablets: The mobile devices used by drivers and customers will act as
interfaces for sharing and getting data. Drivers will be able to accept ride requests, and
passengers will get real-time reports on their ride progress.

5. APIs
APIs are important for integrating external services and ensuring smooth operation within
the IoT environment.

Chosen APIs:
Google Maps API: This API offers maps, routing, and traffic information. It will be used
to track drivers' real-time location and provide the best way to a passenger. It will also
help in predicting traffic patterns to change driver allocations appropriately.

Ride Matching API: This custom API matches drivers to passengers based on location,
road conditions, and other real-time factors. This API can also consider things like user
ratings and interests for a better user experience.

Weather API: Weather data is important for expecting demand spikes (e.g., during rainy
or snowy weather, there may be a rise in ride requests). This API will feed weather data
into the system to change the ride sharing in real-time.

Payment Gateway API: APIs like Stripe or PayPal will link payment services into the
app, allowing users to make payments straight through the app.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Conclusion
By combining these AFTHA components, PickMe will be able to optimize ride
allocation, reduce customer wait times, and improve the general efficiency of their
operations. The IoT Architecture will ensure seamless connection and real-time
processing, while the Frameworks provide a strong structure for development. The Tools
will help organize and study data, while the Hardware ensures real-time tracking. Finally,
the APIs will combine external services like guidance, payment processing, and weather
forecasting to improve the overall system’s usefulness.

This plan will not only handle the current problems but also ensure scalability and
flexibility in future versions.

Application of Selected Techniques to the IoT Development Plan

To solve the problems PickMe faces with inefficient ride sharing and long customer wait
times, we need to combine the right Architectures, Frameworks, Tools, Hardware, and
APIs (AFTHA). Here's a thorough plan on how each component can be applied to build
an effective IoT system.

1. IoT Architecture
Chosen Architecture: Three-Layer IoT Architecture A Three-Layer IoT Architecture is
well-suited for this use case as it is flexible, stable, and handles real-time data well. The
three layers are:

Perception Layer: The gadgets and sensors that gather real-time info.

Sensors: GPS trackers on drivers’ smartphones or cars will provide real-time location
info.
Demand Sensors: Installed in busy places (e.g., airports, malls) to sense customer demand
and send messages to the system.
Network Layer: Ensures the info moves from the perception layer to the computing units.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

contact Protocols: Use cellphone networks (e.g., 4G/5G) or Wi-Fi for contact between
sensors, devices, and cloud services. This provides real-time transmission of location and
demand info.
Application Layer: This is the software tool that handles the info and makes choices.

Backend Servers (Cloud): Cloud platforms like AWS IoT or Google Cloud IoT handle
the large-scale data and analytics to improve ride sharing.
End-User Interface: A mobile program (for customers and drivers) that shows
information in real-time, such as available drivers and expected wait times.
2. Frameworks
Frameworks provide set structures and tools to speed up development and ensure
accuracy.

Chosen Frameworks: Edge Computing Framework: Since latency is important in real-

time systems, we can use Edge Computing to process data closer to where it’s created. By
making calculations locally (on the driver’s device or nearby edge devices), we lower
response time and avoid delays in ride matching.

Cloud Computing Framework: Cloud platforms like AWS IoT Core or Google Cloud IoT
will be used to collect, evaluate, and handle data from all drivers and users. They will also
keep large amounts of historical data, which is crucial for predictive analytics and ride
demand forecasts.

Machine Learning Framework: To improve the distribution of rides, we can use machine
learning frameworks like TensorFlow or Scikit-Learn to build predictive models. These
models will predict areas of high demand and help change ride allocation constantly.

3. Tools Tools are the software solutions and platforms that will be used to create, build,
and monitor the IoT application.

Chosen Tools: ThingSpeak: An IoT control tool that allows real-time tracking of devices
and sensors. It can gather data from sensors and show it in real-time.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Power BI or Google Data Studio: These tools will show key data, like customer wait
times, driver availability, and demand forecasts. Real-time dashboards can help
management teams in decision-making.

IDEs for Development: Tools like Visual Studio Code or Eclipse will be used to write the
code for the mobile apps (for drivers and customers) and server systems. These
environments offer support for making cross-platform apps (Android, iOS).

4. Hardware The hardware involved will be used to capture data, track the state of
vehicles, and ensure that the system works in real-time.

Chosen Hardware: GPS Sensors/Devices: Each driver will have a GPS device on their
phone that constantly sends their position to the system. This will help in real-time
tracking and ride matching.

Demand Sensors: These sensors can be put in high-traffic areas (like airports, shopping
centers, and tourist locations) to detect when people are likely to need rides. This info will
feed into the system and help predict where more drivers will be needed.

Smartphones/Tablets: The mobile devices used by drivers and customers will act as
interfaces for sharing and getting data. Drivers will be able to accept ride requests, and
passengers will get real-time reports on their ride progress.

5. APIs
APIs are important for integrating external services and ensuring smooth operation within
the IoT environment.

Chosen APIs:
Google Maps API: This API offers maps, routing, and traffic information. It will be used
to track drivers' real-time location and provide the best way to a passenger. It will also
help in predicting traffic patterns to change driver allocations appropriately.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Ride Matching API: This custom API matches drivers to passengers based on location,
road conditions, and other real-time factors. This API can also consider things like user
ratings and interests for a better user experience.

Weather API: Weather data is important for expecting demand spikes (e.g., during rainy
or snowy weather, there may be a rise in ride requests). This API will feed weather data
into the system to change the ride sharing in real-time.

Payment Gateway API: APIs like Stripe or PayPal will link payment services into the
app, allowing users to make payments straight through the app.

Conclusion
By combining these AFTHA components, PickMe will be able to optimize ride
allocation, reduce customer wait times, and improve the general efficiency of their
operations. The IoT Architecture will ensure seamless connection and real-time
processing, while the Frameworks provide a strong structure for development. The Tools
will help organize and study data, while the Hardware ensures real-time tracking. Finally,
the APIs will combine external services like guidance, payment processing, and weather
forecasting to improve the overall system’s usefulness.

This plan will not only handle the current problems but also ensure scalability and
flexibility in future versions.

Application of Selected Techniques to the IoT Development Plan

In this part, we'll outline how the chosen AFTHA (Architecture, Frameworks, Tools,
Hardware, and APIs) methods will be applied to develop an IoT solution that solves
PickMe's problem of poor ride sharing and long customer wait times.

1. IoT Architecture: Three-Layer Architecture

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Perception Layer: Hardware: The perception layer will include GPS devices on drivers'
smartphones and demand sensors at key places such as airports and shopping malls.
These devices will gather real-time data on car position, customer demand, and traffic
conditions.
Example: Using GPS, each vehicle will transmit its present location to the central system,
which allows the system to find the nearby available vehicle for each customer.
Network Layer: Software: Data from the awareness layer will be transferred via wireless
networks (e.g., 4G/5G, Wi-Fi) to the cloud platform for further processing.
Cloud Platform: AWS IoT Core or Google Cloud IoT will be used to safely receive, store,
and handle the incoming data from devices.
The communication protocols will ensure safe and efficient sharing of real-time data,
allowing dynamic ride matching and real-time system updates.
Application Layer: Software: The application layer will involve mobile apps for
customers and drivers, where the ride sharing will be handled.
For drivers, a mobile app will allow them to accept or reject ride requests, view current
location, and route to the passenger's location using Google Maps API.
For riders, the app will show real-time location data, expected arrival times, and enable
ride payment via payment gateway APIs like Stripe or PayPal.
2. Frameworks: Cloud Computing, Machine Learning, and Edge Computing
Cloud Computing (AWS IoT Core / Google Cloud IoT): Cloud Platform will be used for
large-scale data gathering, processing, and analytics. It will handle the core code to
process data from cars and sensors, including ride allocation algorithms and traffic
prediction models.
Data Processing: Data from GPS devices and demand sensors will be saved in the cloud
for past analysis and predictive modeling to improve ride allocation.
Machine Learning (TensorFlow, Scikit-learn):
Ride Matching Algorithm: Using machine learning, the system will study past data and
predict demand surges, allowing it to preemptively assign resources (drivers) to areas
with expected high demand.
Traffic Prediction: By using past data, the system will also predict traffic patterns and
delays, helping improve the matching of customers with drivers to minimize wait times.
Edge Computing: Edge devices (e.g., smartphones) will handle some local processing to
lower the load on the cloud and decrease latency. For instance, if a driver is near a

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

passenger, their devices will quickly match them locally without having to wait for cloud
processing.
3. Tools: ThingSpeak, Power BI, and IDEs
ThingSpeak for Real-Time Data display: ThingSpeak will be used for data gathering and
real-time display. Data from the GPS and demand devices will be posted to ThingSpeak
and examined.
It will create a live screen for operations to track the location of cars and places with high
demand in real-time.
Power BI/Google Data Studio for Reporting: Data Visualization tools like Power BI or
Google Data Studio will help managers to track business success through dashboards.
important Metrics: They will show important metrics such as average wait time, fleet
availability, and ride density in certain areas.
IDEs for Application Development:
Mobile Application Development: Using Android Studio and Visual Studio Code, the
mobile apps for drivers and passengers will be created, allowing them to connect with the
system in real time.
4. Hardware: GPS Devices, Demand Sensors, Smartphones
GPS Devices (Driver’s Smartphones): Real-time location tracking: The driver’s mobile
phone will work as the GPS device, giving real-time location data to the cloud server.
This means that guests are matched with the closest available drivers.
Example: If a driver is located near a passenger, the system will use this info to offer the
ride instantly.
Demand Sensors:
Sensor Deployment: Demand sensors will be put at high-traffic places to watch demand
fluctuations. These devices will recognize the number of people in an area and send this
information to the server to change the ride sharing accordingly.
Example: At a shopping mall, the system might increase the number of drivers in the area
during busy hours based on sensor data.
Smartphones/Tablets (Driver and Passenger Apps): Driver App: The driver’s app will
show ride requests, passenger locations, and directions using Google Maps API.
Passenger App: The passenger’s app will provide location info, estimated ride times, and
payment choices via payment gateway APIs.
5. APIs: Google Maps, Ride Matching API, Weather API, Payment Gateway

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Google Maps API: Navigation and Ride Matching: The Google Maps API will be used to
generate optimal routes between drivers and clients, taking into account real-time traffic
data.
Example: If a driver is near a passenger, Google Maps will show the shortest path based
on traffic data to reduce the wait time.
Ride Matching API: A custom ride matching algorithm will be created to match
customers with the closest available drivers based on location, traffic trends, and demand
forecasts.
Ride Matching Process: The system will match drivers with passengers dynamically,
selecting the closest available drivers and controlling demand spikes.
Weather API: Demand Forecasting: The Weather API will help predict demand based on
weather conditions. For instance, during wet weather, ride demand usually increases. The
system will change the number of drivers assigned to high-demand places based on
weather estimates.
Payment Gateway API: The Payment Gateway API (e.g., Stripe or PayPal) will be linked
into the mobile app to allow secure payments for rides.
Payment Integration: Passengers can easily pay through the app using credit/debit cards
or digital wallets, providing a smooth and safe transaction process.
6. Developing the IoT Application Development Process:
Backend System: A cloud-based core system (using AWS IoT Core or Google Cloud
IoT) will handle real-time data processing. The server will also run machine learning
models to predict demand and improve ride matching.
Mobile Apps: Development of mobile apps for drivers and customers, combined with the
Google Maps API for guidance and payment gateway for transactions.
Dashboard for Operations: A real-time dashboard (built using ThingSpeak or Power BI)
will help track success, including fleet availability, ride request density, and driver state.
Conclusion: The IoT application created for PickMe will feature a three-layer architecture
that uses real-time GPS data, demand sensors, cloud computing, and machine learning to
dynamically assign rides. Hardware components such as smartphones and sensors,
combined with Google Maps API, Weather API, and payment methods, will allow
smooth integration of the IoT system into PickMe's current ride-hailing platform. The
application will continually improve based on user input and iterative development,
ensuring that it meets both business and customer needs effectively.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Employ an appropriate set of tools to develop a plan into an IoT application.

To build an IoT application for solving an organization's problem, an appropriate set of

tools must be applied for planning, development, and delivery. The tools can be split into
hardware tools, software tools, and development systems. Below is a detailed plan
outlining how to use these tools successfully to build an IoT application for an
organization like PickMe (which focuses on improving ride sharing and decreasing
customer wait times).

1. Hardware Tools
Hardware forms the real part of an IoT system, allowing it to receive, interact, and act on
data.

a. IoT Devices (Sensors and Actuators)

GPS Modules (for Real-Time Vehicle Tracking):

Purpose: These gadgets track the exact position of each car in real time. By using GPS
units like Neo-6M, the IoT system can track the vehicle's position and figure the best
possible path or closeness to a passenger.
How It Works: Every car in the PickMe service is equipped with a GPS gadget that sends
location data at regular times. This info is important for the backend system to figure ride
sharing and suggest best ways.
Demand Sensors (at Key Locations):

Purpose: These monitors track foot traffic or demand at specific places (like shops, bus
stops, etc.), helping PickMe understand high-demand areas.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

How It Works: devices such as infrared or sound devices identify the number of people
waiting at a place. These data points are sent to the cloud, telling the system of the real-
time demand so that drivers are given properly.
Smartphones/Tablets (Driver and Passenger Interfaces):

Purpose: Mobile apps put on smartphones or tablets allow passengers to request rides,
while drivers use them to journey and connect with the system.
How It Works: Smartphones receive data such as locations, user request, and ride choices.
They send this info via MQTT or REST APIs to the cloud to be processed and matched
with available drivers.
2. Software Tools
Software tools are important to process, analyze, and show the data received from IoT
devices, and to provide the contact layer (like mobile apps).

a. IoT Development Frameworks ThingSpeak:

Purpose: An IoT tool that allows easy collection, saving, and study of sensor data.
How It Works: ThingSpeak can receive real-time GPS data from cars and demand info
from location-based sensors. The tool is ideal for initial testing and fast development,
helping to view data like fleet spread and customer demand.
Node-RED:

Purpose: A flow-based creation tool for putting together gadgets, APIs, and online
services.
How It Works: Node-RED can handle tasks. For example, when a customer orders a ride,
Node-RED can start a number of steps to check for available drivers, assign the nearest
one, and send information back to the user.
b. Cloud Platforms
AWS IoT Core:

Purpose: Securely connects IoT devices to the cloud for processing and saving info. It
handles device control, data input, and offers safe data flow.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

How It Works: AWS IoT Core gets real-time info from devices (vehicle locations,
demand sensors) and saves it. This data is studied to make decisions, such as sending a
close car to a customer.
Microsoft Azure IoT Hub:

Purpose: Similar to AWS, but built for a wide range of devices. Azure IoT Hub also
works well with machine learning models for future research.
How It Works: Azure IoT Hub can handle vast amounts of real-time data from cars and
sensors. It helps handle the fleet and improve ride distribution by predicting areas of high
demand using machine learning.
c. Development Frameworks for Mobile App Android Studio (for Android apps):

Purpose: Development tool for making mobile apps on Android devices.

How It Works: Develop the PickMe driving app using Android Studio. The app will have
tools like ride request handling, GPS tracking, and touch with the central system.
Android’s location services API will allow accurate tracking and efficient routes.
React Native (for Cross-Platform App):

Purpose: A method for making cross-platform games with a single script.

How It Works: Using React Native, you can build a mobile game that runs on both
Android and iOS, cutting development time. The app will link with the backend to fetch
real-time ride sharing data and send requests from riders.
d. Database Management and APIs
MySQL/MongoDB (Databases):

Purpose: Databases keep user data (e.g., driver and customer information) and ride-
related data (e.g., location records, ride preferences).
How It Works: MongoDB or MySQL can keep data from both customers and drivers,
including ride information, driver availability, and real-time system state. It also helps
with tracking user choices for more personalized experiences.
GraphQL/REST APIs:

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Purpose: GraphQL and RESTful APIs allow touch between the mobile app and the
system, allowing real-time data requests and changes.
How It Works: RESTful APIs will allow the mobile app to request ride status or nearby
available cars, while GraphQL allows more efficient data getting by asking only the
necessary fields.
3. Development Platforms
These tools help in writing, controlling, and joining all components of the IoT system.

a. IDEs for Backend Development Visual Studio Code:

Purpose: A lightweight and fast code tool for writing server-side logic.
How It Works: Developers can use Visual Studio Code to write core code that mixes ride
allocation methods and links with the database.
Eclipse IDE:

Purpose: An IDE for Java-based games. It’s useful for Android development and mixing
Java-based services with IoT devices.
How It Works: Eclipse helps build Android apps that connect with cloud services and
handle GPS and ride data.
4. Machine Learning and Data Analysis
Machine learning methods are crucial to study past data and predict ride demand, which
helps in improving ride distribution.

a. TensorFlow/Scikit-learn TensorFlow:

Purpose: A tool for making machine learning models, especially deep learning models.
How It Works: TensorFlow can be used to build models that predict high-demand places
based on past data, weather, time of day, etc. This model helps send drivers to the places
where demand is expected to rise.
Scikit-learn:

Purpose: A machine learning package that helps with better methods for regression,
classification, and clustering.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

How It Works: Scikit-learn can be used to build demand forecast models using past data
like tourist demand at certain places. This info helps in better ride distribution.
5. Communication Tools
For an IoT application to work successfully, all devices must connect efficiently with
each other and with the cloud.

a. MQTT (Messaging Protocol)

Purpose: MQTT is an efficient system made for lightweight communication in IoT apps.
It is well-suited for cases where gadgets constantly send data.
How It Works: MQTT will be used to send real-time data from the GPS sensors, demand
sensors, and mobile apps to the server. It offers low-latency communication, allowing
faster decision-making in the ride allocation process.
6. Testing Tools Testing is important for ensuring the system works as designed and
scales to meet real-world demand.

a. JMeter/Android Emulator JMeter:

Purpose: Used for load and performance testing to ensure the system can handle a large
number of devices and people.
How It Works: JMeter will simulate multiple live users and sensing data to test the
scalability of the server and IoT systems.
Android Emulator:

Purpose: To test mobile apps before release on real devices.

How It Works: It models real-world scenarios and helps debug the mobile application for
ride requests, GPS features, and touch with backend APIs.
Conclusion
By employing this comprehensive set of tools, the PickMe IoT application will be able to
seamlessly integrate hardware (like GPS and demand sensors), software (IoT platforms,
mobile apps), machine learning models, and real-time communication protocols to
provide optimized ride allocation, reduce customer wait times, and improve overall
efficiency. The mix of cloud platforms, sensors, mobile development tools, and data

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

analysis methods will ensure that the application is sturdy, scalable, and offers a smooth
user experience.

Run end-user experiments and examine feedback

Running end-user experiments and examining comments are critical steps in the
development of an IoT application, as they help ensure that the system meets user needs,
is useful, and provides a smooth experience. This process involves creating experiments
to watch how real users interact with the system, collecting feedback, and analyzing the
results to make necessary changes.

Step 1: Planning End-User Experiments

Before running the tests, you should have a clear idea of what parts of the IoT application
you want to test. This could include things like:

Ease of Use: Is the program intuitive? Can users quickly request rides or track their
vehicles?
System Performance: Does the program react in real time? Is there any lag when updating
car locations or finding best routes?
Accuracy: Are the sensors giving correct location data? Does the system give the nearest
available driver to the user?
User Satisfaction: Do the guests and drivers find the functions useful? Does the program
meet their needs?
Types of Experiments:
Pilot Testing (Beta Testing):

Select a small group of users (e.g., PickMe drivers and customers) to test the application.
Users should connect with the system in real-life situations, such as asking rides, tracking
cars, and using the application’s other features.
Duration: Conduct the test for a set time, such as one week, to gather enough data.
Task-Oriented Testing:

Set specific jobs for users to perform, such as "Request a ride from location A to location
B," or "Check the real-time status of a vehicle."

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Observe how users finish these jobs and find pain points or bottlenecks.
Field Testing:

Take the program out of the lab and into the real world. In this case, PickMe drivers and
customers should use the app during normal business.
Monitor how well the system works under real-world conditions, such as changing
network connection or higher-than-usual demand for rides.
Step 2: Collecting User Feedback After the tests, it’s crucial to collect detailed feedback
from the users to understand their experience. Feedback can be gathered in several ways:

a. Surveys/Questionnaires: Questions to Ask:

On a scale of 1-10, how easy was it to request a ride using the app?
Were the GPS tracking and route selection accurate? How long did it take to find a close
driver?
How happy are you with the ride selection process? Did you feel that you waited too
long?
Were there any problems with app speed, such as lag or crashes?
Were you able to understand the directions and app features easily?
Did the program meet your needs in terms of ride distribution and wait time?
b. In-App Feedback: Include a choice for users to leave feedback straight within the app.
This could be a simple rating system (1-5 stars) with an opportunity for extra comments.
This helps you to get more quick and casual comments from users.
c. Direct Observations: Observe how people interact with the system in real-time. This
can be done either in-person or online using tools like screen recording software or user
experience study tools.
Focus on finding where users struggle or get annoyed with the app’s usefulness or design.
d. Interviews and Focus Groups: Conduct follow-up interviews or focus group
discussions to gain more detailed thoughts about their experience.
Ask users to describe specific issues or places they thought could be improved.
Step 3: Analyzing Feedback and Data
Once you have gathered the feedback, it’s time to examine the data to find similar themes
and problems.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

a. Categorizing Issues: Usability Issues: Are users finding it difficult to navigate the app
or perform certain tasks, such as booking a ride or following a vehicle? Common issues
could be unclear directions, confused UI elements, or speed problems.

Technical problems: Are there any system bugs or speed problems, such as crashes,
delays in ride allocation, or wrong GPS data? Check if the IoT devices are giving correct
data and if the system is processing it in real-time.

Feature Feedback: Are people asking extra features? For example, customers might want
the ability to see the expected wait time for a driver, or drivers may want real-time traffic
reports to optimize their routes.

b. Identifying Patterns: Look for patterns in the feedback:

If many users say that the app is hard to navigate, it may be a sign that the UI needs
change.
If multiple users report delays in ride allocation, it could signal that the system isn’t
properly handling data or sending drivers.
If there are issues with sensor accuracy, such as drivers being assigned to the wrong
place, further research into the sensors or their calibration may be necessary.
c. Performance Metrics:
For technical factors, check the performance data from the app:

Response Time: Measure how long it takes from when a ride request is made until a
driver is given. This can help spot delays in the system’s back-end processes.

Error Rates: Look at the error logs to spot any repeated problems or system failures.

User Retention and Engagement: Track how many people continue to use the app after
their first ride request. If many drop off, there may be usability or technical problems that
need to be handled.

Step 4: Making Iterative Improvements

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

After analyzing the data, it’s time to make changes based on the comments.

a. Usability Enhancements: UI/UX Improvements: If users have trouble managing the app
or finding certain features, make changes to the user interface to make it more simple. For
example, improve button placement, simplify screens, or add tooltips for guidance.

Task Flow Optimization: Simplify or ease the process of booking a ride. For example,
ensure that the ride request method has a minimal number of steps and is quick to
complete.

b. Technical Fixes:
Backend Optimization: If the ride allocation process is slow, improve the backend
algorithms to make ride assignments quicker.

Sensor Calibration: If GPS or demand sensors are inaccurate, fine-tune their configuration
or replace faulty hardware.

c. New Features:
New Requests: If users requested additional features, such as real-time traffic data for
drivers or an estimated wait time for passengers, these could be integrated into the next
iteration of the app.
d. Re-run the Experiments:
After implementing the changes, re-test the app with a new set of users (or the same
users) to verify whether the changes have improved the experience.

Step 5: Continuous Improvement

End-user experiments and feedback should be an ongoing process. As more users interact
with the IoT application, more data and insights will emerge, providing opportunities to
enhance the app over time.

Keep collecting feedback after each new update or release.

Regularly analyze the data and iterate on the design to continuously improve the user
experience.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Conclusion
Running end-user experiments and examining feedback is essential to refine the IoT
application and ensure it meets user expectations. By carefully planning the experiments,
collecting detailed feedback, analyzing the results, and iterating on the design, you will be
able to build a robust, user-friendly application that solves the organization’s problem
effectively. In the case of PickMe, this iterative process will lead to better ride allocation,
reduced wait times, and higher satisfaction among passengers and drivers.

Reconciling End-User Feedback and Evaluating IoT Techniques

When creating and refining an IoT application, user feedback plays a critical role in
finding both the strengths and flaws of the chosen techniques. By reconciling this input,
the development process becomes more user-centric, ensuring the application is useful,
efficient, and solves the organization's problem. Below is a thorough explanation,
combining benefits and disadvantages into a complete study.

Reconciling End-User Feedback

Feedback is categorized and examined to find key trends and useful insights. Each input
type directly affects the refinement of the IoT methods.

Categorizing Feedback
Feedback from end users can be split into:

Positive Feedback: Highlights features that are working well, such as fast real-time
tracking or a simple interface.
Negative Feedback: Pinpoints pain points, like delayed alerts or incorrect GPS data.
Suggestions for Improvement: Includes additional features or changes, like forecast fare
estimates or improved driver-rider contact.
Mapping Feedback to IoT Techniques

Real-Time Data Processing: User comments about slow ride allocation lead to improving
data methods for quicker processing.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

GPS and IoT Sensors: Reports of inaccurate locations are handled by recalibrating GPS
devices and testing in various settings.
API Integration: Issues like old traffic data require choosing more reliable third-party
APIs or building backup systems.
Prioritizing and Implementing Changes

Feedback is selected based on criticality:

High Priority: Issues like GPS errors or delayed ride distribution.
Medium Priority: UI/UX improvements, such as easy scrolling.
Low Priority: Aesthetic changes or extra functions.

IoT Technique Advantages Disadvantages

Cloud Computing - Scalability to handle increasing - Dependence on internet
user demand. connectivity.
- Reliable storage with backup and - Potential data security concerns
disaster recovery. requiring encryption measures.
- Global accessibility.
Real-Time Data Processing - Instant updates enhance user - High computational power
experience. requirements increase costs.
- Improves efficiency in ride- Synchronization challenges across
allocation and tracking. devices.
IoT Sensors (e.g., GPS) - Precise tracking for location and- Susceptible to inaccuracies in
speed. areas with poor signal.
- Enables valuable analytics for- Regular maintenance required for
service optimization. consistent accuracy.
API Integration - Simplifies development by using - Dependence on third-party
existing services (e.g., traffic data). providers’ reliability.
- Enhances features and- Limited customization for highly
functionality. specific requirements.
Mobile Platforms - Convenient for users via- Frequent updates needed for
smartphone apps. compatibility with various devices.
- Real-time notifications improve - Performance issues on older
engagement. hardware.

Addressing Disadvantages Through User Feedback

End-user feedback directly informs solutions for mitigating the drawbacks of each
technique:

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Cloud Computing Improvements:

Implement a multi-cloud approach to reduce dependency on a single service.

Use encryption and frequent checks to address security risks.
Real-Time Data Processing Enhancements:

Adopt edge computing to offload some work to local devices.

Optimize algorithms to reduce computing needs and delay.
IoT Sensor Reliability:

Use redundancy by combining multiple sensors to cross-check data correctness.

Test in various settings to reduce signal issues.
API Integration Resilience:

Create backup methods for offline functions (e.g., cached maps).

Partner with reputable companies to ensure API trustworthiness.
Mobile Platform Optimization:

Develop lightweight versions of the app for older smartphones.

Regularly test and adjust for energy savings and performance.
Conclusion: Balancing Strengths and Weaknesses
By adding user input into the development process, the IoT application becomes more
refined and user-focused. Balancing the benefits and drawbacks of IoT methods ensures a
sturdy and efficient solution. For PickMe, addressing real-time ride allocation problems,
ensuring reliable GPS tracking, and improving overall user experience shows the success
of this iterative method.

Iterative Development of the IoT Application

Iteration 1: Basic IoT Application Prototype

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Features Developed:

Real-time Ride Tracking: Basic GPS trackers were introduced to allow customers to track
their rides in real time.
Simple Ride Allocation Algorithm: Allocated rides based on the nearest available driver
without considering busy times or demand spikes.
Basic User Interface (UI): Focused on key functions like booking rides and watching ride
status.
User Feedback:

Slow Ride Allocation: During peak hours, users faced delays in getting rides.
Lack of Notifications: Users had no clear sign of ticket approval or driver arrival.
UI Issues: The interface wasn’t designed for smaller screens, leading to navigation
problems on compact devices.
Planned Enhancements for Iteration 2:

Improve the ride allocation system to handle high-demand cases more efficiently.
Introduce push alerts for ride progress updates and confirmations.
Redesign the user experience to improve usefulness on smaller screens.
Iteration 2: Enhanced IoT Application Features Enhanced:

Optimized Ride Allocation: Incorporated demand forecast to prioritize ride orders during
busy hours.
Push Notifications: Notifications for ride approvals and driver changes were added.
Responsive UI Design: Adjustments were made to ensure a smooth user experience on
both big and small computers.
User Feedback:

Inconsistent Notifications: Notifications didn’t work consistently on all devices,

especially older models.
GPS Issues: Drivers reported incorrect GPS locations, especially in urban places with
high-rise buildings.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Missing In-App Payments: Customers preferred the ease of paying within the app instead
of cash or external systems.
Planned Enhancements for Iteration 3:

Implement a more effective cloud message service to ensure consistent alerts.

Improve GPS tracking by adding complex correction techniques.
Add an in-app payment function with secure handling.
Iteration 3: Advanced IoT Application Features Enhanced:

Cloud Messaging Service: Notifications became uniform across all user devices,
regardless of age or OS version.
Advanced GPS Algorithms: Enhanced location precision by handling urban obstacles like
signal interference.
Secure In-App Payment: Integrated secure payment methods for smooth purchases.
User Feedback:

Request for Ride Rating System: Users wanted the ability to rate their rides and provide
comments.
Driver Suggestions for Route Optimization: Drivers stated the need for tools to reduce
journey distance and fuel usage.
Language Barriers: Some users asked support for various languages.
Planned Enhancements for Iteration 4:

Add a ride review system to improve service quality and responsibility.

Introduce real-time traffic data to improve driving routes.
Enable international support to make the app more available to different users.
Iteration 4: Final IoT Application Features Enhanced:

Ride Rating System: Allowed users to provide comments and rate drivers.
Route Optimization: Integrated live traffic changes to suggest the most efficient ways.
Multilingual Support: Offered language choices to suit people from different cultural
backgrounds.
User Feedback:

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Overall happiness with major features like ride allocation, GPS accuracy, and payment
choices.
Minor ideas for changing the app, such as allowing unique themes and color schemes.
Final Enhancements:

Added theme and color editing for individual personalization.

Conducted thorough stability and speed tests to ensure the application could handle
growth needs.

Summary of Enhancements Across Iterations

Iteration Major FeaturesKey User Feedback Modifications Made
Added/Enhanced
1 Basic ride tracking, rideDelays in ride allocation,Improved algorithms, added
allocation, simple UI. no notifications, difficultnotifications, redesigned UI.
navigation.
2 Optimized allocation, pushInconsistent notifications,Integrated cloud messaging,
notifications, responsive UI. GPS inaccuracy, no in-appadvanced GPS, added payments.
payments.
3 Reliable notifications, accurateNeed for ride ratings,Added rating system, traffic-
GPS, in-app payments. route optimization,based routing, language options.
multilingual support.
4 Ratings, route optimization,Suggestions for UIAdded themes, enhanced
multilingual support. customization. performance, finalized testing.
Each iteration refined the IoT application, directly addressing user concerns and
continuously improving functionality to create a robust, user-centric solution.

Activity 03
Review of the IoT Application: Problems Solved
The IoT application built for PickMe solves several key problems in the ride-hailing
industry, especially focused on improving the speed of ride scheduling, customer
happiness, business costs, and the overall user experience. Below is a better description of
each problem the IoT application solves:

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

1. Reducing Customer Wait Times Problem: One of the most common issues from ride-
hailing service users is long waiting times, especially during peak hours, busy traffic
conditions, or in rural areas. These delays occur when drivers are far away from the
customers, or when the system fails to properly allocate available cars to riders.

Solution: The IoT technology solves this problem by using real-time info on driver
positions and ride orders. Through the merging of GPS tracking and dynamic route
changes, the IoT application predicts demand and improves driver sharing accordingly.
This ensures that drivers are dispatched from close places to pick up people more quickly.
Additionally, the system uses past data and machine learning algorithms to predict
demand trends and constantly ensure that drivers are available in high-demand areas.

By adopting this prediction system, customer wait times are reduced, and riders are
matched with the nearest available drivers, making the entire ride-hailing experience
more efficient.

2. Enhancing Transparency Through Real-Time Tracking Problem: Riders often have no

understanding over where their driver is or how long they will have to wait for pickup.
This lack of openness can cause worry, anger, and distrust between the customer and
service provider.

Solution: The IoT program includes real-time GPS tracking, which allows customers to
watch their driver’s location throughout the trip. When a customer gets a ride, they can
see the driver’s live location on a map and receive real-time information on the driver’s
expected time of arrival (ETA). This openness not only helps customers plan their time
better but also builds trust between them and the service company.

The app also provides customers with tips of any delays or changes, such as traffic jams
or road closures, that may affect the driver's arrival time. As a result, customers feel more
in charge and educated, improving their total happiness.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

3. Optimizing Routes and Reducing trip Time Problem: Drivers often face traffic jams,
crashes, and other hurdles on the road that lead to longer journey times, higher fuel
consumption, and bad customer experiences. In busy urban areas, this problem can be
even more obvious, resulting in delays and waste.

Solution: The IoT application uses strong real-time traffic tracking and route planning
algorithms to help drivers choose the best routes based on live traffic data. The system
constantly reviews road conditions, finds traffic bottlenecks, and offers alternative routes,
lowering the chance of delays. By cutting trip time, the application ensures faster
deliveries and more efficient service, which leads to lower running costs for the company
and better service for customers.

Furthermore, this lowers fuel waste and improves the environmental effect of the service
by reducing needless drive time.

4. Streamlining Payment Systems for Security and Convenience Problem: Payment

security and the general user experience during the transaction process can be a pain point
for many users. Users sometimes have worries about the security of online payments or
experience problems with in-app payment handling during or after the ride.

Solution: The IoT application includes a safe, user-friendly payment system that allows
users to make payments directly from the app using various methods such as credit cards,
e-wallets, and even mobile money. It ensures that payment information are encrypted,
giving a high level of security. Additionally, the system offers the choice for automatic
price calculation based on real-time ride data, such as distance, road conditions, and ride
length. This ensures that payments are fair, open, and safe.

With the seamless merger of payment services, customers no longer need to think about
dealing cash, which improves the entire process, especially when they are in a hurry. The
app also saves payment information safely, allowing users to make quick payments for
future rides with minimal effort.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

5. Enhancing Driver and Customer Safety Problem: Safety problems are important for
both workers and customers. In some cases, drivers may face dangerous situations, or
riders may feel unsafe during rides. The lack of real-time monitoring of driver behavior
and car situations adds to these fears.

Solution: The IoT program uses a range of safety features, such as tracking driving
behavior and car health. The system uses sensors put in the car to track factors like speed,
stopping patterns, and acceleration. If any unsafe driving behavior is identified, the
system can warn the driver and, in severe situations, call the PickMe control center to
take action.

Additionally, IoT-enabled cameras and in-vehicle monitors provide safety by watching

the surroundings inside and around the car. The application also includes a feature that
allows riders to share their ride details, including driver information and location, with
family members or friends for extra peace of mind. These steps help improve safety for
both cars and guests.

6. Optimizing Fleet Management Problem: Managing a large fleet of vehicles efficiently

can be difficult, especially when it comes to organizing care, tracking vehicle
performance, and ensuring that vehicles are being used best.

Solution: The IoT system gives fleet managers with a real-time screen to watch the
performance and state of every car in the fleet. Sensors track data on fuel consumption,
car health, repair plans, and usage trends. This helps the fleet manager to plan repairs
ahead, reduce downtime, and ensure that the fleet is always in ideal working shape.

The program also helps ensure that cars are used properly by watching idle times and
improving their usage throughout the day. By making truck management more efficient,
PickMe can lower running costs and ensure a high-quality service for customers.

Conclusion: The IoT application built for PickMe solves several important problems
related to ride-hailing services. It greatly improves the user experience by reducing wait
times, improving openness, optimizing routes, protecting payment systems, and ensuring

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

safety. Additionally, the system helps the company improve fleet management, lower
running costs, and increase total performance. By fixing these problems, the application
not only helps the customers but also adds to the company’s growth and success in a
competitive market.

Potential Challenges and Solutions in Integrating an IoT Application into an

Organization's System.

When integrating an IoT application into an organization’s larger system, several possible
challenges and problems can arise. These difficulties may relate to both technical and
organizational aspects, and handling them is important to ensure easy merging,
usefulness, and long-term success. Here’s a study of the possible problems the IoT
application for PickMe might encounter:

1. Compatibility with Existing Infrastructure Problem: One of the main challenges in

adding an IoT application is ensuring compatibility with the organization’s existing
systems. PickMe may already have a set of software apps, databases, and platforms that
the IoT solution must work with. This can include fleet control tools, payment gateways,
driver/rider interfaces, and user databases.
Impact: If the IoT application isn’t compatible with the current infrastructure, it could
result in contact failures between systems, data inconsistencies, or even downtime.
Ensuring that the application communicates effectively with current systems is crucial to
keeping the smooth flow of processes.
Potential Solution: The IoT program needs to be made with connectivity in mind. This
could mean using open standards or APIs (Application Programming Interfaces) that
allow the system to connect quickly to other software systems. Thorough testing and a
phased execution method would also help to spot and solve integration problems before
full launch.
2. Data Privacy and Security Concerns
Problem: IoT systems create and collect huge amounts of data, and the integration of the
IoT application into PickMe’s system will likely involve private customer and driver
information, such as location data, payment details, and trip patterns. Ensuring the
security and privacy of this info is important.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Impact: A security breach could lead to the exposure of private information, resulting in
legal, financial, and social damage for the company. Similarly, the failure to comply to
data security rules (such as GDPR or local privacy laws) could result in regulatory
penalties.
Potential Solution: The IoT application should be built with strong encryption methods,
both for data in motion and at rest. Strong authentication methods should be applied for
user access to the system, and data privacy practices must meet with legal regulations.
Additionally, regular security audits and penetration testing should be performed to find
and prevent vulnerabilities.
3. Scalability Issues
Problem: The IoT application needs to be scalable to handle big amounts of data and a
growing number of devices. As PickMe grows and adds more drivers, cars, and users to
its platform, the system must be able to scale without compromising speed or user
experience.
Impact: If the system isn’t built to handle growth, it could lead to performance loss, such
as slower data processing or system crashes, especially during busy times. Over time, this
could harm the user experience and the company’s image.
Potential Solution: To handle scalability, the application should be built on cloud-based
architecture that allows for elastic growth. Distributed systems, load balancing, and
microservices design are all methods that can help the IoT application grow effectively to
meet rising demands.
4. Real-Time Data Processing and Latency
Problem: Real-time data processing is a critical requirement for many IoT applications,
especially in the case of ride-hailing services like PickMe, where reliable, real-time
information about location, traffic conditions, and driver availability is required.
However, integrating the IoT system with the bigger platform and ensuring it handles data
in real-time can be difficult.
Impact: If the application has latency or delays in processing data (e.g., updating the
driver’s location or predicting traffic patterns), it could lead to poor user experience, with
delayed ride alerts, incorrect ETAs, or even missed rides. This can frustrate customers
and reduce the general efficiency of the service.
Potential Solution:

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

To decrease latency, PickMe’s IoT application should use efficient data transfer methods
(such as MQTT or WebSockets) for real-time data. Edge computing (processing data
close to the source of data generation, such as in the car) can also help limit delays and
reduce the amount of data that needs to be sent to the cloud for processing.
5. IoT Device and Sensor Reliability Problem: IoT apps rely heavily on hardware
components, such as sensors, GPS devices, and tracking modules. If these devices fail to
work properly or misfire, the IoT system may not be able to gather accurate data, leading
to faulty decision-making or inefficient operations.
Impact: A malfunctioning sensor (e.g., GPS errors or car health tracking failure) could
lead to inaccurate driver locations, wrong ride allocation, and poor customer experiences.
It could also result in unnecessary car upkeep or higher operational costs.
Potential Solution: The dependability of the gear can be improved through the use of
high-quality, multiple, and fail-safe sensors. Regular upkeep, calibration of devices, and
online tracking of hardware performance are also necessary to identify and fix possible
issues before they impact the system.
6. System Downtime and Reliability Problem: As with any application, the IoT system
could face unexpected downtime or outages due to technical issues, such as server
breakdowns, database damage, or network disruptions.
Impact: If the IoT application experiences downtime, it could greatly disrupt activities.
For PickMe, this could result in missed ride requests, drivers being unable to access the
app, or customers being unable to book rides, which would directly affect the income and
customer trust.
Potential Solution: To avoid downtime, the system should be built for high availability
with redundancy, backup servers, and disaster recovery procedures. Cloud companies
often offer SLAs (Service Level Agreements) that ensure uptime and dependability, and
utilizing these can help reduce the effect of technology failures.
7. User Adoption and Training Problem: Employees and users (drivers and customers)
may face problems accepting and using the IoT application, especially if it needs new
tools or processes that they are unfamiliar with.
Impact: Resistance to change and a lack of training can lead to poor adoption rates,
inefficiency, and frustration for both workers and customers, which may lower the
usefulness of the IoT solution.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Potential Solution: Comprehensive training and hiring programs should be developed for
both drivers and workers. Additionally, the IoT application should have an intuitive and
user-friendly interface to reduce the learning curve and support smooth usage.
8. Data Overload and Analytics Complexity
Problem: IoT apps generate vast amounts of data, and if not treated properly, this data
could become overwhelming for the system and the users. Without effective data
analytics, the insights drawn from the IoT system could be useless.
Impact: Without proper data management, PickMe may struggle to make informed
choices based on the data created by IoT devices. Too much data could slow down the
system, and too little research could result in missed chances for optimization.
Potential Solution: The application should use data filtering methods to ensure that only
relevant and useful data is processed and examined. Machine learning algorithms can be
employed to automatically spot patterns in data, making it easier to draw useful insights
and improve decision-making.
Conclusion
The integration of the IoT application into PickMe’s wider system offers several possible
challenges, ranging from technical issues like system compatibility, data privacy, and
hardware stability, to operational challenges like user adoption and data overload. To
ensure a smooth integration, these challenges should be expected and handled during the
planning and development stages. This can be done through proper system design,
extensive testing, strong security measures, and continuous tracking to ensure easy
working and better user experiences for all parties involved.

Comparison of the Final IoT Application with the Original Plan

To compare the final IoT application with the original plan, you should focus on
evaluating the following key aspects,

1. Objectives and Goals

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Original Plan: The initial plan would have stated clear goals for what the IoT application
should achieve, such as fixing a specific problem, improving efficiency, or enhancing
user experience.
end Application: Compare whether these goals have been fully achieved in the end IoT
application. For example, if the goal was to automate tracking of devices or improve
operational efficiency, does the end application meet these needs?
2. Scope and Features
Original Plan: The scope of the project, including the features and tasks that were
planned, would have been clearly outlined. This could include specific functions such as
data collection, real-time tracking, user interfaces, or integration with other systems.
Final Application: Check if all the features stated in the original plan have been
successfully applied in the final output. Are there any functions that were deleted, added,
or modified? For example, if real-time data analytics was expected but not fully achieved,
you would talk this here.
3. IoT Architecture and Frameworks
Original Plan: The IoT design, frameworks, hardware, and APIs that were chosen in the
initial plan would have been carefully considered to meet the application’s needs.
finished Application: Compare the design and frameworks used in the finished
application to the original plan. Were the tools and frameworks chosen in the original
plan successful, or did they need to be changed to better meet the requirements during
development?
4. User Experience and Feedback Original Plan: The original plan likely included user
experience (UX) goals, such as ease of use, simple displays, or mobile accessibility.
finished Application: Evaluate the finished application’s user layout and user experience.
Has the finished product met the planned UX goals, or have there been changes based on
user feedback?
5. Technology and Tools Original Plan: The technologies, platforms, hardware, and APIs
picked during the planning phase would have been chosen for their fit for the project’s
needs.
end Application: Assess whether the technologies used in the end IoT application match
with the original plan. Were any new tools or methods adopted during development?
Were there any challenges or limits with the originally chosen technologies?
6. Timeline and Milestones

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Original Plan: The original plan would have included a timeline, with clear goals and
deadlines.
Final Application: Review the real schedule and whether the project stayed on track.
Were there any delays? If so, what caused them, and how were they addressed?
7. Scalability and Future Enhancements
Original Plan: The original plan might have included options for scalability and future
changes.
end Application: Determine if the end product is scalable and whether it allows for future
improvements as originally planned. Were any limitations found during development?
Conclusion
In conclusion, compare the goals and deliverables outlined in the original plan with the
real performance and features of the final application. This comparison helps to assess
whether the project has been successful in meeting the initial goals, find areas of
improvement, and note any deviations from the original plan.

Critical Evaluation of the Overall Success of the IoT Application

A critical review of the general success of an IoT application involves examining how
well the solution has met its intended goals, and the larger effect it has had on the people,
business, society, and the end users. Here's how you could approach this evaluation:

1. Success in Achieving Objectives

Problem-Solving Capability: The first step is to evaluate whether the IoT application
successfully solves the core problem described in the original plan. For example, if the
problem was improving energy usage in a building, does the program lower energy
consumption as expected? Has the program met performance standards such as speed,
security, and scalability?

Meeting Functional Goals: Assess whether the key tasks were performed as planned. For
instance, real-time data gathering, tracking, and alerts should be useful and realistic. Was
the IoT system able to achieve the desired performance (e.g., real-time tracking,
predictive repair, automatic control)?

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

User Experience (UX): Review the value of the app. Did it meet the planned user
interface design and experience goals? End-users should find the tool easy to navigate
and work with. Any trouble spots or customer issues should be examined and evaluated.

Technological Integration: Assess how well the IoT program interacts with current
systems, devices, or processes. Was there any need for change of the design or
technology stack during the development? Does the end result match with the initial
technology vision?

2. Impact on People Improvement in Daily Life or Work: If the IoT application was made
for customer use, examine its impact on the daily lives of people. For example, a smart
home system that handles household jobs can reduce energy usage and improve the ease
of routine tasks. For companies, the IoT application could have improved staff output,
safety, or business efficiency.

User happiness: Gather comments from users to rate their general happiness with the IoT
system. Are people happy, more efficient, or more powerful as a result of the system?
Was the tool simple enough to lessen the learning curve?

End-User Benefits: Consider the real-life benefits to the end-users. For example, if it’s a
smart healthcare answer, how has it changed the quality of life of patients? Has it
improved health effects, or raised exposure to healthcare?

3. Impact on Business Operational Efficiency: Did the IoT gadget help improve business
processes or operations? For instance, an IoT system that gives real-time info on goods or
plant health can lead to better decision-making and reduced delay. Evaluate the time, cost,
or resource savings the program brought to the business.

Cost Savings and ROI: Analyze if the IoT application has led to real cost savings, such as
dropped business costs, better asset management, or greater energy economy. The
business should see a return on investment (ROI) after the launch of the IoT system.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Business Growth and Competitiveness: Has the IoT solution made the business become
more competitive or open up new market opportunities? The usage of IoT can drive
innovation and provide businesses with data-driven insights that support growth. Evaluate
whether this application has improved the company's competitive edge in its field.

4. Impact on Society Social Benefits: Consider the bigger social impact of the IoT gadget.
For instance, a smart city system that handles traffic or public services could reduce
delays, improve public safety, and increase the quality of urban life. If the IoT system
includes sustainability efforts, such as energy-efficient lights or smart trash management,
rate its addition to environmental conservation.

Privacy and Security: While IoT devices provide numerous benefits, they also raise fears
about data privacy and security. A critical review would involve examining the system’s
security measures and how well user data is protected. Does the application meet with
important data security laws, such as GDPR? Did people trust the system with their data?

Social Impact and Accessibility: Consider whether the IoT application has made life
easier for disadvantaged groups or better general access to services (e.g., healthcare,
education, transportation). An inclusive IoT system ensures that it helps all members of
society, including those with disabilities or people in rural places.

5. End-User Feedback and Adaptation Feedback Mechanisms: How has the IoT
application applied end-user comments during its development? Were there big changes
or improvements made based on user input? For instance, did the system’s design change
based on feedback about ease of use or wanted functionality?

Iteration and Refinement: Evaluate the iteration process. Were the feedback methods
helpful in improving the product? Continuous improvement is a key part of an IoT
application’s long-term success. How well did the application grow through changes and
versions to match the changing needs of the users?

6. Potential Future Impact and Scalability

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Scalability: Can the application scale effectively to meet growing needs, whether that be
expanding to more people, handling additional devices, or extending to new geographic
areas? A critical review should study how well the system is positioned for future growth.

Innovation and Future Development: Does the program provide a base for future
advances or upgrades? For example, can additional sensors be added, or can the
application join with other technologies like AI, machine learning, or blockchain for
advanced data processing or security?

7. Final Conclusion
Overall Success: In conclusion, the success of an IoT application should be evaluated
based on how well it solves the intended problem, the amount to which it helps people,
companies, and society, and its potential for growth and change over time. The review
should also consider the feedback from end users, the ROI for the business, and the
application’s addition to social goals such as sustainability, safety, and better quality of
life.

By closely analyzing these aspects, you can determine if the IoT application was a hit or
find areas where it could be better.

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)

 lOMoARcPSD|42842578

Downloaded by Mohamed Muthaiyb (mohamedmuthaiyb8@gmail.com)