Group Project

The details
Computer Science and Electronic Engineering (School of)
Colchester Campus
Postgraduate: Level 7
Monday 13 January 2020
Friday 20 March 2020
28 August 2019


Requisites for this module



Key module for

MSC G40012 Advanced Computer Science,
MSC G40024 Advanced Computer Science,
MSC G41112 Artificial Intelligence,
MSC G51512 Big Data and Text Analytics,
MSC G40912 Internet of Things,
MSC G40812 Intelligent Systems and Robotics,
MPHDG40048 Computer Science,
PHD G40048 Computer Science,
MSCIG402 Computer Science,
MSCII100 Computer Science (Integrated Masters, Including Placement Year)

Module description

This module allows students to apply their specialised knowledge to a realistic problem and experience team-based production of software.

Module aims

The aim of this module is to provide students with the opportunity to apply their specialised knowledge to a realistic problem, and gain practical experience of the processes involved in the team-based production of software.

Module learning outcomes

After completing this module each team will be expected to have:

1. Held regular group meetings and maintained a diary of their progress.
2. Defined and allocated tasks to individual members according to their skills.
3. Used available project management tools to organise their activities.
4. Produced a fully tested working implementation of their software.
5. Delivered appropriate documentation of a professional standard.
6. Given a presentation in which they described the way the project was managed, explained their design and demonstrated their final product.
7. Considered the security aspects with respect to their implemented software.

Each individual student will be expected to have contributed fully to his or her team's activities, and will be expected to be able to:

1. Describe the processes involved in the team-based production of software.
2. Explain and justify the design implementation and evaluation of their team's finished product.
3. Give an account of their individual contribution to the team's effort.

Module information

Outline Syllabus

Starting from an outline description of a realistic problem, each team is required to develop a fully implemented software solution using appropriate engineering and project management techniques. Wherever possible, teams are organised on the basis of shared interest, and the problem is designed to exercise their understanding of their area of specialised study.

Assessment is based on the documentation produced at each stage of the process, a presentation and demonstration of the final product, the effectiveness of the team's management of the project, and the understanding and contribution of each individual.

Learning and teaching methods

Lectures and project supervision


This module does not appear to have a published bibliography.

Assessment items, weightings and deadlines

Coursework / exam Description Deadline Weighting
Coursework   Project Presentation/Demonstration    20% 
Coursework   Assignment 1: Requirements Specification     20% 
Coursework   Assignment 2: Final Programming Code and Report    50% 
Coursework   Assignment 3: Personal Appraisal    10% 

Overall assessment

Coursework Exam
100% 0%


Coursework Exam
100% 0%
Module supervisor and teaching staff
Dr Manoj Thakur, email: mpthak@essex.ac.uk.
Dr Manoj Thakur, Dr Renato Amroim, Dr Anirban Chowdhury, Dr Panagiotis Kanellopoulos, Dr Jinya Su, Dr Morteza Varasteh
School Office, csee-schooloffice (non-Essex users should add @essex.ac.uk to create full e-mail address), Telephone 01206 872770



External examiner

Dr Rong Qu
The University of Nottingham
Associate Professor
Dr Marios Angelopoulos
Bournemouth University
Principal Academic
Available via Moodle
Of 6 hours, 6 (100%) hours available to students:
0 hours not recorded due to service coverage or fault;
0 hours not recorded due to opt-out by lecturer(s).


Further information

Disclaimer: The University makes every effort to ensure that this information on its Module Directory is accurate and up-to-date. Exceptionally it can be necessary to make changes, for example to programmes, modules, facilities or fees. Examples of such reasons might include a change of law or regulatory requirements, industrial action, lack of demand, departure of key personnel, change in government policy, or withdrawal/reduction of funding. Changes to modules may for example consist of variations to the content and method of delivery or assessment of modules and other services, to discontinue modules and other services and to merge or combine modules. The University will endeavour to keep such changes to a minimum, and will also keep students informed appropriately by updating our programme specifications and module directory.

The full Procedures, Rules and Regulations of the University governing how it operates are set out in the Charter, Statutes and Ordinances and in the University Regulations, Policy and Procedures.