MSc Projects

Overview

As part of their MSc studies, all students undertake a substantial Computer Science project, resulting in a dissertation. The projects are guided by at least one supervisor from the School.

Dissertation projects will involve various sets of skills and explore various areas of computer science. They may be very technical, or very mathematical, or involve design and interviews, focus on system building, or involve detailed analysis of existing solutions. However, they are all expected to be equally difficult, and of equal quality.

The dissertation also has to be clearly related to the specific MSc programme, e.g. an MSc AI dissertation has to fall broadly into the area of AI, and an MSc HCI dissertation should be related to human-computer interaction. Dissertations in IT-related programmes should demonstrate competence in non-trivial use of IT.

The development and supervision process is decided by the student and supervisor but will involve regular meetings to decide direction and monitor progress. Each student is responsible for managing and completing their project.

There are deliverables due at fixed points throughout the project, but marking is holistic. The outcome will be an artifact such as a product, software, or a formal system. Although many projects involve software development, this is not a requirement.

Although many dissertations create exciting new results, the projects are not expected to advance the state of the art the way PhD theses are. However, there has to be a novel element to the work, not simply repeating existing work. It is important that it is challenging enough and demonstrates your ability to apply CS and/or IT skills gained through your degree to a large, complex problem.

Important people

Projects coordinator: project-coord-cs@st-andrews.ac.uk
Director of Postgraduate Teaching: dopgt-cs@st-andrews.ac.uk
Director of Teaching: dot-cs@st-andrews.ac.uk

Please always use the appropriate alias, not personal email addresses.

MSc dissertation modules

CS5099 - Dissertation in computer science (60 credits)

For students on postgraduate MSc programmes. This is an individual project.
Done over the summer (May-Aug)

CS5098 - Group project and dissertation in computer science (60 credits)

For students on postgraduate MSc programmes. This is the group version of the dissertation.
There is a degree of collaboration with other students, but write-up and evaluation are individual.
Done over the summer (May-Aug)

For information on CS5199 see the MSci project page. For information on CS4099, CS4098 and CS4796 see the SH project page.

Location of studies

The policy on Location of Studies applies for the entire duration of the MSc programme, including the summer dissertation period.

Under the policy, you must live within “commutable distance from St Andrews” over the dissertation period, which is loosely defined as you being able to attend the School on a daily basis if required, and more formally as within 75 miles of St Andrews.

If you wish to be further away from St Andrews for more than 10 consecutive days, you must obtain formal approval in advance via the Director of Postgraduate Teaching, having first obtained the approval of your supervisor.

Note also that the policy states that “Overseas students must seek expert advice on the conditions of their visa prior to leaving the UK for any reason”.

Project allocation process

Allocation for CS5099/CS5098 typically takes place in early S2. Your dissertation project may be completed individually (CS5099), or may be part of a larger project which involves group work (CS5098). In both cases, you will write an individual dissertation, which is marked individually. Allocation centres around the project proposals list.

Staff advertise projects on the list and students can look for interesting projects. Students should come up with a shortlist of projects and contact the supervisors directly to discuss the project, the requirements (background knowledge and experience, what is expected in terms of programming or maths, supervision style, etc.). Keep in mind that some supervisors get many requests from students and that there is a limit per supervisor. Typically the mean number of students per supervisor is around three.

Once both the supervisor and the student agree, the student should email the project coordinator (and CC all supervisors) to register this choice. The final allocation is done by the project coordinator. The allocation is not finalised until the project coordinator confirms the allocation.

The list allows sorting based on topics, modules, and tags, but these are meant mostly for guidance, so do approach a supervisor if you are interested in a topic even if your module is not explicitly listed.

Self-proposed projects

A small but significant number of students choose to propose their own project. This is fine, but is a bit more involved because the original idea often needs to be refined together with a potential supervisor to make sure that it is relevant, doable, and challenging. Make sure to leave some extra time if you decide to go down this route – don’t leave it to the last moment! There is no automatic right to do a self-proposed project; a project can only be done if a supervisor agrees to supervise it.

In this case, the student writes a 1-2 page summary of what they propose to do, how they propose to do it, and what the outcome will be. Then they can contact a potential supervisor (typically someone with expertise in the topic) asking them to supervise. If you are not sure who would make the best supervisor for a particular topic, contact the project coordinator to make some suggestions.

Once the project is agreed, email the coordinator (and CC the supervisors) as before.

Supervision meetings

You must attend regular supervision meetings with your supervisor, starting at the beginning of the dissertation period (week beginning 20th May). Usually meetings will be held every week in the early stages of the project, and again toward the end of the dissertation period. In the middle part, meetings may be a little less frequent if you and your supervisor both agree, but should still be held at least every two weeks.

At least four of the supervision meetings, well spaced over the dissertation period, must be held in-person, as part of the School’s engagement monitoring process. Beyond this, supervisors have discretion to meet online if they consider it appropriate, or to require students to meet in-person.

Staff are strongly encouraged to take holiday leave during the summer, and may also travel for research purposes, so it’s likely that your supervisor will be away for parts of the period. If necessary they will arrange for another staff member or a research student to provide informal supervision during their absence.

Supervisors will record meeting attendance in MMS. These records will be monitored and academic alerts will be issued for unapproved absences.

Project deliverables

These are the same for most CS-coded dissertations. The deadlines are specified on MMS.

