Some notes on your viva voce exam
So you have a viva coming up for your honours or masters dissertation, and you’re a bit worried. Well that’s OK. This here page is meant to answer some of your questions regarding the following:
- what it’s for,
- what to expect,
- and what to do in preparation.
Purpose
The main purpose of your viva is to establish that you are the author of the work that you’ve submitted. This doesn’t mean that anybody thinks that you’ve engaged in any academic misconduct, just that the best way to confidently dismiss any suspicions is by having a conversation with you face-to-face. The basic idea is that for you to be able to answer any questions that might come up you will have to know the dissertation project in detail, and be able to explain both the content and the reasoning that went into it. This is mainly for the benefit of the second marker who usually has not see you very often during the project duration. Ideally your supervisor will have seen the development of your project, and associated writing, regularly during supervision throughout the duration of your project. But sometimes this is not the case. Occasionally students will work very independently, or a supervision team might change due to changeovers in academic staff, so the viva can also help the supervisor.
A secondary benefit is that you might not have written about everything that you did during the project, or you might not have had the right words to fully explain your project in writing in the way that you wanted to. In the past, some students have pre-edited their dissertations to remove or omit work that they’d done that they didn’t think was relevant, and didn’t speak to their supervisors about where this was a good idea. During the viva it has become clear that additional work was done, and often the discussion during the viva has filled in gaps that that the markers noticed. Also, you might just be able to better explain your work verbally and so you might be able to garner a few additional marks as a result.
Finally, the viva is often the last occasion that students meet with teaching staff, other than perhaps at graduation, so it can be the last opportunity to get some feedback on what you’ve just spent months working on. So the viva is a feedback opportunity and therefore a learning opportunity.
Expectations
You should turn up with the expectation that you will have a conversation about your work. Nothing more. There is no set structure, so anything in your dissertation might become the basis for a chat. This is not however in order to try to catch you out and justify taking away marks. Rather it is the best way to establish how well you understand your own work, assuming you are actually the author of the report. Remember though that your markers are often also interested in the projects that they are marking, so they might just want to geek out a bit. Your markers also, usually, have a lot of computer science or software engineering experience, and quite often just like talking about research, computers, and just geeking out a bit. So if you’ve done something interesting, then the viva might go on a bit. Not as a punishment, but as a reward for having done interesting work. For the avoidance of doubt: this is a good thing.
Procedure
Your viva will normally start with an opening question along the lines of “Can you please summarise your project?”. The conversation will usually just follow from whatever you say in response. So it is a good idea to have pracised a 2-5 minute introductory overview. If you have already presented the work in a poster session then this is how we would expect things to go. If you didn’t then you might have been asked by your supervisor to prepare a 5-10 minute presentation, perhaps involving a software demonstration, in lieu of the poster session.
Whilst the conversation during the viva will normally develop naturally, your markers will use their own notes, from reading your dissertation, to formulate questsions. For the most part, these questions will be related to specific chapters and sections of your report. Some markers might even take you through the report fairly sequentially, asking questions as they go along from the introduction through to the conclusions.
What to do?
Before the viva, relax. I know that this is easier said than done. Have a copy of your report handy so that you can look things up if necessary. No-one is expecting you to recall specific details of data, or an exact phrasing of a given sentence. It’s a good idea to skim over your report again before the viva, just so you can easily find things if asked. Additionally, if you’ve created software during your project, which is usually expected in the majority of computing dissertations, then you can also demonstrate this during your viva. This can be a very good way to convey the details of your project if the words escape you.
Remember that a conversation is a two-way street, so you can also ask questions, particularly if you are unsure how to answer something and need clarification or for a question to be rephrased in a way that you can answer.
Summary
The viva is not meant to catch you out. It’s not used to try to take marks away, but is basically your final opportunity to gain perhaps a few extra marks just in case. As a rule I’ve not seen grades go down as a result of a viva, except for clear academic misconduct, but I have seen grades occasionally go up.