Chapter 49 — Engineering thesis | Engineering Human factors and cyber policy

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Chapter 49 — Engineering thesis

Lesson map

Lesson 49 published. Map, example, EX145.

flowchart TD
  N0["Learning outcomes"]
  N1["49.1 Thesis structure"]
  N2["49.2 Coherent argument"]
  N3["49.3 Citation and caution"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX145"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["49.1 Thesis structure"]
  N2["49.2 Coherent argument"]
  N3["49.3 Citation and caution"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX145"]

[Learning outcomes]
    |
    v
[49.1 Thesis structure]
    |
    v
[49.2 Coherent argument]
    |
    v
[49.3 Citation and caution]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX145]

Learning outcomes

You will (1) structure an engineering thesis on a human factors programme; (2) present design, verification and validation coherently; (3) write with appropriate citation and caution.

49.1 Thesis structure

Aiko's thesis is titled Designing a reporting-centred security programme for a water utility. Its chapters cover the problem and context, the literature, requirements, design alternatives and choice, implementation, verification, validation, the contractor capstone and conclusions. Each chapter ends with a short summary linking to the next. The structure follows the engineering life cycle, which helps examiners trace each design decision from requirement to evidence. Appendices hold the verification tables, lab code and ethical approvals, with synthetic examples replacing sensitive data. It runs to ninety pages.

49.2 Coherent argument

The thesis argues that a programme centred on reporting, fast feedback and supporting controls reduces exposure more effectively than a compliance-led programme, while respecting staff. Aiko supports this with her validation and pilot results, and with literature such as Adams and Sasse (1999), Sasse, Brostoff and Weirich (2001) and Bada, Sasse and Nurse (2019). She is careful to separate what her data show from what the literature suggests, and she presents her before and after results as consistent with, rather than proof of, the argument.

49.3 Citation and caution

Aiko checks every citation against the original source and records DOIs only where she has confirmed them. She uses cautious language: results suggest rather than prove, and effects are described with their uncertainty. She acknowledges that her case is one utility and that other organisations may differ. Prof. Kerr reads a full draft and asks for one change: to move the ethical rules for simulations from an appendix into the main text, because they are central to the design rather than an administrative detail.

Worked example

Aiko structures her thesis along the engineering life cycle, separates her evidence from literature and states results cautiously.

Synthetic case. The thesis is synthetic; the cited works are real.

Errors and limits

One case limits generalisation. Literature may not fit the utility context.

Exercises

EX145 — Structure basis. What does the thesis structure follow? Rubric: 3 = the engineering life cycle;; 2 = life cycle;; 1 = vague;; 0 = none.
EX146 — Separation. What does Aiko keep separate? Rubric: 3 = what her data show and what the literature suggests;; 2 = separation;; 1 = vague;; 0 = none.
EX147 — Requested change. What change did Prof. Kerr request? Rubric: 3 = move the ethical simulation rules into the main text;; 2 = ethics;; 1 = vague;; 0 = none.

Synthesis

A good engineering thesis traces decisions to evidence and states results with care.

Continue studying — chapter 49 of 50

← Chapter 48 (draft) · Course chapter index · Chapter 50 (draft) →