Study guide
15.3 Embedded Systems, the Internet of Things, and Types of Computing Systems
Praxis Computer Science 5652
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Praxis 5652 Exam Overview and ETS Pseudocode
1.1 Praxis 5652 Test Facts, Scoring, and Registration 1.2 Official ETS Pseudocode Notation and Tracing Strategy
2 Chapter 2: Impacts of Computing: Innovation, Access, and Effects
2.1 Computing for Creativity, Problem Solving, Communication, and Innovation 2.2 Equal Access, the Digital Divide, and Accessibility 2.3 Beneficial and Harmful Effects of Computing Innovations
3 Chapter 3: Impacts of Computing: Intellectual Property, Ethics, Privacy, and Security
3.1 Intellectual Property: Copyright, Open Source, and Creative Commons 3.2 Ethical and Unethical Computing Practices and Their Implications 3.3 Privacy, Security, Data Collection, and Local vs. Cloud Storage
4 Chapter 4: Algorithms and Computational Thinking: Abstraction, Decomposition, Number Bases, and Representation
4.1 Abstraction and Abstraction Hierarchies 4.2 Decomposition, Pattern Recognition, and Developing Algorithms 4.3 Number Bases: Binary, Octal, Decimal, and Hexadecimal 4.4 Algorithm Formats: Natural Language, Flowcharts, Pseudocode, and Tracing
5 Chapter 5: Algorithms: Efficiency, Limits of Computing, and Randomization
5.1 Algorithm Efficiency: Linear, Quadratic, Exponential, and Logarithmic Growth 5.2 Limits of Computing: Unsolvable Problems, Intractability, and Heuristics 5.3 Randomization, Random vs. Pseudorandom Numbers, and Scaling to a Range
6 Chapter 6: Algorithms: Searching, Sorting, and Recursion
6.1 Searching Algorithms: Linear Search and Binary Search 6.2 Sorting Algorithms: Tracing, Comparisons, Correctness, and Efficiency 6.3 Recursion: Base Cases, Tracing, Errors, and Iterative Equivalents
7 Chapter 7: Programming: Variables, Data Types, Strings, and Expressions
7.1 Variables, Data Types, and Type Conversion 7.2 Strings and String Operations 7.3 Operators, Precedence, Expressions, and Formulas 7.4 Boolean Expressions, Truth Tables, and Boolean Algebra
8 Chapter 8: Programming: Selection, Iteration, and Writing Code
8.1 Sequence and Selection: if, else, Chained and Nested Conditions 8.2 Iteration: for, while, do … while, and repeat … until Loops 8.3 Reading, Completing, and Modifying Code
9 Chapter 9: Programming: Procedures, Arrays, and Data Structures
9.1 Procedures, Parameters, Return Values, Nested Calls, and Scope 9.2 Arrays, Lists, and Two-Dimensional Arrays 9.3 Stacks, Queues, and Dictionaries (Maps)
10 Chapter 10: Programming: Correctness, Errors, Testing, and Code Quality
10.1 Program Correctness: Preconditions, Postconditions, Invariants, and Testing vs. Proof 10.2 Error Types and Debugging Techniques 10.3 Choosing Useful Test Cases: Boundaries, Partitions, Coverage, and Regression 10.4 Extensibility, Modifiability, and Reusability: Constants and Parameterization 10.5 Documentation, Code Reviews, Peer Feedback, and End-User Feedback
11 Chapter 11: Programming: Events, Usability, Input Validation, and APIs
11.1 Event-Driven Programming, Asynchronous Events, and Concurrency 11.2 Usability, Meaningful Error Messages, and Input Validation vs. Verification 11.3 Libraries and APIs: Reading Definitions, Making Calls, and Weighing Trade-offs
12 Chapter 12: Programming: Languages, Tools, Paradigms, and Object-Oriented Design
12.1 Low- and High-Level Languages, Compilers and Interpreters, and IDEs 12.2 Programming Paradigms: Procedural, Object-Oriented, and Others 12.3 Classes, Objects, Instance Variables, Methods, and Encapsulation 12.4 Inheritance, Polymorphism, and Overloading vs. Overriding
13 Chapter 13: Data: Bits, Encoding, Compression, and Encryption
13.1 Bits and Bytes: Why Binary, Storage Calculations, and Signed Integers 13.2 Encoding Text, Images, and Sound 13.3 Lossless and Lossy Compression: Run-Length Encoding, Huffman Coding, and Media Formats 13.4 Encoding vs. Encryption, Symmetric and Public-Key Encryption, and Their Trade-offs
14 Chapter 14: Data: Analysis Tools, Simulation, Storage, and Collection
14.1 Analyzing Data with Spreadsheets: Cleaning, Transforming, and Visualizing 14.2 Simulation and Modeling 14.3 Files, Databases, and Storage Requirements: Scale, Redundancy, and Backup 14.4 Collecting, Aggregating, and Generating Data: Public Data Sets, Surveys, Sensors, and Crowdsourcing
15 Chapter 15: Computing Systems: Hardware, Operating Systems, and Computing Environments
15.1 Hardware Components and the Fetch–Decode–Execute Cycle 15.2 Operating Systems, Software Components, and Resource Issues 15.3 Embedded Systems, the Internet of Things, and Types of Computing Systems 15.4 Local, Network, and Cloud Computing and Storage; How Binary Data Are Stored
16 Chapter 16: Networks, the Internet, the Web, and Cybersecurity
16.1 Network Types and Wired and Wireless Communication 16.2 Network Hardware and Layered Network Models (OSI and TCP/IP) 16.3 Network Performance: Bandwidth, Latency, Load, and Estimating Needs 16.4 How the Internet Works: Protocols, IP Addressing, DNS, URLs, and Reliability 16.5 The Web: HTTP, HTML and Markup Languages, Browsers, Servers, and Clients 16.6 Cybersecurity: The Five Pillars, Strong Passwords, Security Strategies, and Trade-offs
15.3 Embedded Systems, the Internet of Things, and Types of Computing Systems
Key Takeaways Explain This Topic AI
An embedded system is a computer built into a larger device to perform a dedicated function, often with limited resources and real-time requirements, as in ATMs, pacemakers, car braking systems, and microwave ovens.
The Internet of Things (IoT) is the network of everyday physical objects with sensors, processors, and Internet connectivity that collect and exchange data, such as smart thermostats and connected refrigerators.
Embedded systems use sensors to measure the environment, process the readings, and drive actuators in a sense–process–act loop.
A cluster is a group of networked computers that work together as one system for high performance or high availability.
Compare computing systems on processing power, memory and storage, portability, battery life, cost, energy use, reliability, scalability, and connectivity, relative to the task.
Last updated: September 2026
What this competency asks
Two ETS competencies are covered here:
Be familiar with computing systems embedded in everyday objects (for example, IoT, ATMs, and medical devices): describe what an embedded system is, define what the IoT is and how it is used, and describe how sensors are used in embedded systems.
Know the capabilities, features, and uses of different types of computing systems (for example, desktop, mobile, and cluster): identify them for each type, and identify criteria to evaluate and compare computing systems.
ETS's sample question asks which scenario is an IoT example. The answer is a refrigerator that orders milk from an online service when supplies run low. A car's collision warning, a GPS watch, and a heart-rate watch are embedded computing, but they do not need the Internet to work.
Embedded systems
An embedded system is a computer that is part of a larger device and is dedicated to specific functions.
- Characteristic Explanation
- Dedicated purpose Runs one program, or a few, for the device's job
- Microcontroller A small chip combining CPU, memory, and input/output on one chip
- Limited resources Little memory, low power use, low cost
- Real-time Often must respond within strict time limits, as with airbags and anti-lock brakes
- Reliability Must run unattended for years; failures can be dangerous
- Little or no conventional interface Buttons, a small display, or none at all
Examples: ATMs, pacemakers and insulin pumps, car engine controllers, anti-lock brakes, airbag systems, microwave ovens, washing machines, digital cameras, traffic signals, and elevator controllers. There are far more embedded computers in the world than desktop and laptop computers combined.
Sensors in embedded systems
Embedded systems interact with the physical world through a sense → process → act loop:
Sensors measure a physical quantity such as temperature, light, motion, pressure, sound, or location. An analog-to-digital converter turns the measurement into a number.
The processor compares the reading with thresholds or runs a control algorithm.
Actuators act: motors, heaters, valves, alarms, displays.
The loop repeats, often many times per second. This is feedback control .
Example: a thermostat. Read the temperature every few seconds. If it is below the set point, turn the heat on. If it is above the set point plus a small margin, turn the heat off. The margin prevents rapid on-off switching.
Design issues include sampling rate (how often to read), sensor noise and calibration , power consumption (reading less often saves battery), and safety when a sensor fails.
The Internet of Things
The Internet of Things extends embedded systems with network connectivity , so everyday objects collect data, communicate over the Internet, and can be monitored or controlled remotely.
- Area IoT example
- Home Smart thermostats, doorbells with cameras, voice assistants, connected appliances
- Health Remote patient monitoring, connected glucose monitors
- Agriculture Soil-moisture sensors that trigger irrigation
- Cities Smart parking, adaptive traffic signals, connected streetlights
- Industry Machines that report their condition before they fail (predictive maintenance)
- Schools Energy management, occupancy sensors, asset tracking
Benefits: automation, remote control, data for better decisions, energy savings, convenience.
Concerns:
Security: many devices ship with weak default passwords and are rarely updated. In 2016 the Mirai botnet took over large numbers of IoT devices, such as cameras and video recorders, and used them in massive denial-of-service attacks (Section 16.6).
Privacy: cameras, microphones, and location sensors collect sensitive data continuously (Section 3.3).
Dependence: a device may stop working when its manufacturer's cloud service shuts down.
Interoperability among brands, and the energy and waste of many small devices.
Types of computing systems
- System Capabilities and features Typical uses
- Desktop Powerful CPU and GPU; large screen; expandable; plugged in Programming, design, labs, gaming
- Laptop Desktop-class software; portable; battery powered Students and teachers on the move
Mobile (smartphone, tablet) Very portable; touch; cameras and sensors (GPS, accelerometer); cellular; limited input for heavy work Communication, field data collection, apps
- Wearable Tiny; body sensors; long battery life Fitness and health monitoring
- Server Reliable, always on, many users; often "headless" (no monitor) Websites, email, databases, file storage
Cluster Many networked computers acting as one; scales out; tolerates failure of individual machines Web services with heavy traffic; scientific computing; big data
- Supercomputer Enormous parallel computing power Climate modeling, physics, drug discovery
- Mainframe Extremely reliable; massive transaction volume Banks, airlines, government records
- Embedded Dedicated, low-power, often real-time Appliances, vehicles, medical devices
A cluster divides work among its nodes (parallel computing) and keeps running if one node fails (high availability). Cloud providers run huge clusters in data centers (Section 15.4).
Criteria for evaluating and comparing systems
Criterion Questions to ask
Processing power Number of cores, clock speed, GPU: enough for the workload?
Memory and storage Enough RAM for the software; enough storage, and how fast?
Portability and size Must it be carried into the field or classroom?
- Battery life and energy use Unplugged use; operating cost; heat
- Cost Purchase price plus software, maintenance, and support
Reliability and availability What happens if it fails? Is redundancy needed?
Scalability Can it grow with more users or data?
Connectivity Wi-Fi, cellular, wired; which ports?
Input and output Keyboard for coding? Touch? Sensors? Screen size?
Security and manageability Can it be updated, locked down, and managed centrally?
Software compatibility Does it run the required applications?
The best system depends on the task. A cluster is wasted on word processing, and a phone is a poor choice for compiling a large project. The best answer usually matches the system's strengths to the stated requirements.