Chapter 49 — Engineering thesis
Lesson map
Lesson 49 published. Map, example, EX145.
flowchart TD
N0["Learning outcomes"]
N1["49.1 Structure"]
N2["49.2 Argument"]
N3["49.4 Contribution"]
N4["Writing the discussion chapter"]
N5["Citing sources accurately"]
N6["Future work"]
N7["Synthesis"]
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 Argument"]
N3["49.4 Contribution"]
N4["Writing the discussion chapter"]
N5["Citing sources accurately"]
N6["Future work"]
N7["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7 --> Q["EX145"]
[Learning outcomes]
|
v
[49.1 Structure]
|
v
[49.2 Argument]
|
v
[49.4 Contribution]
|
v
[Writing the discussion chapter]
|
v
[Citing sources accurately]
|
v
[Future work]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX145]
Learning outcomes
You will (1) write the thesis; (2) structure arguments; (3) state limits.
49.1 Structure
The thesis follows the engineering lifecycle so readers can see how each stage led to the next: the problem and context; requirements; analysis of threats and options; the chosen design; implementation and migration; verification and validation; evaluation against criteria; and discussion with conclusions. Each chapter opens by stating what it contributes and closes with what the next chapter takes from it. This structure lets a reader start with the problem and follow a continuous argument, rather than meeting a collection of separate reports.
49.2 Argument
A thesis is an argument, not a diary. Kofi's central claim is that a small public body can substantially reduce internal exposure with modest, verified segmentation without harming service. Every supporting claim in the thesis refers to evidence in the dossier by identifier, so readers can check it. Where evidence is weaker, such as the small research sample, he uses careful language and explains why. He removes sections that describe work but support no claim, which shortens the thesis and makes the argument easier to follow.
49.3 Limits
Dr Vasquez asks Kofi to make limits clearer, and he gathers them into a dedicated section as well as noting them beside affected results. The main limits are: a single council as the setting; a three-month availability period; a research sample of eight offices; and some evidence available only from lab tests. For each, he explains how it might affect the conclusions and what would reduce it. Clear limits make the thesis more credible, because readers trust authors who show they understand the weaknesses of their own evidence.
49.4 Contribution
Kofi states his contribution plainly: a documented, verified approach to segmenting a small, multi-site public-sector network, including the zone model, templated policy, migration method, test suite and evidence structure, together with measured outcomes from one real deployment. He does not claim new theory. Engineering theses often contribute by showing that known principles can be applied successfully under real constraints, and by documenting the method well enough that others can reuse it. Being precise about the contribution prevents examiners from judging the thesis against claims it never made.
Writing the discussion chapter
The discussion chapter interprets results rather than repeating them. Kofi asks what the results mean for the council, for similar small public bodies and for practice more broadly. He compares his outcomes with expectations from the literature, such as the value of segmentation in limiting lateral movement described in NIST guidance and the link between policy complexity and errors. Where results differ from expectations, he offers explanations and notes which ones the evidence supports. He also discusses alternatives he did not choose, explaining when those alternatives might be better, so readers in different situations can adapt the approach.
Citing sources accurately
Every factual claim from outside the project cites a source, and every source is checked. Kofi cites NIST special publications, RFCs and peer-reviewed papers, confirming each title, number and year against the original document. He avoids citing summaries or blog posts when the original standard is available. When a source makes a weaker claim than he wants to make, he either softens his own claim or finds stronger evidence. Accurate citation lets examiners verify claims and shows respect for the work of others, and it protects the thesis from errors copied through secondary sources.
Future work
A good thesis ends with clear future work. Kofi lists four directions: a longer availability study across all offices once second links are complete; a larger study of whether early unexpected denies predict complaints, pooling data from neighbouring councils; evaluation of stronger device authentication on the staff network to reduce reliance on network location; and assessment of whether finer segmentation within the server zone is worthwhile. Each item states why it matters and what data would be needed. Future work shows that the author understands the limits of what was done and where the next valuable questions lie.
Worked example
Dr Vasquez reviews drafts and asks for clearer limits.
Synthetic case. The thesis is synthetic.
Errors and limits
Claims without evidence weaken the thesis.
Exercises
- EX145 — Thesis structure. List the seven parts. Rubric: 3 = seven;; 2 = five;; 1 = fewer;; 0 = none.
- EX146 — Contribution. State the contribution. Rubric: 3 = documented verified approach;; 2 = design;; 1 = vague;; 0 = none.
- EX147 — Limits. Name two limits. Rubric: 3 = two;; 2 = one;; 1 = vague;; 0 = none.
Synthesis
The thesis presents a verified engineering contribution with honest limits.
Continue studying — chapter 49 of 50
← Chapter 48 (draft) · Course chapter index · Chapter 50 (draft) →