Chapter 40 — Thesis and presentation | Bachelor's Quantum and post-quantum security

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 40 — Thesis and presentation

Lesson map

Lesson 40 published. Map, example, EX079.

flowchart TD
  N0["Learning outcomes"]
  N1["40.1 Thesis structure"]
  N2["40.2 Presentation"]
  N3["40.3 Defence"]
  N4["40.4 Handover"]
  N5["40.6 Practical activity"]
  N6["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6
  N6 --> EX["Worked example"]
  EX --> Q["Exercise EX079"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["40.1 Thesis structure"]
  N2["40.2 Presentation"]
  N3["40.3 Defence"]
  N4["40.4 Handover"]
  N5["40.6 Practical activity"]
  N6["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> Q["EX079"]

[Learning outcomes]
    |
    v
[40.1 Thesis structure]
    |
    v
[40.2 Presentation]
    |
    v
[40.3 Defence]
    |
    v
[40.4 Handover]
    |
    v
[40.6 Practical activity]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX079]

Learning outcomes

You will (1) structure a bachelor's thesis; (2) present findings to technical and non-technical audiences; (3) defend choices under questioning; and (4) hand over work so others can continue it.

40.1 Thesis structure

A thesis contains: abstract; introduction with problem and questions; background with sourced concepts and standards status; method; results; discussion including limitations; conclusion; references; appendices with code and lab records. Each chapter should be traceable to evidence. Label all synthetic data clearly in text and captions.

Keep the background short and focused on what the reader needs for your question; a full history of quantum computing is rarely necessary. Make the discussion answer the research questions directly, in the same order they were asked.

40.2 Presentation

Prepare two versions: a technical talk with method and results, and a short decision-oriented summary for non-specialists. Open with the question and the answer; then show evidence; end with what the audience should do. Use one idea per slide and readable figures.

Rehearse both versions with someone outside the field and note where they get lost. A figure that needs a minute of explanation is usually too complex for a slide. Keep backup slides with the detailed evidence for questions, and end on the decision you want the audience to take rather than on a summary of methods.

40.3 Defence

Expect questions on assumptions ("why z from 10 to 25?"), method ("why paired design?"), standards ("is IR 8547 final?") and ethics ("how did you obtain data?"). Answer directly, admit uncertainty, and point to evidence. If you do not know, say so and explain how you would find out.

Prepare by listing the questions you would ask if you were the examiner, especially about your weakest assumptions. Bring the lab records and decision records, so that you can show evidence rather than recall it. A calm, honest answer to a hard question counts for more than a polished answer to an easy one.

40.4 Handover

Leave a README explaining how to run the code, regenerate results and extend the work, plus a list of open questions. Quantum readiness depends on continuity; your work is most valuable when someone else can build on it.

Test the README by asking someone who has not seen the project to follow it. Include the versions of every tool used and the date of the standards status you relied on. For HCU, the handover would go to the team running the migration, so the open questions should be written as decisions they will face.

40.5 Worked example

The CBOM capstone presentation opens: "Which of HCU's cryptographic flows should migrate first? Under every quantum timeline from 13 to 25 years, the same five flows lead, headed by mortgage archive transfers." The non-specialist version ends: "Protect the branch connections carrying mortgage files within a year; plan certificate changes next." In the defence, an examiner asks why category 3 was assumed; the student cites the synthetic policy and FIPS 203's category mapping, and explains the effect of choosing category 5.

Both versions used the same figures.

40.6 Practical activity

Deliver a ten-minute presentation and a two-minute summary; answer three prepared questions from a peer acting as examiner.

Time both versions and cut anything that runs over. The peer should ask at least one question about assumptions and one about method, and should note any answer that was unclear. Afterwards, revise the slide or explanation that caused the most difficulty and record the change in your practice log, together with what you would do differently next time. Keep the peer's notes with your log.

40.7 Common errors and limits

Results without the question.
Defensiveness under questioning.
No handover materials.
Overloading slides with tables that cannot be read from the back of the room.
Claiming more certainty than the evidence supports when under pressure.
Answering a different question from the one asked.
Leaving code and data without instructions, so the work ends with the student.

Each reduces the value of a capstone that may otherwise be strong. A practice run with a peer exposes most of them in time. Schedule it a week ahead.

Exercises

EX079 — Abstract. Write a 120-word abstract for the CBOM capstone. Rubric: 3 = problem, method, result, limitation, implication.
EX080 — Defence answer. Answer: "Isn't this pointless if quantum computers never arrive?" Rubric: 3 = HNDL uncertainty argument, agility benefits, cost proportionality.

Synthesis

A thesis traces every claim to evidence; good presentations lead with question and answer; good defences admit uncertainty; good handovers let others continue.

Continue studying — chapter 40 of 40

← Chapter 39 (draft) · Course chapter index · Worked results ↓ · Next course via chapter index →