Honours Computer Science Project CSI-6-CSP School of Engineering

Short Description

The project contributes significantly towards the final degree. Future employers may well ask you about your project, and use performance in the project as one of the most reliable guides to your potential. Requests for references often ask about the project.

The project is a level 6 double module (i.e. worth 40 credits) for the Honours degree, enabling students to demonstrate the extent of the theoretical knowledge and practical skills which they have gained through prior study and industrial internships, if any. The project is therefore a very important piece of work. It is intended to demonstrate to the examiners your ability to independently undertake and complete all the parts of a substantial piece of work.

According to the BCS 

It is expected that within an undergraduate programme, students will undertake a major computing project, normally in their final year and normally as an individual activity, giving them the opportunity to demonstrate:

• their ability to apply practical and analytical skills present in the programme as a whole
• innovation and/or creativity

• synthesis of information, ideas and practices to provide a quality solution together with an evaluation of that solution

• that their project meets a real need in a wider context
• the ability to self-manage a significant piece of work
• critical self-evaluation of the process."

The project is normally undertaken during Semester 1 and Semester 2 (“Semester-based projects”), or (for full-time top-up students) during Semester 2 and over the Summer (“Summer-based projects”).

1. AIMS OF THE MODULE

The aim of this module is to further develop and integrate all of the knowledge and skills you have acquired during your degree studies into a single major piece of work. You will experience first-hand the issues and challenges of project management, research and development.

This module brings together aspects of your previous studies into a major piece of work that you will have responsibility for at every stage. You will be guided by an academic supervisor, but a key principle is that you take responsibility for your own project. We believe that this will be to your advantage when looking for employment, and subsequently in the workplace.

1. Learning Outcome

4.1 Knowledge and Understanding

Research methods and practice appropriate to the chosen pathway Application of in-depth, subject-specific knowledge

4.2 Intellectual Skills

Critically evaluate academic literature and write structured, informed arguments

4.3 Practical Skills

Manage time and resources in order to deliver a significant piece of project work Design, plan, execute and evaluate a significant computer science related project

4.4 Transferable Skills

Sustain self-directed learning Write large formal reports

1. Assessment of the Module

Coursework 100% Project Assessment

All three components are compulsory and must be passed individually in order to pass the module. All are subject to individual resits in the case of failure.

Initial Progress Report

Submitted in week 10 of the project, this report consists of the following:

• An introduction to the project demonstrating the student has a clear grasp of the project aims, the value of the project, the scope of the project and the interpretation of the proposal the student has developed.
• A draft literature review that provides context and background for the project and provides evidence justifying the value of the project.
• A draft technical review that considers technologies, platforms and architectures that could be used to implement the project, identifying the relevance, advantages and disadvantages of them and drawing conclusions as to what is suitable for use.
• A plan of implementation, consisting of a discussion of the methodology to be used, the way in which the various tasks will be organised over the duration of the project and a look back over the first ten weeks of the project and how that time was used.

The purpose of the initial progress report is to ensure that students have made suitable progress by week 10. It is used to assess the professionalism, time management and self-organisation of the student. It is marked not by the student’s supervisor, but by their second assessor.

Final Report and Viva

The final report will be submitted at the end of the module. Students with a support plan that includes additional time or with a supported extenuating circumstances claim can submit according to the University’s late submission regulations.

The viva should take place as soon as practical following submission, and no longer than three weeks after the submission of the project. Students are expected to make themselves available during the specified period following submission. Vivas are mandatory and must be passed individually in order to pass the module.

Every attempt to hold a viva for the student will be made where the student wants to hold one outside normal working hours but this cannot be guaranteed.

Vivas may take place online or in person at the discretion of the supervisory team.

The final report is independently marked by both the supervisor and second assessor and the markers are then required to agree a final mark. The viva mark is also awarded by agreement between both markers. Where markers are unable to reach a consensus, the module co-ordinator may allocate a third marker to resolve the dispute.

Referrals

All assessment components are mandatory to pass and have individual resit opportunities in the event of failure.

