Chapter 1 — Computing systems
Lesson map
Lesson 01 published. Map, example, EX001.
flowchart TD
N0["Learning outcomes"]
N1["1.1 The case"]
N2["1.2 The systems in use"]
N3["1.3 Why identity ties them together"]
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 The case"]
N2["1.2 The systems in use"]
N3["1.3 Why identity ties them together"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX001"]
[Learning outcomes]
|
v
[1.1 The case]
|
v
[1.2 The systems in use]
|
v
[1.3 Why identity ties them together]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX001]
Learning outcomes
You will (1) describe the computers and services a small multi-site business uses; (2) identify where accounts live; (3) explain why identity ties them together.
1.1 The case
Kai Thompson is a technologist student at the fictional Harlow Polytechnic, mentored by Ruth Adeyemi, an experienced systems administrator. His work placement is with the fictional Fernhill Veterinary Group, which runs five clinics, north, south, east, west and central, with about 85 staff: vets, nurses, receptionists, a small finance team and one part-time IT person. Staff use a cloud directory and office suite, a practice management system holding clinical and client records, a booking system and shared workstations at reception desks. Kai's placement goal is to bring order to Fernhill's accounts and access over three years, using only synthetic data in this book.
1.2 The systems in use
Kai lists every system: the cloud directory and office suite for email and documents; the practice management system, which stores animal records, prescriptions and client contact details; the online booking system; a payroll service; and the clinics' shared reception workstations and tablets used in consulting rooms. For each system he records who supplies it, which Fernhill person looks after it, what data it holds and how staff sign in. This inventory is the foundation for everything that follows, because nobody can manage access to systems they have not listed.
1.3 Why identity ties them together
Every system decides who may use it and what they may do. If each system keeps its own separate accounts, staff collect many passwords and leavers are easily forgotten somewhere. If systems trust the cloud directory, one account per person controls access everywhere, and disabling it removes access in one step. Kai finds that the office suite and booking system use the directory, while the practice management system and payroll keep their own accounts. Identity is therefore the thread that connects Fernhill's systems, and where that thread breaks, gaps appear.
Worked example
Kai's inventory lists six systems across five clinics; two use the cloud directory, two keep separate accounts and two are shared devices.
Synthetic case. Kai Thompson, Harlow Polytechnic, Ruth Adeyemi, Fernhill Veterinary Group and all systems are synthetic.
Errors and limits
Starting access work without a complete system list leaves unknown systems where accounts persist.
Exercises
- EX001 — Fernhill size. How many clinics and staff does Fernhill have? Rubric: 3 = five clinics, about 85 staff;; 2 = five;; 1 = one;; 0 = none.
- EX002 — Separate-account systems. Which systems keep separate accounts? Rubric: 3 = practice management system and payroll;; 2 = two;; 1 = office suite;; 0 = none.
- EX003 — One-step removal. What is the benefit of systems trusting the directory? Rubric: 3 = disabling one account removes access everywhere;; 2 = one step;; 1 = speed;; 0 = none.
Synthesis
A complete inventory of systems and sign-in methods shows where identity connects or fragments a business.