Chapter 1 — Computing and service architecture
Lesson map
Lesson 01 published. Map, example, EX001.
flowchart TD
N0["Learning outcomes"]
N1["1.1 Depot systems"]
N2["1.2 Security in shifts"]
N3["1.3 Baseline record"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4
N4 --> EX["Worked example"]
EX --> Q["Exercise EX001"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["1.1 Depot systems"]
N2["1.2 Security in shifts"]
N3["1.3 Baseline record"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX001"]
[Learning outcomes]
|
v
[1.1 Depot systems]
|
v
[1.2 Security in shifts]
|
v
[1.3 Baseline record]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX001]
Learning outcomes
You will (1) describe the systems used at a logistics depot; (2) identify where staff interact with security during shifts; (3) record a baseline of security tasks.
1.1 Depot systems
Priya Raman, a technical trainee at the fictional Eastvale Technical College, joins the IT support team at the fictional Kestrel Logistics, a company with 300 staff across three depots. Her instructor, Tom Hallett, asks her to list the systems staff use. Warehouse workers use handheld scanners and shared terminals to log deliveries. Office staff use laptops, email and a dispatch system that holds customer addresses. Drivers use a mobile app for routes. Priya draws a simple diagram showing which group uses which system, and how the systems connect to the cloud services that run dispatch.
1.2 Security in shifts
Priya follows a warehouse shift and an office shift to see where security appears. Warehouse workers log into shared terminals with a single team password written on the wall, because each login takes time and shifts are busy. Office staff receive many emails from customers and carriers, some with attachments and links. Drivers sometimes receive texts claiming to be from the company about route changes. Priya notes each point and the pressure staff face there, such as loading deadlines or angry customers on the phone.
1.3 Baseline record
Priya records a baseline: number of systems, logins per shift, shared passwords in use, and how staff currently report anything suspicious. She finds there is no clear reporting route; most people tell their supervisor, who may or may not tell IT. She writes the baseline as a one-page summary for Tom and the IT lead. A baseline lets the team measure later whether changes improved things, and it shows where effort is most needed before any tool or policy is changed.
Worked example
Priya maps depot systems, observes security points during shifts and records a baseline including a shared wall password and no reporting route.
Synthetic case. Kestrel Logistics is synthetic.
Errors and limits
Two shifts may not be typical. Observations should not record names.
Exercises
- EX001 — Wall password. Why is the team password written on the wall? Rubric: 3 = individual logins take time during busy shifts;; 2 = time;; 1 = carelessness;; 0 = none.
- EX002 — Driver texts. What do drivers sometimes receive? Rubric: 3 = texts claiming route changes from the company;; 2 = fake texts;; 1 = vague;; 0 = none.
- EX003 — Current reporting. How do staff currently report suspicious messages? Rubric: 3 = tell their supervisor, who may tell IT;; 2 = supervisor;; 1 = a button;; 0 = none.
- EX004 — Baseline purpose. Why record a baseline? Rubric: 3 = to measure later whether changes helped;; 2 = comparison;; 1 = vague;; 0 = none.
Synthesis
A baseline of systems and shift pressures shows where human-centred security is needed.