In the case of the initial progress report, the resit attempt is at the end of the module and consists of a different assignment (as it would not make sense to have a progress report at the end of the module): The student is required to write a reflective commentary of the way in which they approached the execution of the project including a critical analysis of why their initial progress report was not of a satisfactory standard. The aim of this report is for the student to demonstrate that they are conscious of what went wrong in the initial stages of the project and of mitigating measures that were taken (or not) during the execution of the remainder of the project. The main criteria assessed is that the student understands the level of professionalism the project demands and what that consists of.

In the case of the Viva - another viva will be held in the resit period.

In the case of the final report the referral consists of a rewrite. This means that the student must resubmit an improved report that addresses the flaws identified by the feedback from the first submission. This rewrite can then be marked by the supervisor. It is not necessary for the rewrite to be double-marked. However, in the case of a non-submission the report submitted at the resit deadline will be double-marked as for the normal first submission.

1. FEEDBACK

Feedback on the initial progress report will be provided within 15 working days of submission of work to your supervisor. General feedback on draft work can be obtained from the supervisor on a regular basis. Final marks will not be released prior to the publication of all module marks following the examination boards at which the marks are ratified.

1. INTRODUCTION TO STUDYING THE MODULE

7.1 Overview of the Main Content

As an individual piece of work that is of major importance to the degree and subsequent employment, the emphasis is on both process and content.

Process will be developed primarily within your one-to-one supervisory support sessions. You are expected to manage this major piece of work by yourself, with the aid of the support provided. You will be required to plan, monitor and critically evaluate your progress, and to set and achieve a series of milestones throughout your project.

Content will be presented and evidenced via the project dissertation, backed up by a logbook and/or online reporting. The key areas we will look for are:

• Establishment of the problem, typically through the introductory section of the dissertation
• Relevant research and synthesis of both primary and secondary sources
• Solution of the problem with appropriate use of methodologies
• Summarising of the project at various levels, such as the abstract and conclusions
• Appropriate attribution and referencing of sources (we are especially looking to see that you make appropriate use of your sources)
• Demonstration and critique of project management.

7.2 Overview of Types of Classes

Given the individualistic nature of the final year project, the primary mode of learning is through self-study and self-motivated development under the guidance of your project supervisor, with additional support available from the project co-ordinator during the project workshop sessions.

7.3 Importance of Student Self-Managed Learning Time

Effective self-motivation and self-management are vital for the project. Students are expected to combine theory and practice in the planning, development and successful delivery of the project and its associated deliverables. It is your responsibility to determine what is required for this, to plan your time as appropriate in relation to the goals of your project, and to deliver on time.

7.4 Employability

This module develops skills that any employer would find valuable, and furthermore employers frequently tell us that they regard achievement in the project as a good indicator of a graduate's suitability for employment. In addition, we stress independent (but supported) learning in this module, as this is valued highly. Graduates who work in the US for example have reported that this has given them an edge compared to US graduates, who typically work in a much more prescribed way on their projects.

1. THE PROGRAMME OF TEACHING, LEARNING AND ASSESSMENT

Guidance will come primarily from your project supervisor. You will typically meet – or at least be in contact with – your supervisor on a bi-weekly basis to discuss your progress to date and next steps. Your meetings and general progress should also be recorded and monitored via a logbook and/or online reporting.

You are encouraged to make use of the wide range of support resources available and to take responsibility for your project from the outset. This encompasses problem definition, project planning, specification, research, development, analysis, reflection and presentation.

Submission Deadlines

The submission deadline for projects undertaken during Semester 1 and Semester 2 will be as follows:

Semester 1 & Semester 2 (Semester-based projects): The submission deadline for the initial progress report will be the end of Week 10 of Semester 1 and the submission deadline for the final dissertation will be the end of Week 11 of Semester 2.

The submission deadline for (full-time top-up) projects undertaken during Semester 2 and over theSummer will be as follows:

Semester 2 & Summer (Summer-based projects): The submission deadline for the partial draft will be the end of Week 10 of Semester 2 and the submission deadline for the final dissertation will be in the summer following the end of Semester 2 teaching.

In both cases students have a nominal 25 weeks of from the start of the project to the final submission (this excludes vacation weeks for semester-based projects, but includes them for summer-based projects, which are carried out during what would otherwise be vacation as part of the one-calendar year top-up course structure).

