CS3072 Computer Science Project

Study Guide for 2011/12

MODULE DETAILS

Module leader FYP Team Leader: Prof. Panos Louvieris

Department Information Systems and Computing
Credits 40
Other staff FYP Team: Dr Steve Counsell, Prof. Tony Elliman, Dr Mark Perry and
Dr Shengxiang Yang, Mrs Leanne Hunt, Ms Zaib Ahmed.
Contact and private study time Lectures 11 hours
Supervisor sessions 18 hours
Private Study 371 hours
Total 400 hours
Assessment Method Proportion of marks
Coursework 100%

ACCESS TO SUPPORT MATERIAL AND ADDITIONAL INFORMATION

The majority of the teaching, learning and support material is provided electronically via the University’s
Blackboard Learn system.

Note that the details provided in this study guide are based on the formal module syllabus for this module
which sets out the agreed content, learning outcomes, assessment and teaching methods. Module syllabus
and scheme of studies documents for your programme of study can be found by looking at Course and
Module Data held by Registry.

INTRODUCTION/AIMS/BACKGROUND
The aim of this module is to:

enable students to demonstrate an integrated approach to the topics covered in the degree
programme. In particular:

• acquire analytical and problem-solving skills

• recognise and define a problem to be explored and the work to be completed through
experiential rather than passive learning
• develop skills for independent research and development
• develop the ability to describe and solve a problem in such a way that it can be measured
• adapt and apply academic knowledge and skills in the investigation and solution of a
problem

Some of these aims relate to high-level concepts, such as independent inquiry, whilst others are lower level,
more practical concepts, such as report writing. Nevertheless they all have a part to play.

The final year project is an opportunity for you to demonstrate your ability to tackle a substantial problem.
Within the project you will investigate the relevant literature and make informed decisions regarding the
approach through which the problem is solved. This process, of considering alternative approaches and
deciding which one to apply is an integral part of the project. Thus it is vital that your final report reflects
this process by discussing the choices made rather than simply outlining your solution.

A project is a 40-credit core module, and is a component in all undergraduate programmes. This module
brings together knowledge and skills accumulated throughout the undergraduate programme and
provides an opportunity to research a topic in your discipline in depth. It will require you to work under your
own initiative (and the guidance of a supervisor) and to use and demonstrate your analytical, critical and
development skills in the context of a problem solving project.

Updated 26 September 2011 Page 1 of 6

A Computer Science project requires the development of non-trivial software solution to a practical
problem and, in general, this may be performed in two ways:

• It may be a project where a solution is implemented via the writing of program code in a traditional
programming language.
• It may also concentrate on earlier elements of the systems development life-cycle, such as
requirements analysis, systems analysis, and design, although there is a specific requirement that
you develop program code. For example, the major concentration might be on analysis and design
with only a part of the design being actually implemented. Or it might be a project where design
and implementation is involved but the implementation is achieved by use of components/fourth
generation system/package/prototype/etc, However, it must involve more than component reuse,
or automatically generated code/scripts.

It is important to note that:

1. If you do not meet the criteria for a pass grade, you will not be eligible for consideration for the
award of an Honours degree.
2. There are three different types of project, one for those enrolled on a BSc Information Systems
degree, another for those doing a BSc Network Computing degree, and this one, for those doing a
BSc Computer Science degree. There are naturally different requirements for each, but it is
important to be aware that the essential difference is in the requirements for software
development. A separate study guide exists for each type of project. Make sure you are reading
the correct one.
3. For the award of BSc Computer Science with a specialism the topic chosen for the CS3072 project
must be drawn from the relevant specialism. These are defined as:
• Artificial Intelligence: Software artefacts (or programs) that display apparently intelligent
behaviour (including machine learning paradigms) applied to the production of innovative
and useful artefacts.
• Digital Media and Games: Software artefacts targeted at the entertainment market and
their development and implementation.
• Network Computing: The ways distributed information systems work and their
development and implementation.
• Software Engineering: The management, organisation and execution of large-scale
software design and development activities including reuse and integration.

Ethical Approval
The university requires that all project work follows ethical procedures and conforms to ethical standards.
Consequently you are required to discuss the ethical aspects of your proposed work with your dissertation
project supervisor and under their guidance complete the ethics approval process. This is a two-stage
process:

Stage 1 – The first stage of the process takes place as part of Task 1 - planning your project. You must
determine whether you need the University’s permission to involve other people in your project and, if you
do, you must also determine whether it is a high risk project. These decisions must be confirmed by your
supervisor.

ALL students need to complete DISC ethics checklist. If you have answered yes to any of the checklist points,
then you will need ethical approval for your project activity. In this case you also need to complete the
questions on pages 1 and 2 of the DISC ethics approval short form. These documents must then be
submitted with your Task 1 project plan by 14th November 2011. If you miss this deadline you will not be
permitted to continue any other FYP work until you have submitted the required ethics documents.

