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
For ongoing human participation invitations to support the projects see survey.
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.
Projects Involving Human Participants/User Surveys: Please be aware that projects requiring user participation, surveys, or human evaluation are challenging to execute. The School will not distribute student research surveys via mass e-mails to the student body. Projects that rely on widespread user participation are considered infeasible unless you have your own independent method of distribution or an established group of participants. See CM3203 Ethics and Other Issues for more details.
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:
Disseminating Research Surveys: Following best-practice guidance from the Learning and Teaching Academy (LTA), the School will not disseminate student research surveys to the wider student body through official School channels (e.g., mass e-mail lists). This policy is in place to prevent survey fatigue and protect engagement with key institutional surveys like the NSS and Module Enhancements. If your project requires survey data or user testing, you are responsible for your own participant recruitment. Please consider these alternative methods include:
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 use of AI tools is permitted in this module. This includes, for example, large language models, code assistants, generative tools, search/summarisation tools, and other assistive or automated techniques. These tools should be treated in the same way as any other tool, software package, library, service, dataset, or instrument used in the project: if their use is material to the work, it should be appropriate, justified, and acknowledged. You remain responsible for everything you submit, and get the marks for what you have done yourself. This includes the correctness, quality, originality, legality, ethics, and presentation of the work, regardless of which tools were used to help produce it.
Where AI or other tools play a material role in the project, you should:
Do not cite an AI tool instead of the underlying scholarly or technical source where the underlying source is what supports a claim. Do not upload confidential, personal, sensitive, restricted, or otherwise protected material to external tools unless this is permitted by the project's ethics, legal, licensing, and data-protection requirements.
The project runs in the spring term from week 1 to week 12. Regular supervisor meetings will take place during this period and are arranged individually with your supervisor. As the student is responsible for managing their own project, they must also ensure that these meetings occur as agreed. On average, supervision time is about 30 minutes per teaching week, but this can be distributed flexibly across the 12 weeks and may include group sessions where appropriate. If the supervisor has not replied within about one week, or the agreed meeting schedule breaks down, the student must email the project coordinator and include their previous correspondence with the supervisor.
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.
Supervisors can give formative feedback on an outline or a near-complete report draft, and answer specific questions. They will not suggest likely marks or predict outcomes, and they are not expected to read every line. They may scan for structural or scope problems and comment on whether an outline or table of contents looks suitable.
Ask for written comments once or twice—for example at outline stage and again on a late draft—not on many successive versions. Allow at least about a week for a reply and send requests well before deadlines; see the initial plan and final report pages for related guidance.
We provide an optional skill for formative help with CM3203 project work, the initial plan and the final report. It can help with, for example:
This skill is provided only as an experimental support tool to help you improve your work and understand the guide. It is:
Official requirements and decisions come only from the CM3203 guide, PATS, and the relevant module staff. Even when using this skill, you should still check the current guide and PATS yourself, especially for deadlines, submission requirements, and case-specific issues, and you should discuss your work with your supervisor and the project coordinator where appropriate.
Like any other entity, system, or tool, this skill may be useful, but it may also be incomplete, misleading, or wrong. You must therefore not rely on it without checking, testing, and verifying its outputs yourself, just as you should critically evaluate any advice, feedback, or information from any other source — something a good AI would also try to do.
Download: CM3203 Project Help Skill V0.0.2
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.