Test a two-zone farm dependency

Steps

Screens captured against Cisco Packet Tracer Cisco Packet Tracer 9.0.1 on Ubuntu 22.04 (Apptainer/Xvfb); project saved and reopened 2026-09-10 on 2026-09-10; the tool may have moved on — the text steps are the contract.

1. 1 Step 1

   Do

   Open lab.pkt in Packet Tracer and inspect the named Things in the Logical workspace.

   You will see

   North-Humidity and North-Sprinkler form one zone; South-Temperature and South-Sprinkler form another beside Farm-Server.

   Why it matters

   Naming each sensor, dependency, action, and evidence source makes the test boundary reproducible.

2. 2 Step 2

   Do

   On the Logical canvas, read the chapter-specific names beneath the devices and compare their roles.

   You will see

   The Logical canvas shows two sensing zones and their local sprinkler Things in this lab's named workspace.

   Why it matters

   Different physical jobs can share a network while still requiring different thresholds, safe states, and operating evidence.

3. 3 Step 3

   Do

   On the Logical canvas, trace the solid PC0 cable and any visible dotted wireless associations back to Home Gateway0.

   You will see

   The solid black line connects PC0 to Home Gateway0; where dotted lines are visible, they mark wireless associations.

   Why it matters

   A visible association is evidence of topology, not by itself proof of authentication, registration, or delivery.

4. 4 Step 4

   Do

   On the Logical canvas, identify each object that has no visible gateway line; do not count it as registered evidence.

   You will see

   Objects without a line to Home Gateway0 remain visibly outside the registered control path.

   Why it matters

   Packet Tracer physical objects are not automatically network endpoints, so an absent line must remain explicit.

5. 5 Step 5

   Do

   On the Logical canvas, use the model captions and names to separate sensing, actuation, service, and physical-context roles.

   You will see

   The device names and model captions distinguish sensors, actuators, service endpoints, and physical context.

   Why it matters

   Role labels keep a plausible diagram from being mistaken for measured control-loop behavior.

6. 6 Step 6

   Do

   Close and reopen lab.pkt, then compare the restored Logical workspace with this evidence image.

   You will see

   After reopening the saved project, the same lab-specific names, positions, and connection lines remain visible.

   Why it matters

   A reopen check proves persistence of the saved topology without inventing runtime readings or protocol semantics.