Stage 2 – All students who need ethical approval must prepare full details of their investigation –
information sheets, questionnaires, interview agendas, etc. – for assessment. Your supervisor will tell you
whether your proposed work is a high or low risk. Low risk projects need only complete the rest of the DISC
ethics approval short form but high risk projects must complete the full ethics approval form.

Once the form has been completed it must be submitted, together with all the associated information, for
assessment. Low-risk activities are assessed by your supervisor but high-risk activities will be assessed by the

Updated 26 September 2011 Page 2 of 6

SISCM or University research ethics committee. The deadline for submitting this documentation to the
ethics committee is the 16th December 2011.

Once the assessments have been completed, the ethics committee will send you a formal approval letter.
Once you have received the formal ethics approval letter, you may start your data collection. You may not
carry out any activity that involves other people in your project before you receive this letter. This
process is time consuming and you may be asked to rewrite some of the documents. If you need to
undertake systems analysis tasks with other people before January 2012 you will need to get approval
quickly. You can’t wait until the 16th December deadline to submit your request for approval.

More detailed information on the ethics approval process can be obtained from the “Research Ethics”
section of Blackboard Learn.

LEARNING OUTCOMES
Whatever module or programme of study you are studying for at Brunel University, there are learning
outcomes that you must meet/achieve in order to be awarded the credits, which comprise the module and
programme of study. In order to get a pass grade (D- or above) in this module, you must meet these
learning outcomes below, that is, you must demonstrate ability to:
1. Demonstrate problem solving skills that involve model building and analysis, applying both
theoretical and empirical knowledge to make choices and find solutions.
2. Specify, design, code, modify and test a non-trivial software solution in a contemporary
programming paradigm and language using appropriate commercial grade development
environments and tools.
3. Implement useful software systems – that is satisfy the needs of their key stakeholders.
4. Develop good communication skills that would enable them to communicate clearly with clients,
managers, and technical colleagues.

The project will also allow you to demonstrate ethical awareness in accordance with the British Computer
Society guidelines for professional software development practice. More detailed information on these
requirements is provided in the planning your time section of this study guide.

METHOD OF TEACHING
The essential core concepts and logistics of conducting a large piece of project-based coursework will be
delivered through formal lectures. You will also have access to a design and programming clinic for help
with technical issues from week 6 onwards in SJ123.

Your project is a third of your final year programme – you should be spending nearly two days a week on
project work. The department has assigned Friday as “project day” in the level 3 timetable. SJ123 is reserved
all day for level 3 project students, the project lectures and the design and programming clinic all take place
on a Friday. We have tried to minimise other activity on a Friday but unfortunately, one or two things could
not be scheduled earlier in the week.

The on-going guidance, formative feedback and tailored direction will be offered through weekly
supervisory sessions. You are entitled to the following specific support actions from your supervisor:
• A scheduled time slot for group or individual project meetings during term time.
• Read and comment on at least one version of Task 1 before submission.
• Review structure of complete draft of the Project Report and at least one chapter in detail.
• A reply to emails within 3 working days (unless illness or agreed absence prevents them).
• Explain the assessment criteria to you.

It is up to the supervisor’s discretion if they wish to complement or augment these requirements.

Updated 26 September 2011 Page 3 of 6

Obtaining a Supervisor
Students are expected to secure their own supervisors. This consists of a four-stage process as indicated
below. In the event that a student is unsuccessful in this process, the FYP team will assign a suitable
member of staff to supervise that student.
Stage 1: Staff advertise proposed projects, which students can access on Blackboard Learn.
Stage 2: Students approach staff to discuss either projects that have been advertised by staff on
Blackboard Learn or project ideas that the student is proposing.
Stage 3: Staff invite students to be their supervisees.
Stage 4: Students accept staff invitations

Record of Attendance
Once you have secured a supervisor you should have weekly meeting with them right through to the end of
the second term. Your attendance at meetings with your supervisor will be recorded in the same as it was
for the group projects at level 1 and 2. If, for any reason, you cannot attend a scheduled meeting you should
let you supervisor know in advance of the meeting.

LECTURE SEMINAR PROGRAMME

Formal lectures will be held in selected weeks in terms 1 and 2 as indicated below:

Autumn Term
Weeks 1 to 6 will address project planning issues such as: Project Definition, Literature Research Skills,
Project Management, Ethics and Methodology (Software Development, Surveys and Interviews)
Note: Week 7 is Effective Learning Week
Weeks 7 and 8 will address more specific project execution methods (Data Collection and Analysis and
Practical Software Implementation).

Spring Term
Weeks 9-11 will address issues around finishing off your project such as Evaluation and Testing, Plagiarism,
Communication Skills and Critical Thinking.
Note: Week 21 is Effective Learning Week

READING LIST
You will be expected to use the library resources to define your own reading material that is pertinent to the
research that you will carry out. Your supervisor will be able to assist you in recommending sources.

