CS407 - The group project is intended to give students experience of team project work, similar to that which might be expected of them in a working environment, demanding management and problem-solving skills as well as individual initiative.
The project will be in response to the needs of a "customer" who will normally be an industrial partner, or may alternatively be an academic, and will be closely involved in the specification and running of the project. The themes for such projects will offer more scope for interdisciplinary and collaborative activities than a typical third year project, requiring a mature knowledge of computer science and its applications.
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.
The topics of the group projects are up to students and their supervisors and may be drawn from any area in Computer Science. Topics of the lectures focus on key skills in software engineering, such as:
Version control
Testing and continuous integration
Build systems and package management
Containerisation/development
Writing for Computer Science
These topics will be illustrated using relevant, current technologies.
By the end of the module, students should be able to:
Please see Talis Aspire link for most up to date list.
View reading list on Talis Aspire
Some groups of students may work on small research projects.
Students will learn how to engineer complex software systems or conduct research projects according to the requirements of a customer.
Technical skills, communication skills, critical thinking, multitasking
| Type | Required |
|---|---|
| Lectures | 5 sessions of 1 hour (2%) |
| Project supervision | 20 sessions of 1 hour (7%) |
| Private study | 275 hours (92%) |
| Total | 300 hours |
Private study consists of:
Researching topic
Developing software
Writing reports
Preparing presentations
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.
| Weighting | Study time | Eligible for self-certification | |
|---|---|---|---|
| Progress Presentation | 20% | No | |
|
Group presentation to assessors using overhead slides and optionally a demo. All group members to take part in presentation. |
|||
| Group Report | 60% | No | |
|
The Group Report is jointly authored by the members of the group, is typically of length 30,000 words (excluding appendices), and counts for 60% of the assessment. Its purpose is to document the process of delivering the agreed software, from both a technical and a process management standpoint. The report should demonstrate that the group has applied their skills in the software development process, and also that they have worked together effectively as a team. |
|||
| Individual Report | 10% | No | |
|
The individual report is a piece of reflective writing which allows each group member to discuss their own contribution to the project, and what lessons they have learned from the process. |
|||
| Final Presentation | 10% | No | |
|
The final presentation allows the group to present their completed work to their assessors as well as to an audience, and allows members of the audience to question members of the group about their work. Depending on the type of project, the group will be expected to demonstrate their working software or present a poster of their research results. |
|||
| Weighting | Study time | Eligible for self-certification | |
|---|---|---|---|
| Resit report on group project management | 50% | No | |
|
A report consisting of
|
|||
| Viva on Group Projects | 50% | No | |
|
Following on from the Written Report, a discussion with two assessors on the first attempt in CS407 (including technical aspects) as well as general insights into software development project management. |
|||
Individual feedback via Tabula and group feedback via email
This module is Core for: