 |
| STUDENTS
> Group Project
|
Group Project
Note:
Whilst every effort is made to keep the syllabus and assessment records correct
for this course, the precise details must be checked with the lecturer(s).
| Code: | 3092 |
| Year: | 3 |
| Prerequisites: | Successful completion of years 1 and 2 of the Computer Science programme |
| Term: | 1 and 2 |
| Taught By: | Projects co-ordinator = Licia Capra (100%)
|
| Aims: | To put students in a situation where they have to work within a group
to develop a prototype implementation of a software system from an initial
specification given to them by a client. To develop group working
skills and provide the opportunity to work on the development of a larger
application. |
| Learning Outcomes: | To be able to: work as a member of a team developing a
software application, plan and coordinate development activities, produce
deliverables (software and reports) on time, make realistic work commitments,
present and communicate the work done effectively and perform critical
self-assessment. |
Content:
| Course Introduction - Stipulation of Contract (Week 3 - Term 1) | Students are split into project groups with 6-8 members, each
group having a supervisor who is a member of academic staff. The supervisor
provides support and guidance; sometimes it may also act as the customer. Project groups
are selected by the course organiser, with students having no choice.
Supervisors select the project ideas. The project runs continuously through
both teaching terms with the group responsible for organising themselves, with
advice from their supervisor. Groups are expected to meet with their
supervisor once per week. A series of deliverable deadlines are set and must be met by
the project groups. A group diary needs to be kept to record the progress of
the group, including the minutes of meetings held.
Project Management - First output: agreed and signed contract.
|
| Past project assessment (end of October) - No deliverable required | The first group activity is to perform an assessment of the
reports delivered by a group project from a previous year. This starts the
development of critical assessment skills and also provides an example of what
project reports and the results of a project look like. |
| Deliverable 1 - Interim Report (Week 7 - Term 1) | The first stage of a project, during term 1, is to identify a
feasible set of user requirements, perform analysis and start
prototyping.
The Interim report outlines the project, documents the requirements and background research,
illustrate the design, and provides a plan for completing the project. |
| Deliverable 2 - Main Report, including Executive Summary and Group Diary (Week 6 - Term 2) | The end of term 1 and up until week 8 of term 2 are devoted to
the main design and implementation effort, with the aim of producing a working
prototype.
The main report documents the results of the project, focusing
on design, implementation and testing. A user manual should be included. A 1
page is required (Executive Summary) to provide a concise description of the
project and its results. The group diary, including meeting minutes is also
included. |
| Deliverable 3 - Personal Report (Week 6 - Term 2) | Each student is required to submit a personal report giving a)
an assessment of the structure, organisation and progress of the project
group, b) an assessment of the project results and the effectiveness of the
group as a whole, c) an assessment of each group member, d) an assessment of
their own role, including a summary of what they contributed.
|
| Deliverable 4 - Presentation (Week 7 of Term 2) | Each group is required to give a 15 minute formal presentation
of their work, making use of suitable AV equipment. The presentation should
explain what the project is about, what were the challenges and give an
overview of the design and implementation approach. A demonstration of the
working prototype should be included. |
| Deliverable 5 - Weekly Reports (every week during term time) | Each student is required to email their supervisor once per
week reporting on the work done towards the project. Supervisors keep the
reports to help keep a record of individual progress.
|
Method of Instruction:
Group working with support from tutorials held by the group
supervisor.
Two workshops organised in collaboration with Goldman Sachs that focus on: 'team building' (week 3 - Term 1) and 'presentation skills' (week 1 - Term 2).
Assessment:
The course has the following assessment components:
- Reports
(150 hours, 100%)
To pass this course, students must:
- Pass the Coursework (40% or more)
Resources:
Books, papers, manuals etc. relevant to the project.
Course homepage
|
|
+44 (0)20 7679 7214 - Copyright © 1999-2007
UCL