The viva presentation will take place in the three weeks immediately following submission, unless logistical reasons require other arrangements to be made. See the “Assessment” section of this document for more information about the arrangement of the viva.

Viva/demo

The viva/demo is intended to be a question and answer session in which the student has an opportunity to demonstrate their knowledge about the work they have submitted. It serves three main purposes:

1. it enables the supervisor and (more importantly) the second assessor to get a clearer picture of what has been done than they might be able to get just by reading the dissertation
2. it enables the supervisor and the second assessor to satisfy themselves that the work submitted is indeed the student's own work
3. it enables the student to practice presenting their work within a formalised setting, which is something they may need during future interview sessions when applying for jobs.

1. STUDENT EVALUATION

The student experience varies greatly depending on the project chosen, the student’s relationship with their academic supervisor, etc. Therefore it is inappropriate to evaluate the student experience in the same way as for other taught modules.

1. LEARNING RESOURCES

Week 1: Contact supervisors to proactively make choice, propose own project idea.

Week 2: Supervisor allocation for majority of students.

Week 3: Officially fix your project proposal and supervisor. Arrange schedule to meet with your supervisor. Set date and time for Viva presentation at end of project. Get to grips with what your project consists of. Establish scope of work. Write an introduction that demonstrates you have achieved this.

Carry out background research into the subject area and write this up as a referenced literature review.

Carry out a review of possible technologies you might use and write it up with a justified selection of what you think you will use.

Make a plan for how you are going to accomplish your goals and identify an appropriate methodology that you can adapt for your development work, and write all this up.

Establish the formal requirements for the development work.

Install all required development tools and environments and create cloud accounts etc. as required, carry out initial experiments to use these tools and platforms and begin proof-of-concept coding experiments.

Week 10

Submit Initial Progress Report consisting of draft chapters for: Introduction, Literature and Technical Review, and a plan for methodology and development.

Assessment Requirements

This module is a Level-6 double module (40 credits) requiring you to plan, execute and report a substantial, independent computing project over the academic year. The assessment is 100% coursework and has three compulsory components that must each be passed:

1. Initial Progress Report (week 10) : Draft Introduction, Literature Review, Technical Review (technologies/platforms/architectures), and Implementation Plan (methodology, task breakdown, reflection on first 10 weeks). Marked by second assessor.

2. Final Report / Dissertation (end of module) : Full project write-up showing problem definition, research, design, implementation, evaluation, conclusions and appropriate referencing. Independently double-marked.

3. Viva / Demo (within 3 weeks of submission) : Oral examination to validate ownership, clarify technical details, and defend conclusions. Must be passed.

Key administrative & process requirements:

• Projects run Semester-based (S1+S2) or Summer-based (S2+Summer) with nominal 25 weeks.

• Regular supervised meetings (bi-weekly recommended) and a logbook/online progress record are expected.

• All work must demonstrate: independent project management, applied technical and analytical skills, innovation/creativity, synthesis of theory and practice, and critical self-evaluation.

• Resit provisions exist for each component (reflective commentary for progress report resit; viva resit; rewrite for final report resit).

• Feedback timelines: supervisor feedback within 15 working days for the initial report; final marks published after exam board ratification.

How the Academic Mentor Guided the Student

Below is the practical, sequential way an academic mentor typically supports a student to meet the brief : from project start through to viva.

Step 1 : Clarify the Brief & Learning Outcomes (Week 1)

• Mentor reviews the module aims (project demonstrates integration of degree knowledge, project management, research and development).

• Confirm assessment components, deadlines, marking criteria and resit rules so the student understands pass/fail stakes.

Step 2 : Topic Selection & Scope Definition (Weeks 1–3)

• Mentor helps refine an idea into a feasible project: define problem statement, objectives, and success criteria.

• Coach on scope control: ensure the project is substantial but achievable within 25 weeks.

Step 3 : Research Plan & Literature Review (Weeks 3–6)

• Mentor demonstrates how to locate, evaluate and synthesise primary/secondary sources.

• Student drafts a literature review that establishes context, gaps and justification for the chosen solution. Mentor critiques for depth and relevance.

