Chapter 49 — Engineering thesis

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 Arguing from evidence"]
  N3["49.3 Limitations and future work"]
  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 Arguing from evidence"]
  N3["49.3 Limitations and future work"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX145"]

[Learning outcomes]
    |
    v
[49.1 Thesis structure]
    |
    v
[49.2 Arguing from evidence]
    |
    v
[49.3 Limitations and future work]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX145]

Learning outcomes

You will (1) write the engineering thesis; (2) argue from evidence; (3) state limitations and future work.

49.1 Thesis structure

Jonas's thesis argues that a small community organisation can operate a secure token system if security is engineered across the whole lifecycle and its operations, not only in contract code. Chapters cover the problem, requirements, architecture, implementation, verification, operations and the capstone. Each chapter presents claims with evidence from the dossier. Dr Nwosu advises him to keep the argument visible in every chapter's introduction and conclusion. He drafts the introduction last, after the evidence chapters are complete, so it describes the argument as it actually developed. Dr Nwosu reads each draft chapter and marks claims that lack evidence.

49.2 Arguing from evidence

Jonas supports his argument with measured results: full role policy conformance, no invariant violations in production months, reconciliation mismatches traced and fixed, recovery times within targets, and external review findings resolved. He compares his approach with public guidance from EthTrust, ConsenSys and NIST IR 8202, showing where he followed and adapted it. He avoids claiming the system is secure in absolute terms, citing EthTrust's statement that no review guarantees security. Each comparison is tabulated, so readers can see which guidance items were adopted, adapted or not applicable.

49.3 Limitations and future work

Limitations include a permissioned ledger with only three validators, a small member base, synthetic test data and one external review. Future work includes extending to neighbouring villages with independent validator operators, formal verification of the minting contract, and a longer study of member custody choices. Stating limitations and future work honestly shows assessors that Jonas understands the boundaries of his results, which is part of engineering maturity. He also explains how each limitation might have affected his results and what evidence would be needed to address it.

Worked example

The thesis argues lifecycle-wide security engineering, supported by measured results and comparison with public guidance, with four stated limitations and three future directions.

Synthetic case. Results and the thesis are synthetic; EEA EthTrust, ConsenSys best practices and NIST IR 8202 are real sources.

Errors and limits

Claiming absolute security for a system contradicts the limits stated by review standards.

Exercises

• EX145 — Thesis argument. What does the thesis argue? Rubric: 3 = secure token systems need lifecycle-wide engineering;; 2 = lifecycle;; 1 = code alone;; 0 = none.
• EX146 — Evidence example. Name one measured result used. Rubric: 3 = full role policy conformance;; 2 = recovery within targets;; 1 = vague;; 0 = none.
• EX147 — Future work. Name one future direction. Rubric: 3 = formal verification of the minting contract;; 2 = independent validators;; 1 = vague;; 0 = none.

Synthesis

An evidence-based argument with honest limits forms a strong engineering thesis.

Continue studying — chapter 49 of 50

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