PROFESSIONAL PROJECT - 2022/3
Module code: COM3001
In light of the Covid-19 pandemic the University has revised its courses to incorporate the ‘Hybrid Learning Experience’ in a departure from previous academic years and previously published information. The University has changed the delivery (and in some cases the content) of its programmes. Further information on the general principles of hybrid learning can be found at: Hybrid learning experience | University of Surrey.
We have updated key module information regarding the pattern of assessment and overall student workload to inform student module choices. We are currently working on bringing remaining published information up to date to reflect current practice in time for the start of the academic year 2021/22.
This means that some information within the programme and module catalogue will be subject to change. Current students are invited to contact their Programme Leader or Academic Hive with any questions relating to the information available.
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.
DONGOL Brijesh (Computer Sci)
Number of Credits: 45
ECTS Credits: 22.5
Framework: FHEQ Level 6
JACs code: I100
Module cap (Maximum number of students): N/A
Overall student workload
Independent Learning Hours: 428
Guided Learning: 12
Captured Content: 10
Prerequisites / Co-requisites
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 type||Unit of assessment||Weighting|
|Coursework||FINAL YEAR PROJECT||100|
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.
- 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.
|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|
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.
Upon accessing the reading list, please search for the module using the module code: COM3001
Programmes this module appears in
|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 2022/3 academic year.