Supplementary Reading
Berndtsson, M., Jorgen Hansson, B. Olsson, B. Lundell (2002) Planning and Implementing your Final Year
Project - with Success! A Guide for Students in Computer Science and Information Systems.
Springer.
Coolican, H. (2004) Research Methods and Statistics in Psychology (4th Ed). Hodder & Stoughton.
Cornford, T. and Smithson, S. (2005) Project Research in Information Systems - a Student’s Guide. 2nd
Edition. London: Macmillan.
Cottrell, S. (2005) Critical Thinking Skills: Developing Effective Analysis and Argument, Palgrave Macmillan
Cottrell, S. (2008) The Study Skills Handbook, 3rd Edition, Palgrave Macmillan
Dawson, C. W. (2006) Projects in Computing and Information Systems: A Student's Guide, Addison Wesley.
Dawson C.W. (2005) The Essence of Computing Projects; A Student’s Guide. Harlow: Prentice Hall.
Oates, B.J. (2005) Researching Information Systems And Computing. Sage, London.
Phillips, J. (2004) IT Project Management: On Track from Start to Finish, 2nd Edition. McGraw-Hill Osborne
Media.
Saunders, M., Lewis, P. and Thornhill, A. (2003) Research Methods for Business Students. London: Pitman,
3rd edition
Weaver, P. (2004) Success in Your Project: A Guide to Student System Development Projects. FT Prentice
Hall.
Wysocki, R.K. and McGary, R. (2006) Effective Project Management: Traditional, Adaptive, Extreme. 4th
Edition. Wiley.

Updated 26 September 2011 Page 4 of 6

ASSESSMENT
The assessment for this module consists of three tasks, two of which are formative and one which is
summative. Your grade will be determined only by the summative component of this assessment. The tasks
are outlined below:

Task Description Percentage Weighting Feedback Type

of Assessment (Grade)
Task 1 Project Proposal & Ethical Assessment 0% Formative
Task 2 Presentation 0% Formative
Task 3 Project Report 100% Summative
.
DELIVERABLES AND FEEDBACK - IMPORTANT DATES
You should prepare and submit all coursework according to the Department's instructions for assessments
available in the Student Handbook on Blackboard Learn. You should make sure that you are fully aware of
the Department's policy on plagiarism and the marking of joint work. You should also be aware that you
cannot later claim that you did not know the rules and regulations as you must make yourself familiar with
them. If you cannot complete any work on time, you should look at the Department’s instructions on what
to do.

The Department policy is that all coursework must be submitted electronically via the University’s
Blackboard system. Please navigate to the Blackboard Learn pages for this module for further details.
You will get feedback on your performance via the Blackboard Learn pages for this module. If do not receive
your feedback by the given date, you should first contact the module leader. If it proves necessary, you
should also contact your Level Co-ordinator.

The important dates:

Assignment title/s Date to be made available on Submission deadline Feedback due by
the module page on Blackboard date/s date
Learn
Obtaining a Supervisor N/A 12th September, 2011 12th October, 2011
to 7th October, 2011
Task 1 Project Proposal 30th September, 2011 14th November, 2011 5th December,
& Ethical Assessment at 23:59 UK time 2011
Stage 2 Ethical N/A 16th December, 2011 at 23th January 2011
Assessment 23:59 UK time
st th
Task 2 Presentation 31 October, 2011 10 February, 2012 (see below)
at 23:59 UK time
th
Presentation Delivery N/A 6 February, 2012 to (see below)
10th February, 2012
Task 3 Project Report 31st October, 2011 27th March, 2012 N/A
at 16:30 UK time
Software N/A 30th March, 2012 to N/A
Demonstration 1st April, 2011

You are required to complete formative tasks (Task1 and Task2) which are designed and strategically
scheduled to offer you feedback on the progress and quality of your work. Both tasks will be assessed by
but will not be formally graded. This feedback is designed to improve your performance in the Task 3 report.

Feedback for Task 2 will be provided directly to the student at the time of the delivery of the presentation.

There will be no formal release of feedback for Task 3. This is because Task 3 is treated in the same way as a
final assessment for a module, the grades for which will be considered at the Board of Examiners and
communicated to the student via transcript

Updated 26 September 2011 Page 5 of 6

ADDITIONAL VITAL INFORMATION
The Information Systems and Computing student handbook can be found on the Information Systems and
Computing Blackboard site (portal). The ISC handbook is a useful source of information for all aspects of
your studies, including procedures of how to inform us of problems you are facing with your studies, how to
apply for an extension to your coursework, plagiarism, house style for assignments, joint and group work
submissions and other important matters. The Department assumes that you familiarise yourself with this
information, so you will need to look at these pages carefully at various times throughout your studies. The
Department also operates within the rules and regulations of the University more generally, and you should
also look at what are known as 'Senate Regulations’ under the University’s web pages.

These policies and procedures might change from one academic year to another and it is in your own
interest to keep yourself aware about them and their possible changes.

Updated 26 September 2011 Page 6 of 6