Applications & Use Cases · Study deck
IoT Requirements: Classification and Connectivity
Write the promise from the resident's point of view.
Blueprint Bina is your guide for this deck.
After studying this chapter
Learning objectives
You will be able to:
- Explain IoT architecture: Describe the complete data flow through the five IoT system layers from sensor to application
- Apply minimum requirements: Identify and verify the three essential components every IoT device must have using the Three Ingredients Test
- Evaluate IoT characteristics: Assess IoT systems against eleven ideal characteristics and assign priority weights by domain
- Select appropriate technologies: Compare connectivity options (Wi-Fi, LoRaWAN, cellular) and justify choices based on application requirements
Major section
Start With the Story
The idea sounds useful, but the owner still needs to know what is sensed, who gets the warning, how soon it arrives, and what happens when power or the link fails.
- A distant service may store, compare, and notify, but it must not be the only path to immediate protection.
- Practitioner turns the promise into acceptance tests.
Major section
Quick Mental Model
A farm sensor optimized for millisecond response while ignoring battery life is solving the wrong problem.
- Timer microwave: Thing + computation, but no internet reach ->: Embedded device.
- Bluetooth lock: Thing + computation + local wireless, but no internet reach ->: Connected product.
Major section
Minimum Viable Understanding
If any one is missing, the device is not IoT -- it may be embedded (no connectivity) or connected (no internet reach), but not IoT.
- Eleven characteristics separate good from great: Ubiquitous, Smart, Agile, On Demand, Blend into Background, Secure, Low Maintenance, Fast, Upgradable, Growing, and Adaptable are quality benchmarks.
Major section
Make Classification Testable
The Three Ingredients Test is a requirement filter, not a vocabulary exercise.
- A product qualifies as IoT only when the physical thing, local computation, and internet reach work together to support a useful data or control loop.
- A LoRaWAN soil sensor may qualify through a gateway even though the sensor itself never opens a TCP connection.
Major section
Make Classification Testable (continued)
The requirement is the service path, not a specific radio.
- The test forces you to name the asset, the embedded logic, and the path that carries telemetry, commands, alerts, configuration, or updates beyond the local environment.
- Classification is only the first pass.
- The second pass asks whether the device is good IoT for its job.
Major section
Make Classification Testable (continued)
A qualifying service path combines a physical thing, local computation, and direct or gateway-mediated internet reach; removing any one ingredient changes what the product can observe, decide, or control remotely.
- A Bluetooth-only lock may be connected, but it is not the same requirement set as a lock that reaches a cloud service through a Wi-Fi bridge or integrated Wi-Fi radio.
- A factory vibration sensor may reach a historian through an edge gateway and still count as IoT if the end-to-end path supports remote visibility or action.
- A thermostat may prioritize local control, comfort, update safety, and household privacy.
Major section
Make Classification Testable (continued)
This framing prevents technology-first design.
- A smart thermostat, cold-chain tracker, irrigation valve, medication dispenser, and fleet sensor all satisfy the three ingredients, but their strongest characteristics differ.
- A cold-chain tracker may prioritize battery life, location coverage, tamper evidence, and data retention.
- A fleet sensor may prioritize mobility, cellular roaming, ruggedness, and remote diagnostics.
Major section
Make Requirements Measurable
The words are only useful when they become testable acceptance criteria.
- Wi-Fi fits mains-powered devices with local bandwidth and installation support.
- Thread or Zigbee may fit home and building meshes where a border router is acceptable.
- BLE can work for phone-assisted setup, short-range sensing, or local wearables.
Major section
Make Requirements Measurable (continued)
LoRaWAN fits small, infrequent telemetry over long range when downlink limits are acceptable.
- LTE-M or NB-IoT may fit wide-area assets when gateway ownership is impractical and the business model can carry subscription cost.
- A smart-home lock might require local unlock when the cloud is down, revocation within minutes, low-battery warning before failure, and a clear household recovery path.
- These statements are design inputs, not after-the-fact documentation.
Major section
Requirements Cross the Five Layers
A freshness requirement may need a sensor timestamp, device clock behavior, gateway buffering rule, MQTT or HTTPS message policy, cloud ingestion timestamp, application stale-data label, and operator response rule.
- Treating freshness as a dashboard label alone leaves the system ambiguous.
- Manufacturing may assign a device identifier and certificate.
- The gateway may authorize which devices can join.
Major section
Requirements Cross the Five Layers (continued)
Provisioning may bind the device to an owner, site, room, vehicle, patient, or asset.
- The physical layer, edge layer, connectivity layer, cloud layer, and application layer all need a share of the requirement.
- The cloud may map device identity to tenant identity and permissions.
- The application may expose ownership transfer and decommissioning.
Major section
Requirements Cross the Five Layers (continued)
Without those rules, a retry storm, duplicated command, stale reading, or silent offline device can look like normal operation until the user notices the failure.
- If any step is vague, support teams cannot safely replace, resell, retire, or investigate the device.
- Data semantics are the other hidden dependency.
- Requirements make those meanings explicit.
Deck summary
Key takeaways
The idea sounds useful, but the owner still needs to know what is sensed, who gets the warning, how soon it arrives, and what happens when power or the link fails.
- A farm sensor optimized for millisecond response while ignoring battery life is solving the wrong problem.
- If any one is missing, the device is not IoT -- it may be embedded (no connectivity) or connected (no internet reach), but not IoT.
- The Three Ingredients Test is a requirement filter, not a vocabulary exercise.
- The requirement is the service path, not a specific radio.
Retrieval practice
Recall check 1 of 2
Blueprint Bina says: answer from memory, then check your reasoning.
Q1A soil sensor reaches a cloud service through a LoRaWAN gateway. How does the chapter classify it?
Show answer
Answer: C The three ingredients can be completed through a gateway.
Retrieval practice
Recall check 2 of 2
Blueprint Bina says: answer from memory, then check your reasoning.
Q2A Bluetooth-only lock adds a working Wi-Fi bridge to a remote service. What should the requirement review trace?
Show answer
Answer: B Classification depends on the thing, computation, and direct or gateway-mediated reach working together.
Print reference
Answers
Answer key.
- C · The three ingredients can be completed through a gateway.
- B · Classification depends on the thing, computation, and direct or gateway-mediated reach working together.