Internet of Things Syllabus

The syllabus varies with the parent branch. A credible programme connects core engineering subjects with device-to-application integration.

Engineering Mathematics

Calculus, differential equations, matrices, probability, statistics, numerical methods and discrete Mathematics support signals, communication, algorithms and data analysis. Students should connect formulas with measurements and code.

Programming fundamentals

C teaches memory, data types, control structures, functions, pointers and bit operations useful in embedded work. Python, Java or another language may support applications, testing and data processing. Students need debugging ability rather than memorised syntax.

Data structures and algorithms

Arrays, lists, stacks, queues, trees, graphs, hashing, sorting and searching support efficient software. Complexity matters because devices may have limited processing power and memory.

Digital electronics

Students learn number systems, Boolean logic, combinational and sequential circuits, registers, counters and data conversion. These concepts explain how controllers interact with digital signals and peripherals.

Analog electronics and sensor interfaces

Basic circuits, operational amplifiers, filters, noise and analog-to-digital conversion help students handle real sensors. Poor grounding, supply instability or incorrect voltage levels can make a software-correct design fail.

Microprocessors and microcontrollers

Courses cover processor architecture, memory, interrupts, timers, serial interfaces and peripheral programming. Laboratories use development boards to read sensors and control outputs.

Embedded systems

Embedded design connects hardware and software under constraints. Students study firmware structure, device drivers, timing, power, debugging and reliability. Advanced courses may cover real-time operating systems.

Sensors and actuators

Students examine temperature, humidity, pressure, proximity, motion, light, gas, inertial and other sensors. They learn range, resolution, accuracy, calibration, drift and environmental limitations. Actuators include motors, relays, valves and displays.

Computer networks

Networking covers layers, addressing, routing, transport protocols, switching and network troubleshooting. IoT students should understand packet flow and failure rather than treating connectivity as a library command.

Wireless communication

Students learn propagation, modulation basics, link budget, interference and wireless standards. Practical study may include Wi-Fi, Bluetooth Low Energy, Zigbee, cellular IoT, RFID, NFC and low-power wide-area technologies.

Technology selection depends on range, data rate, energy, coverage, cost, topology and regulation. No wireless option is best for every application.

IoT architecture

Architecture courses examine devices, gateways, messaging, platforms, applications and management. Students compare centralised, edge and hybrid processing and learn how requirements shape design.

IoT protocols

Application and messaging protocols may include MQTT, CoAP, HTTP and related methods. Students study publish-subscribe and request-response patterns, quality of service, session behaviour and payload design.

Operating systems and real-time systems

Operating-system foundations cover processes, scheduling, memory, files and concurrency. Real-time topics address deadlines, task priorities, interrupts and predictable behaviour. Timing errors can be more serious than slow response in physical systems.

Database management

Devices generate time-stamped information that must be stored and queried. Students learn relational databases, SQL, time-series storage, indexing, retention and data quality. Collection should be limited to what the application genuinely needs.

Cloud computing

Cloud subjects cover compute, storage, messaging, serverless functions, APIs, scaling and monitoring. Students should understand cost, availability, vendor dependence, privacy and network failure.

Edge and fog computing

Edge processing occurs near the device to reduce latency, bandwidth or privacy exposure. Gateways may filter readings, run models or continue limited operation during cloud disconnection. Deployment needs update and recovery plans.

Cybersecurity

IoT security covers device identity, authentication, access control, encryption, secure boot, key management, firmware updates, network segmentation and logging. Default passwords and exposed services create serious risk.

Security must cover the complete lifecycle from manufacture and installation to maintenance and retirement. A device without a supported update path can become unsafe long before its hardware fails.

Data analytics and machine learning

Students learn data preparation, visualisation, anomaly detection and predictive models for sensor data. Evaluation must account for missing readings, drift, imbalance and changing operating conditions.

Signal processing

Sampling, filtering, frequency analysis and feature extraction help interpret vibration, sound, biomedical or motion signals. Students should understand aliasing and noise before applying a machine-learning model.

Control systems

Feedback, stability and controller design are relevant when IoT systems influence physical processes. Remote monitoring does not automatically justify remote control. Safe limits and local fallback are important.

Web and mobile applications

