Chapter 49 — Engineering thesis
Lesson map
Lesson 49 published. Map, example, EX145.
flowchart TD
N0["Learning outcomes"]
N1["49.1 Structure"]
N2["49.2 Key results"]
N3["49.3 Lessons"]
N4["49.4 Limitations"]
N5["49.5 Contribution"]
N6["Writing process"]
N7["Discussion"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7
N7 --> EX["Worked example"]
EX --> Q["Exercise EX145"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["49.1 Structure"]
N2["49.2 Key results"]
N3["49.3 Lessons"]
N4["49.4 Limitations"]
N5["49.5 Contribution"]
N6["Writing process"]
N7["Discussion"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7 --> Q["EX145"]
[Learning outcomes]
|
v
[49.1 Structure]
|
v
[49.2 Key results]
|
v
[49.3 Lessons]
|
v
[49.4 Limitations]
|
v
[49.5 Contribution]
|
v
[Writing process]
|
v
[Discussion]
|
v
[Worked example] --> [Exercise EX145]
Learning outcomes
You will (1) write the engineering thesis; (2) synthesise design, evidence and lessons; (3) state limitations.
49.1 Structure
Problem, requirements, design, implementation, verification, validation, operations, lessons.
The order follows the life of the project, so a reader can see how each stage led to the next. Each chapter opens with a short summary and ends with links to evidence. Mateo keeps background material brief and refers to the course chapters for detail, so the thesis concentrates on what he did and what he found. Lessons come last because they draw on everything before. Appendices hold the procedures. Dr Novak approved the outline.
49.2 Key results
Exposure reduced from about 294 to 21 PC-days per fortnight (estimate); availability 0.9999; help-desk breakdown calls halved.
Mateo labels the exposure figure as an estimate because it comes from the model, not from counting exposure directly. The availability figure combines measured repair times with the baseline failure count. The call result comes from the research study and its limits apply. Each result in the thesis carries its label and its link to evidence, following his supervisor's request to separate estimates from measurements. Dr Novak checked the labels.
49.3 Lessons
Audit before enforce; test restore scope; design recovery for the design.
Each lesson comes from a specific moment in the project. Audit before enforce comes from the accessibility reader that the first audit week would otherwise have blocked. Testing restore scope comes from the temporary folder that survived the first restore test. Designing recovery for the design comes from the trial's printer gap and the review's finding on the signing key. Mateo explains each with its evidence. Each lesson is short.
49.4 Limitations
One organisation; synthetic-structure figures; older hardware.
One organisation means the results describe Fernhill's PCs, staff and patrons, and other networks may differ. Many figures were produced with synthetic data shaped to match Fernhill's records, so they show how the methods work rather than precise facts about the library. Older hardware may have made some results, such as restore times, worse than newer equipment would. Mateo states how each limit could change the conclusions. Readers can then judge how far the results apply to their own setting.
49.5 Contribution
A tested, documented design for public PC services others can adapt.
The design is written so another library or a school could adopt it: the requirements, the control specifications, the test procedures and the runbooks are all included and use standard tools. Mateo does not claim novelty for any single part, since each draws on published guidance. What the thesis offers is the combination, tested end to end in a real public service, with the evidence and the lessons. Fernhill agreed to share it.
Writing process
Mateo writes the thesis chapter by chapter, starting with methods and results while details are fresh, then the introduction and discussion. Dr Novak reviews each chapter. Figures are generated by scripts so they can be re-created if data change.
He keeps a list of claims and checks each against the dossier before submission.
Discussion
The discussion compares results with expectations: restore and availability performed as planned; help-desk calls about saving work rose, which was not anticipated.
Future work
Thin clients, attestation and longer studies are proposed.
Acknowledgements
He thanks Fernhill staff and Dr Novak.
Final review
Dr Novak signs off the thesis for submission.
Formatting
Tables and figures follow the institute's style.
Word count
It stays within the limit.
Claims check
Every claim is checked.
Accessibility
The thesis follows accessible formatting.
Submission
It is submitted on time.
Abstract
A short abstract states problem, method and results.
Key message
The thesis's key message is that a simple, tested reset design, built with users, can greatly reduce privacy and integrity problems on public computers.
Peer reading
Two classmates read drafts and flag unclear passages, which Mateo rewrites.
Structure note
Each chapter begins with a short summary and ends with links to evidence.
Worked example
Dr Novak asks Mateo to separate estimates from measurements. He labels each figure accordingly.
Synthetic case. Synthetic.
Errors and limits
Mixing estimates and measurements misleads readers.
Exercises
- EX145 — Structure. Give the thesis structure. Rubric: 3 = problem to lessons sequence; 2 = partial; 1 = vague; 0 = none.
- EX146 — Results. State two key results. Rubric: 3 = exposure estimate, availability, calls halved; 2 = two; 1 = one; 0 = none.
- EX147 — Labelling. How were figures labelled? Rubric: 3 = estimate vs measurement; 2 = partial; 1 = vague; 0 = none.
Synthesis
Synthesise honestly, separating estimates from measurements.
Continue studying — chapter 49 of 50
← Chapter 48 (draft) · Course chapter index · Chapter 50 (draft) →