This is the main page for information about the 40 credit one-semester individual project module CM3203 for third year BSc Computer Science undergraduate students, including all specialisms. Everything related to this module is managed via PATS. Deadlines and general tasks to complete are visible when you log into PATS (once you are set up).
Project Coordinator: Frank C Langbein at LangbeinFC@cardiff.ac.uk
The setup of the module and project selection takes place in autumn term. This includes setting you up on PATS, creating proposals and selecting a project.
Further video recordings from the lectures are available on learning central/panopto for this module.
Before project selection starts, you will get an account on PATS linked to your Cardiff University account. You will receive a notification to your university e-mail address when this is done. Once setup:
You can select a staff proposal or propose your own project:
See Project Proposals for further details.
Project selection usually takes place from autumn week 5 to 11. Details will be sent to your e-mail registered in PATS, and there will be a lecture introducing the module, including project selection and suitable project topics at the start of the selection period. You will only be able to see proposals and available supervisors and agree on supervision once selection has been opened, which usually happens during or right after the introduction lecture. You will also receive a notification once this has happened.
See Project Supervision for further details.
Your project may require ethics approval. All projects involving human participants, human material or human data (Human Research), including surveys and user tests, must be subject to ethical review before the work commences. If you are unsure, discuss this with your supervisor and potentially a School Research Ethics Committee member. You cannot proceed with the work on your project without this. Sometimes it may only be an optional part of the work, but some projects crucially depend on it. You must clarify this as early as possible to ensure the project can be done. So this is an issue already to consider during project selection, even if approval may only be possible to obtain later on. The student and supervisor are responsible for ensuring the project can be done under the School's ethics regulations, including alternative project directions, should it not be possible to ensure this during selection.
Please watch the “Ethics for Dissertations” video in the panopto/learning central CM3203 folder [PDF Slides] with further details. If you need ethical approval there are two options:
The CM3203 ethics framework with the dissertation project ethics form for simplified ethics:
with the following templates/exemplars for adoption by the students:
Other issues, such as required resources (e.g. special hardware or software) or legal issues (e.g. intellectual property and licensing), must also be considered for the proposal when agreeing to supervision and during execution, with proper risk management in place.
It is the student's and supervisor's responsibility to ensure that the project is, in principle, feasible to execute and suitable for the module/degree scheme.
The project is executed in spring term, from week 1 to week 12. Regular supervisor meetings will happen in that period and are to be arranged individually with each supervisor. As the student is expected to manage the project, they are also responsible for ensuring these meetings occur. The supervisors may follow up on students not attending, but this is not guaranteed. On average, the meetings are expected to be 30 minutes per term week, but the time can be distributed arbitrarily across the 12 weeks. It may include group sessions as suitable for the project. Specific arrangements should be agreed upon between the student and supervisor. If the student cannot get hold of the supervisor within the agreed schedule, they should contact the project coordinator (considering that usually, it can take up to a week for the supervisor to respond, even if often they are faster).
The work on the project is towards the two assessments for the module:
You also find the required deliverables with their exact submission deadlines under your PATS project details. The word limits are a maximum for the main body of the report, not a target. Enough information such that a competent computer scientist can understand and reproduce the work should be given in the report, and any appendices or supplementary material (both do not count towards the word limit). More guidance and details about the coursework are in the corresponding sections above.
If you have any extenuating circumstances, Cardiff University's rules for undergraduate coursework apply (do not confuse these with the regulations for postgraduate dissertations). You can either obtain an extension or a deferral to the next possible time (usually in the resit period over the summer or the following academic year). Generally you would submit this in the two weeks before deadline.
If you do the project in the summer resit period (for any reason), you would usually work on the same project with the same supervisor and moderator. This will automatically be set up, and you will get details on deadlines, etc., after the year exam board. If the supervisor is not available, another supervisor will be found.
If you repeat the project (for any reason) during term, this will not be automatic. It will be an internal repeat of the module (external is not possible), taking you through the complete process. You must select a project/supervisor again in the autumn term to execute the project in the spring term. Still, you can agree on the same/adjusted project with the same supervisor if they are available.