Step 4 : Technical Review & Tooling Choice (Weeks 4–7)

• Mentor guides a technical survey: platforms, architectures, frameworks, libraries and trade-offs (advantages/disadvantages).

• Together they select the technologies best aligned with project aims and constraints (performance, cost, deployment).

Step 5 : Methodology & Implementation Plan (Weeks 6–9)

• Mentor advises on an appropriate methodology (e.g., Agile iterations, prototyping, experimental evaluation).

• Help create a detailed implementation schedule, milestones and risk log. Student prepares the Initial Progress Report draft.

Step 6 : Initial Progress Report Submission (Week 10)

• Mentor reviews and tightens the draft (Intro, literature, technical review, plan) ensuring clarity of aims and evidence of progress.

• Second assessor marks this report : mentor prepares the student for feedback and any immediate adjustments.

Step 7 : Development, Testing & Logging (Weeks 11–Final Submission)

• Mentor supports iterative development: code reviews, experiment design, data collection, evaluation methods.

• Emphasises maintaining the logbook/online progress updates to demonstrate professional project management.

Step 8 : Final Write-up & Report Refinement (Final Weeks)

• Mentor provides focused feedback on structure: clear abstract, methods, results, evaluation, limitations and conclusions.

• Reviews referencing, appendix material (tests, datasets), and ensures the report meets formal requirements.

Step 9 : Viva Preparation (2–3 weeks before submission)

• Mentor conducts mock vivas, helps prepare demo scripts, slides and a concise “elevator pitch” of your contribution.

• Practices Q&A on methodology, technical choices, validation and ethical considerations.

Step 10 : Submission, Viva & Post-Submission Tasks

• Mentor supports submission logistics and attends (if appropriate) viva scheduling.

• Post-viva, mentor helps interpret feedback and prepare for any resit/rewrite if needed.

Final Outcome

By following this supervised process the student delivered:

• A week-10 Initial Progress Report demonstrating a clear problem definition, justified literature review, practical technical choices and a realistic implementation plan.

• A functioning project artefact (software prototype, system, experiment, or comparable deliverable) implemented according to the plan, with testing and evaluation results.

• A final dissertation that synthesised research, methodology, implementation and critical evaluation, demonstrating subject-specific depth.

• A successful viva/demo showcasing understanding and ownership of the work (or a clear remediation path if a resit was required).

Learning Objectives Covered

The project explicitly developed and assessed the following knowledge and skills:

4.1 Knowledge & Understanding

• Applied research methods and in-depth technical knowledge relevant to the chosen computing pathway.

4.2 Intellectual Skills

• Critical evaluation of academic literature and construction of structured, evidence-based arguments.

4.3 Practical Skills

• Time and resource management to deliver a significant technical project.

• Designing, planning, executing and evaluating a substantive computer-science related solution.

4.4 Transferable Skills

• Sustained self-directed learning and professional project management.

• Producing a large formal report and developing presentation skills via the viva.

• Problem solving, critical reflection and the ability to justify technical choices to expert assessors.

Get Your Reference Sample

Looking for clarity before you start writing your own assignment? You can download the sample solution provided above and use it as a study guide to understand structure, formatting, and academic expectations. This reference file is meant to support your learning, not replace your own academic work.

Please remember: submitting the sample as your own may lead to plagiarism penalties. Universities use advanced detection tools, and using someone else’s work without modification can put your grades and academic integrity at risk. Always use sample files only for research and guidance.

If you need a completely original, high-quality assignment tailored to your topic and university guidelines, our expert academic writers are here to help. We create custom-written assignments from scratch, ensuring full originality, proper referencing, and adherence to your instructions. Every solution is plagiarism-checked and delivered on time, helping you submit confidently without compromising academic honesty.

Why Choose a Fresh, Custom-Written Solution?
• 100 percent original and plagiarism-free work
• Written by qualified subject-matter experts
• Structured according to your university’s marking criteria
• Error-free content with accurate referencing
• Delivered on deadline with unlimited revisions support

Get the guidance you need with a sample file or secure a brand-new assignment crafted just for you.

Download Sample Solution     Order Fresh Assignment