Description, Objectives, Ethics & Resources (DOER)
Ethics form (ethics category 1/2; see ethics section below)
Ethics form (ethics category 3/4; see ethics section below)
Plan & context survey
Interim demo
Final report & materials
Final demo

All deliverables are mandatory and you may be issued an academic alert if you miss them. Regular supervision meetings are also mandatory.

DOER

The DOER is a short document you will need to submit as your first deliverable. It is not a form, and has no fixed template, but is a mini report of its own. It generally consists of about two pages of text.

You and your supervisor will have to agree on everything in the DOER document. Typically, the process looks like this:

Schedule a meeting with your supervisor(s) to flesh out the description, objectives, and any needed resources.
Write this all up in a word processor, following the structure presented above.
Present this to your supervisor(s) and make sure you all agree with the contents (this can be done via email or in person).
Submit the DOER to MMS.

In the DOER you must include the following four sections.

Description

The title and a short description of the project aims, context and background. It should explain the big picture of what you would like to achieve, why it is important, and how you intend to go about doing it (e.g. by using some kind of technology or developing a new algorithm, or following a particular methodology, etc.)

Objectives

This is a list of clearly defined, measurable goals you intend to achieve by the end of your project. This could include any software artefacts you intend to submit in the end, results of an evaluation (for surveys or research algorithms), etc. Your performance will be measured against these objectives.

Typically, you will list about 3–5 primary objectives which are necessary for a project to be deemed successful, and further 3 or so secondary objectives which allow a successful project to be extended in an interesting direction. Occasionally, tertiary objectives may also be listed, but these are comparatively rare.

Ethics

Ethical issues must be considered for all projects, and one of the following categories selected:

No ethical issues: no human subjects are involved in the project, and no personal data is processed.
Artifact evaluation: the only involvement of human subjects and personal data is a user evalution of the project artifact, limited to members of the university and maximum 60 minutes contact.
Amendment: the supervisor already holds ethics approval covering the project, and the student needs to be added to it.
Full application: if none of the other categories are applicable, a full ethics application must be submitted.

You must indicate which category has been selected in your DOER submission.

If category 1 or 2 is selected, you must also submit the corresponding simple form (signed by supervisor) to the Ethics page on MMS, with the same deadline as the DOER. These forms are linked from the student handbook ethics page.

If category 3 or 4 is selected, you must submit the ethics amendment or full application form to the Ethics page, with a later deadline. This is only for documentation purposes and does not automatically submit the application to the Ethics Committee, so you should also email ethics-cs@st-andrews.ac.uk to say that you have submitted the form. You are very strongly advised to submit applications well before the deadline; this should be considered a final cut-off, after which the project as intended will probably not be viable.

Failure to get ethical approval may endanger your project and hence your degree, so do take this seriously!

Resources

This is a list of any special resources your project will need: hardware, software, licenses, access to infrastructure (e.g. compute servers), drones, etc. Think ahead, but be realistic – the School will not be able to fulfill all requests.

Most projects can be completed using standard school equipment, in which case this section will contain only a short statement confirming this.

Plan and context survey

This deliverable consists of a very early draft of your dissertation – normally as one PDF document. There are three elements:

Table of contents with all the chapter and section headings. These will form the skeleton of your thesis and ensure that your report is properly structured;
Mostly complete review of related work (literature review). This is normally 5-10 pages long and will include citations to most important papers on this topic and explain how they relate to the task;
Work plan for the rest of your dissertation period (week-by-week) indicating the main tasks and objectives you will need to tackle and when you will be doing this. This is usually in the form of a table, a Gantt chart, or similar.

Interim demo

Partway through the project, you will upload your current work to MMS. This can include all your code, any drafts of the report, evaluation scripts, outputs of your algorithms such as graphs, evaluation data, etc.

You should also make arrangements to show your work to your supervisor. This deliverable is mandatory and failure to submit will result in an academic alert.

Final report

The final report is extremely important!

It will form a major part of your final mark, and a poor report can undo a lot of otherwise good technical work. The report should show that you understand your work, show where the design and work went, and convince the markers that it is important and valuable. It should critically reflect on the project and what was achieved.

Reports should be understandable to any CS staff – not all markers will be specialists in all fields. Sending a draft to your supervisor for comments is very important and the more time you leave for this, the better the result is likely to be.

There are examples of past reports in the project library in the student handbook and it is good to study them, as well as looking at the report guidance linked below.

There is a hard 15,000 word limit on all MSc dissertations. This is a maximum, not a target to be aimed for. A good report will be well-structured, clear and informative, demonstrate understanding of the topic and related work, and not be overly verbose. Talk to your supervisor for tips and feedback.

Submission

There is a 600 MB limit for MMS submissions. Your submission should include your report, and any artifacts developed by you such as original code, scripts and build instructions, configuration files, etc. It should not include:

other people’s code, such as libraries
copies of repositories (provide a link to the repository instead)
python or javascript module trees
virtual machines such as JVM
machine learning datasets (especially not sensitive ones, like medical datasets!)

Assessment

MSc projects are evaluated by two CS academics. Normal coursework descriptors apply. Assessment will be based on the report, any demonstration, and the quality and difficulty of any submitted artefacts. The markers will agree a joint mark and feedback which will be released to the students once all marks are finalised.