Applications display device state, alerts and trends. Students may learn APIs, dashboards and mobile interfaces. Interfaces should make uncertainty and stale data visible rather than creating false confidence.

Power management

Battery-powered devices need sleep modes, efficient communication, energy measurement and realistic lifetime estimates. Energy harvesting may help in suitable environments but does not remove the need for careful design.

PCB and hardware design

Advanced programmes introduce schematics, printed circuit boards, component selection, electromagnetic considerations, testing and manufacturing. Students should follow electrical safety and laboratory procedures.

Industrial IoT

Industrial courses cover operational technology, field devices, industrial communication, gateways, supervisory systems, predictive maintenance and safety. Students learn that production networks have different availability and change-control requirements from consumer applications.

Standards, ethics and privacy

Students examine interoperability, spectrum use, consent, surveillance, data ownership and environmental impact. Connected cameras, microphones, location devices and workplace sensors require special care.

Protocol and connectivity selection

Protocol choice begins with requirements rather than popularity. Engineers estimate distance, obstacles, message size, reporting interval, latency, power source, number of devices, mobility and expected service life. They also consider whether an operator network, private gateway or existing local network is available.

Wi-Fi can carry comparatively large amounts of data but may consume more energy and depends on local access. Bluetooth Low Energy is useful for short-range, low-power interaction. Mesh technologies can support groups of nearby devices, while low-power wide-area approaches serve smaller messages over longer distances. Cellular options can simplify wide-area coverage but introduce subscription, module and certification costs.

Engineers must check legal frequency bands, transmit-power limits and product certification before deployment. A radio module functioning in a student prototype does not by itself make the final product compliant. Antenna placement, enclosure material and nearby metal can change performance considerably.

Device lifecycle management

Connected products require management after installation. Each device needs a unique identity, configuration record, firmware version, ownership status and maintenance history. Teams need safe processes for onboarding, credential rotation, updates, fault reporting and retirement.

Over-the-air updates reduce site visits but create risk if power or communication fails. A dependable design validates the update, protects the previous working version and supports rollback. Critical changes should be staged on a test group before deployment across a fleet.

Retirement is also a security activity. Credentials and personal data should be removed, cloud access revoked and electronic hardware recycled appropriately. A product plan that ends at sale is incomplete.

Reliability and environmental testing

IoT devices may face heat, moisture, dust, vibration, electrical noise and unstable power. Testing should reproduce likely conditions within safe laboratory limits. Engineers examine startup after power failure, clock error, memory exhaustion, sensor disconnection, gateway loss and corrupted messages.

Long-duration testing can reveal leaks, overheating, battery drain and communication problems that a short demonstration misses. Teams should record failure rate and recovery time and distinguish temporary data loss from unsafe loss of control.

Interoperability and data models

Two devices using the same transport protocol may still describe information differently. Teams need consistent units, timestamps, identifiers, schemas and error values. A temperature value without its unit, sensor location, time and quality status can be misleading.

Open interfaces can reduce dependence on one vendor, but they require disciplined documentation and version management. When a data format changes, older devices and applications may need compatibility support. Interoperability testing should be part of acceptance rather than an assumption.

Software engineering and DevOps

Requirements, version control, testing, configuration, deployment and monitoring support reliable systems. Device fleets need controlled firmware releases, inventory and rollback. IoT operations extend beyond deploying a web application.

Typical semester pattern

Laboratories

Important laboratories include programming, electronics, microcontrollers, sensor interfacing, networks, embedded systems, wireless communication, cloud integration and security. A lab should require students to measure, test and troubleshoot.

Project ideas

• soil and weather monitoring with responsible irrigation advice;
• energy meter with secure local and remote dashboard;
• authorised machine-condition monitor using vibration;
• cold-chain monitoring with offline data recovery;
• accessible room-control interface;
• indoor air-quality monitor with calibrated sensors;
• water-tank monitoring with safe manual override;
• campus asset tracker with privacy controls;
• edge-based fault detector;
• secure smart-lock prototype with threat analysis;
• solar-system performance monitor;
• laboratory equipment utilisation system.

Projects should state requirements, architecture, threat model, calibration, communication failure behaviour, power estimate, testing and limitations. Students should never connect an experimental device to critical infrastructure without permission and qualified supervision.