Internet of Things
This unit covers designing and developing IoT applications, including analysing requirements, planning using common architectures, implementing with hardware/software, and evaluating integration challenges.
Assessment criteria
Topic Overview
Cloud Computing is a paradigm that enables on-demand access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. In the Pearson BTEC Level 5 HND in Cloud Computing, this topic forms the foundation for understanding how modern IT infrastructure is delivered and managed. You will explore the essential characteristics of cloud computing—such as on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service—and learn how these attributes drive business agility and cost efficiency.
The module covers the three primary service models: Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS), along with deployment models including public, private, hybrid, and community clouds. You will also study key enabling technologies like virtualization, containerization (e.g., Docker, Kubernetes), and orchestration tools. Understanding these concepts is critical because cloud computing is now the default for IT delivery; organisations of all sizes rely on cloud services to scale operations, reduce capital expenditure, and accelerate innovation. This topic also sets the stage for more advanced units on cloud security, architecture, and DevOps.
Within the wider HND programme, this unit connects to modules on networking, operating systems, and database management. For example, you will apply knowledge of TCP/IP and DNS when configuring virtual networks in the cloud, and you will use Linux commands to manage cloud instances. By the end of this unit, you should be able to compare cloud providers (AWS, Azure, Google Cloud), evaluate migration strategies, and design a basic cloud solution that meets business requirements. This practical, vendor-neutral approach ensures you develop transferable skills valued by employers.
Key Concepts
Core ideas you must understand for this topic
- →Essential Characteristics: Understand the five essential characteristics defined by NIST—on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service—and how they differentiate cloud from traditional hosting.
- →Service Models: Know the differences between IaaS (virtual machines, storage, networks), PaaS (managed runtime environments like AWS Elastic Beanstalk), and SaaS (applications like Office 365). Be able to give examples and explain who manages what in each model.
- →Deployment Models: Distinguish between public (multi-tenant, e.g., AWS), private (single-tenant, on-premises or hosted), hybrid (combination with orchestration), and community (shared by several organisations with common concerns).
- →Virtualization and Containerization: Grasp how hypervisors (Type 1 vs Type 2) enable multiple VMs on one physical host, and how containers (e.g., Docker) share the host OS kernel for lighter-weight isolation. Understand orchestration tools like Kubernetes for managing container clusters.
- →Metering and Billing: Cloud services use a pay-as-you-go model. Understand how resource usage is metered (CPU hours, storage GB/month, data transfer) and how this affects cost management and budgeting.
Learning Objectives
What you need to know and understand
- 1. Analyse what aspects of IoT are necessary and appropriate when designing software applications.2. Outline a plan for an appropriate IoT application using common architecture, frameworks, tools, hardware and APIs.3. Develop an IoT application using any combination of hardware, software, data, platforms and services.4. Evaluate your IoT application and the problems it might encounter when integrating into the wider IoT ecosystem.
- 1. Analyse what aspects of IoT are necessary and appropriate when designing software applications.2. Outline a plan for an appropriate IoT application using common architecture, frameworks, tools, hardware and APIs.3. Develop an IoT application using any combination of hardware, software, data, platforms and services.4. Evaluate your IoT application and the problems it might encounter when integrating into the wider IoT ecosystem.
- 1. Analyse what aspects of IoT are necessary and appropriate when designing software applications.2. Outline a plan for an appropriate IoT application using common architecture, frameworks, tools, hardware and APIs.3. Develop an IoT application using any combination of hardware, software, data, platforms and services.4. Evaluate your IoT application and the problems it might encounter when integrating into the wider IoT ecosystem.
- 1. Analyse what aspects of IoT are necessary and appropriate when designing software applications.2. Outline a plan for an appropriate IoT application using common architecture, frameworks, tools, hardware and APIs.3. Develop an IoT application using any combination of hardware, software, data, platforms and services.4. Evaluate your IoT application and the problems it might encounter when integrating into the wider IoT ecosystem.
- 1. Analyse what aspects of IoT are necessary and appropriate when designing software applications.2. Outline a plan for an appropriate IoT application using common architecture, frameworks, tools, hardware and APIs.3. Develop an IoT application using any combination of hardware, software, data, platforms and services.4. Evaluate your IoT application and the problems it might encounter when integrating into the wider IoT ecosystem.
Assessment Criteria
Key criteria assessors look for in your portfolio
- Analyse which IoT aspects are necessary for a given application.
- Outline a plan using appropriate IoT architecture and tools.
- Develop a functional IoT application combining hardware and software.
- Evaluate the application and identify potential integration problems.
- Analyses appropriate IoT aspects for software applications.
- Outlines a plan using common architecture and tools.
- Develops an IoT application integrating hardware and software.
- Evaluates the application and potential integration issues.
- Considers security, scalability, and interoperability.
- Analyse the necessary aspects of IoT for a given application.
- Outline a plan using common IoT architecture and tools.
- Develop an IoT application integrating hardware and software.
- Evaluate the application and potential integration issues.
- Analyses the necessity and appropriateness of IoT for a given application.
- Outlines a plan for an IoT application using common architectures and tools.
- Develops a functional IoT application with hardware and software.
- Evaluates the application's performance and integration challenges.
- Considers security, scalability, and interoperability issues.
- Analyse appropriate IoT aspects for software application design.
- Outline a plan for an IoT application using common architecture and tools.
- Develop an IoT application integrating hardware, software, and services.
- Evaluate the IoT application and identify integration problems.
- Consider security and scalability in the IoT ecosystem.
Assessment Guidance
Guidance for achieving higher grades
- 💡Familiarise yourself with common IoT platforms and APIs.
- 💡Consider scalability and power consumption in design.
- 💡Document the evaluation with specific examples of issues.
- 💡Use standard IoT architectures (e.g., 3-layer).
- 💡Document your development process.
- 💡Consider real-world constraints.
- 💡Familiarise yourself with common IoT platforms (e.g., Arduino, Raspberry Pi).
- 💡Understand the importance of interoperability and standards.
- 💡Practise evaluating IoT solutions against requirements.
- 💡Start with a clear problem statement and requirements.
- 💡Prototype iteratively and test each component.
- 💡Document your design decisions and evaluation criteria.
- 💡Familiarise yourself with platforms like Arduino or Raspberry Pi.
- 💡Use diagrams to show system architecture.
- 💡Document your development process thoroughly.
- 💡When comparing service models, always use the 'shared responsibility' matrix. For IaaS, you manage the OS, middleware, and apps; for PaaS, you manage only apps and data; for SaaS, you manage nothing but usage. Examiners look for this precise understanding.
- 💡In exam questions about deployment models, mention real-world use cases. For example, a bank might use a private cloud for sensitive data and a public cloud for customer-facing apps, connected via a hybrid model. This shows you can apply concepts to scenarios.
- 💡For calculation questions on elasticity or cost, always show your working. If asked to estimate monthly cost for a VM, include assumptions (e.g., 730 hours/month, $0.10/hour) and break down compute, storage, and data transfer separately. Marks are awarded for method, not just final answer.
Common Mistakes
Common errors to avoid in your coursework
- Overlooking security and data privacy considerations.
- Choosing inappropriate hardware or protocols for the use case.
- Insufficient testing of interoperability with other IoT systems.
- Focusing only on hardware without software design.
- Ignoring security and data privacy concerns.
- Failing to test or evaluate the application.
- Choosing inappropriate hardware or protocols for the application.
- Neglecting security and data privacy in IoT design.
- Failing to test the application in real-world conditions.
- Overlooking security and privacy concerns.
- Choosing inappropriate hardware or protocols.
- Failing to test the application in real-world conditions.
- Choosing inappropriate hardware or protocols.
- Neglecting security considerations.
- Failing to test the application in a realistic environment.
- Misconception: 'Cloud computing is just someone else's computer.' Correction: While cloud does involve remote servers, it's a comprehensive model with defined service levels, elasticity, and measured service. It's not simply renting a server; it's a paradigm shift in how IT is consumed and delivered.
- Misconception: 'Public cloud is always cheaper than on-premises.' Correction: Cost depends on workload patterns. For predictable, always-on workloads, reserved instances or on-premises may be cheaper. Cloud is cost-effective for variable or spiky workloads due to its pay-as-you-go model.
- Misconception: 'Cloud is inherently insecure.' Correction: Security is a shared responsibility. Cloud providers invest heavily in physical and infrastructure security, but customers must configure their own security groups, IAM policies, and encryption. Misconfigurations are the main cause of breaches, not the cloud itself.
Frequently Asked Questions
Common questions students ask about this topic
Pass / Merit / Distinction Evidence Checklist
How your portfolio evidence is graded for PEARSON Internet of Things
Demonstrate baseline knowledge, accurate terminology, and core practical application.
Provide detailed analysis, structured explanations, and clear workplace reasoning.
Deliver thorough evaluation, original problem solving, and fully justified recommendations.
Before You Start
Prior knowledge that will help with this topic
- •Basic understanding of computer hardware (CPU, RAM, storage) and networking (IP addresses, DNS, HTTP/HTTPS).
- •Familiarity with operating systems (Windows Server, Linux) and command-line interfaces (e.g., SSH, bash).
- •Foundational knowledge of virtualization concepts (e.g., VMware, Hyper-V) from previous units or experience.
Coursework AI Review
Self-check your coursework evidence against P/M/D criteria
Key Terminology
Essential terms to know
- 1. Analyse what aspects of IoT are necessary and appropriate when designing software applications.2. Outline a plan for an appropriate IoT application using common architecture, frameworks, tools, hardware and APIs.3. Develop an IoT application using any combination of hardware, software, data, platforms and services.4. Evaluate your IoT application and the problems it might encounter when integrating into the wider IoT ecosystem.
- 1. Analyse what aspects of IoT are necessary and appropriate when designing software applications.2. Outline a plan for an appropriate IoT application using common architecture, frameworks, tools, hardware and APIs.3. Develop an IoT application using any combination of hardware, software, data, platforms and services.4. Evaluate your IoT application and the problems it might encounter when integrating into the wider IoT ecosystem.
- 1. Analyse what aspects of IoT are necessary and appropriate when designing software applications.2. Outline a plan for an appropriate IoT application using common architecture, frameworks, tools, hardware and APIs.3. Develop an IoT application using any combination of hardware, software, data, platforms and services.4. Evaluate your IoT application and the problems it might encounter when integrating into the wider IoT ecosystem.
- 1. Analyse what aspects of IoT are necessary and appropriate when designing software applications.2. Outline a plan for an appropriate IoT application using common architecture, frameworks, tools, hardware and APIs.3. Develop an IoT application using any combination of hardware, software, data, platforms and services.4. Evaluate your IoT application and the problems it might encounter when integrating into the wider IoT ecosystem.
- 1. Analyse what aspects of IoT are necessary and appropriate when designing software applications.2. Outline a plan for an appropriate IoT application using common architecture, frameworks, tools, hardware and APIs.3. Develop an IoT application using any combination of hardware, software, data, platforms and services.4. Evaluate your IoT application and the problems it might encounter when integrating into the wider IoT ecosystem.
Ready to learn?
AI-powered learning tailored to this unit