Module code: COM3001

Module Overview

The project consists of a substantial written report and accompanying video presentation and software submission, completed by the student towards the end of their programme of studies. These are based on a major piece of work that involves applying material encountered in the taught component of the degree, and extending that knowledge with the student's contribution, under the guidance of a supervisor. The project lasts over both semesters, and usually involves software development, experimental or theoretical research, or a substantial analysis on a specific topic.

Module provider

Computer Science

Module Leader

DONGOL Brijesh (Computer Sci)

Number of Credits: 45

ECTS Credits: 22.5

Framework: FHEQ Level 6

Module cap (Maximum number of students): N/A

Overall student workload

Workshop Hours: 2

Independent Learning Hours: 134

Lecture Hours: 8

Tutorial Hours: 6

Module Availability

Year long

Prerequisites / Co-requisites


Module content

The project is the result of an expected 450 hrs of work. Most of this is done individually by the student, in locating and reading relevant sources, working on the technical contribution that is the main part of the project, and writing up the final report. Some time is also spent in regular discussions with the supervisor. Further details are given in the module handbook.

Assessment pattern

Assessment type Unit of assessment Weighting
Coursework FINAL REPORT 100

Alternative Assessment

Not Applicable

Assessment Strategy

The assessment strategy is designed to provide students with the opportunity to demonstrate the learning outcomes for this module.

The summative assessment for this module consists of:

·     A final project report detailing the student’s work together with a short video presentation demonstrating it. Final submission is tentatively due in week 12 of semester 2.


Formative assessment and feedback

There are 2 formative assessments for which feedback is provided: The interim discussion around week 10 of Semester 1 and the draft final report submission around week 8 of Semester 2.

As such formative feedback is given by the supervisor during regular meetings as well as on a draft version of the final report. Additional formative feedback will be provided by an examiner as the result of the interim discussion.

Module aims

  • Require students to undertake and complete a substantial piece of work at a professional level. It is the most substantial individual piece of work in the degree programme.
  •  Provide the opportunity for students to plan, organise, and implement a large piece of work over a long period of time.
  • Allow students to show inspiration for a project and follow it through to completion, whatever the level of academic achievement thus far in their degree.
  • Provide students an awareness of external factors which may affect the work of the computer professionals, including computer security, Intellectual Property and related issues, design, implementation and maintenance of trustworthy software.

Learning outcomes

Attributes Developed
1 1. Put into practice concepts and techniques studied in the undergraduate programme P
2 1. Apply scientific and software/hardware techniques to solving a problem CP
3 1. Demonstrate literacy skills, including gathering relevant references and perform critical literature review, citing references properly, and understand plagiarism and copyright KPT
4 1. Analyse the solution to evaluate the associated results C
5 1. Demonstrate the ability to time manage tasks T
6 1. Demonstrate the ability to present the project work T
7 1. Demonstrate the ability to explain the importance of professional responsibilities and the role of professional codes of conduct KP
8 1. Demonstrate an understanding of IT Regulation and compliance in practice, and the ability to evaluate the importance of information security KCPT
9 Demonstrate the ability to recognise and the ability to understand software contracts, to deal with issues related to intellectual property (IP) and the relevance of IP to software and associated materials KPT

Attributes Developed

C - Cognitive/analytical

K - Subject knowledge

T - Transferable skills

P - Professional/Practical skills

Methods of Teaching / Learning

The learning and teaching strategy is designed to:

Provide students with the knowledge, skills, and practical experience covering the module aims and learning outcomes.

The learning and teaching methods include:

·       Regular meetings with the allocated supervisor to discuss progress. (approximately 12 meetings of ½ hour each)

·       Lectures on research methods, technical writing, and presentation skills (three lectures of 2 hours)

·       Supporting lectures to provide guidance on structuring a project and report writing (four lectures of 1 hour)

·       An interim discussion early in the project cycle, to provide formative feedback on the selected topic and plan of work (one meeting of ½ hour)

·       A draft report submission towards the end of the project cycle, to provide formative feedback on the write-up

·      The project will include the preparation of a report, a video presentation of the work performed, and the submission of any software written as part of this work

              ·       All activities will be co-ordinated via SurreyLearn where detailed project guidelines and other supporting materials are available

Indicated Lecture Hours (which may also include seminars, tutorials, workshops and other contact time) are approximate and may include in-class tests where one or more of these are an assessment on the module. In-class tests are scheduled/organised separately to taught content and will be published on to student personal timetables, where they apply to taken modules, as soon as they are finalised by central administration. This will usually be after the initial publication of the teaching timetable for the relevant semester.

Reading list
Upon accessing the reading list, please search for the module using the module code: COM3001

Programmes this module appears in

Programme Semester Classification Qualifying conditions
Software Development for Business BSc (Hons)(CORE) Year-long Core Each unit of assessment must be passed at 40% to pass the module
Computer Science BSc (Hons)(CORE) Year-long Core Each unit of assessment must be passed at 40% to pass the module
Computing and Information Technology BSc (Hons)(CORE) Year-long Core Each unit of assessment must be passed at 40% to pass the module

Please note that the information detailed within this record is accurate at the time of publishing and may be subject to change. This record contains information for the most up to date version of the programme / module for the 2020/1 academic year.