CS351-30 Computer Systems Engineering Project
Introductory description
The third year project is an extended, individual piece of work which forms a core element of the Computer Systems Engineering degree. Students choose a topic and find a supervisor in the summer term of their second year.
This module is not available to students from other departments.
Module aims
To provide experience of undertaking a significant individual research or development exercise from conception through to design, execution and delivery.
Outline syllabus
This is an indicative module outline only to give an indication of the sort of topics that may be covered. Actual sessions held may differ.
Students select a project during the third term of their second year by submitting an outline of the proposed project and finding an academic member of staff to supervise it. The Project Specification, which outlines the project plan, is submitted during the first term. The written Progress Report on the current state of the project is submitted early in the second term for 15% credit (combined with the Project Specification). The Final Report, which is a detailed written report of the project, is submitted during the Easter break, with a plan submitted to the supervisor near the end of the second term. The student will take part in the Viva, which is a short presentation and extended question and answer session, early in the third term. The Final Report and Viva, together, are worth 75% of the module credit. The student will submit a short document, worth 10%, describing how they have managed their project, at the same time as the Final Report. This module is primarily not a taught module, but a major design and development exercise for the student carried out under supervision.
Learning outcomes
By the end of the module, students should be able to:
- - Plan and manage a significant individual project, including detailed consideration of resources, health and safety, professional ethics, time management and professional issues
- - Build a computer hardware and/or software system from design to documentation or to carry out a substantial research project from methodology to conclusions
- - Present their work orally, with appropriate use of audio- visual aids and interactive demonstrations, and respond to questions effectively
- - Produce a substantial technical report
Indicative reading list
Please see Talis Aspire link for most up to date list.
View reading list on Talis Aspire
Research element
The entire project may be based around undertaking a significant research exercise from conception through to design, execution and delivery.
Subject specific skills
The individual project involves consolidating, combining and applying a wide variety of subject specific skills gained in the rest of the degree course so far.
Transferable skills
- Technical - Technological competence and staying current with knowledge
- Communication - Verbal, listening, writing, technical communication skills, using different medium for communicating
- Critical Thinking - Problem-solving, analysis of possible solutions etc
- Multitasking - Soft skills such as time management, organization skills etc
- Creativity - Ability to harness creative ideas and turn them into tangible and strategic products/solutions
Teaching split
| Provider | Weighting |
|---|---|
| Computer Science | 50% |
| School of Engineering | 50% |
Study time
| Type | Required | Optional |
|---|---|---|
| Lectures | 8 sessions of 1 hour (3%) | |
| Seminars | 2 sessions of 1 hour (1%) | |
| Project supervision | 20 sessions of 30 minutes (3%) | |
| Practical classes | (0%) | 2 sessions of 2 hours |
| Online learning (independent) | 2 sessions of 1 hour (1%) | |
| Private study | 278 hours (93%) | |
| Total | 300 hours |
Private study description
Private study and independent learning in this module includes:
- Research into the subject area of the project, and into available existing solutions.
- Planning and managing own work.
- Preparing for and learning from supervision meetings.
- Designing, solving, programming, testing and evaluating own software artefacts or research outcomes.
- Preparation of the written reports and the Viva.
- Reflecting on feedback received on the Progress Report and the Final Report Plan.
Other activity description
Evaluation Day.
Costs
No further costs have been identified for this module.
You do not need to pass all assessment components to pass the module.
Students can register for this module without taking any assessment.
Assessment group A6
| Weighting | Study time | Eligible for self-certification | |
|---|---|---|---|
| Progress Report | 15% | No | |
|
Progress report on the project, with a maximum length of 4,000 words. |
|||
| Final Report & Viva | 75% | No | |
|
Final Report expected length: 8,000 words. Final Report maximum length: 10,000 words. Viva duration: 45 minutes. |
|||
| Project Management | 10% | Yes (extension) | |
|
A short written report describing how the student has managed their project. Maximum length: 1,000 words. |
|||
Assessment group R5
| Weighting | Study time | Eligible for self-certification | |
|---|---|---|---|
| Resit Final Report (including Project Management) & Viva | 100% | No | |
|
Final Report expected length: 9,000 words. Final Report maximum length: 11,000 words. In addition to the content which is expected to be included in the non-resit version of the Final Report, the Resit Final Report should also include a discussion of how the student has managed their project (Project Management). Viva duration: 45 minutes. |
|||
Feedback on assessment
Project Specification: Oral feedback from supervisor within two weeks of submission.
Progress Report: Feedback via Tabula within 20 university working days.
Final Report & Viva: Feedback via Tabula on or before end-of-year mark release.
Project Management: Feedback via Tabula within 20 university working days.
Pre-requisites
This module is not available to students from other departments.
Courses
This module is Core for:
- Year 3 of UCSA-G406 Undergraduate Computer Systems Engineering
- Year 3 of UCSA-G408 Undergraduate Computer Systems Engineering
- Year 4 of UCSA-G407 Undergraduate Computer Systems Engineering (with Intercalated Year)
- Year 4 of UCSA-G409 Undergraduate Computer Systems Engineering (with Intercalated Year)