Chapter 18 — Supervised technical project
Lesson map
Lesson 18 published. Map, example, EX069.
flowchart TD
N0["Learning outcomes"]
N1["18.1 Planning the project"]
N2["18.2 Testing and handing over"]
N3["18.3 Reflecting on the course"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4
N4 --> EX["Worked example"]
EX --> Q["Exercise EX069"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["18.1 Planning the project"]
N2["18.2 Testing and handing over"]
N3["18.3 Reflecting on the course"]
N4["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX069"]
[Learning outcomes]
|
v
[18.1 Planning the project]
|
v
[18.2 Testing and handing over]
|
v
[18.3 Reflecting on the course]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX069]
Learning outcomes
You will (1) plan and deliver a supervised improvement; (2) test and hand it over; (3) reflect on the course.
18.1 Planning the project
For her final project Aiko proposes a release reconciliation service: every fifteen minutes it compares tools marked returned in the database with deposit releases on the ledger and alerts if a return has no release after twenty minutes, or a release has no matching return. Objectives are to detect all seeded mismatches, keep false alarms below one a week and halve the time staff spend checking releases by hand. The scope is read-only. Mr Kowal approves the plan and agrees weekly progress meetings.
18.2 Testing and handing over
Aiko builds the service with the standard library and tests it with synthetic data containing a return without a release, a release without a return and a duplicate release. It detects all three. On two weeks of synthetic normal data it raises one false alarm, from a return entered twice at the counter; she adds a duplicate check on returns. Staff checking time falls from about an hour to twenty-five minutes a week. She writes an operator guide, trains two staff and hands the service over with a scheduled review.
18.3 Reflecting on the course
Aiko reflects on eighteen months: the most useful skills were careful scoping, reading telemetry, methodical troubleshooting and clear documentation. She notes that several problems she met looked technical but had process causes, like signer rosters. She also notes the value of saying what she did not check. Mr Kowal's final assessment praises her evidence-based work and her respect for scope. The library keeps her service in use, and Aiko continues as a part-time technician while preparing for further study in the following year.
Worked example
Aiko's read-only release reconciliation detects all three seeded mismatches, gains a duplicate-return check and cuts staff checking from about an hour to twenty-five minutes weekly.
Synthetic case. The project, results and reflection are synthetic.
Errors and limits
Handing over a service without trained operators leaves it unused when its builder leaves.
Exercises
- EX069 — Release alert rule. When does the service alert for a return? Rubric: 3 = no release after twenty minutes;; 2 = twenty minutes;; 1 = immediately;; 0 = none.
- EX070 — Seeded detection. How many seeded mismatches were detected? Rubric: 3 = all three;; 2 = three;; 1 = one;; 0 = none.
- EX071 — False alarm fix. What fixed the false alarm? Rubric: 3 = a duplicate check on returns;; 2 = duplicate check;; 1 = raising limits;; 0 = none.
- EX072 — Time saved. How did weekly checking time change? Rubric: 3 = from about an hour to twenty-five minutes;; 2 = about halved;; 1 = unchanged;; 0 = none.
Synthesis
A supervised, tested and handed-over improvement completes a technical course well.
Continue studying — chapter 18 of 18
← Chapter 17 (draft) · Course chapter index · Worked results ↓ · Next course via chapter index →