CE320-6-AU-CO:
Large Scale Software Systems and Extreme Programming

The details
2017/18
Computer Science and Electronic Engineering (School of)
Colchester Campus
Autumn
Undergraduate: Level 6
Current
Thursday 05 October 2017
Friday 15 December 2017
15
16 March 2011

 

Requisites for this module
(none)
(none)
(none)
(none)

 

(none)

Key module for

(none)

Module description

Learning Outcomes

The aim of this course is to provide students with a working knowledge of modern software development techniques for large software systems gained through a series of lectures, a 6-week team project and hands-on laboratories.

Upon completion of this course students will be able to

. Understand the issues involved in large scale software development and how they can be managed with modern practices, techniques and tools
. Make effective use of modern tools and techniques for the cooperative development of software including version control, ticketing systems, build tools, etc.
. Make effective use of modern bug prevention and detection techniques as well as refactoring techniques.
. Make use of modern practices and techniques for the effective development of software within teams

Outline Syllabus

The course will focus on powerful technologies such as:

1. agile software development,
2. extreme programming
3. working effectively in teams,
4. version control systems (which are also essential tools for configuaration management),
5. unit and acceptance testing,
6. integrated development environments,
7. build automation, continuous integration, integration servers,
8. ticketing systems,
9. refactoring,
10. release planning.

Module aims

No information available.

Module learning outcomes

No information available.

Module information

STUDENTS SHOULD NOTE THAT THIS INFORMATION IS SUBJECT TO REVIEW AND CHANGE

Learning and teaching methods

Lectures and laboratories

Bibliography

This module does not appear to have any essential texts. To see non-essential items, please refer to the module's reading list.

Assessment items, weightings and deadlines

Coursework / exam Description Deadline Coursework weighting
Coursework   CE320 Project Iteration 1   24/11/2017  40% 
Coursework   CE320 Project Iteration 2   15/12/2017  60% 
Exam  Main exam: 120 minutes during Summer (Main Period) 

Exam format definitions

  • Remote, open book: Your exam will take place remotely via an online learning platform. You may refer to any physical or electronic materials during the exam.
  • In-person, open book: Your exam will take place on campus under invigilation. You may refer to any physical materials such as paper study notes or a textbook during the exam. Electronic devices may not be used in the exam.
  • In-person, open book (restricted): The exam will take place on campus under invigilation. You may refer only to specific physical materials such as a named textbook during the exam. Permitted materials will be specified by your department. Electronic devices may not be used in the exam.
  • In-person, closed book: The exam will take place on campus under invigilation. You may not refer to any physical materials or electronic devices during the exam. There may be times when a paper dictionary, for example, may be permitted in an otherwise closed book exam. Any exceptions will be specified by your department.

Your department will provide further guidance before your exams.

Overall assessment

Coursework Exam
50% 50%

Reassessment

Coursework Exam
0% 0%
Module supervisor and teaching staff
Prof Riccardo Poli, email: rpoli@essex.ac.uk.
Professor Riccardo Poli
CSEE School Office, email: csee-schooloffice (non-Essex users should add @essex.ac.uk to create full e-mail address), Telephone 01206 872770

 

Availability
Yes
No
No

External examiner

Dr Jeremy Ian Hiller Gow
Goldsmiths College
Lecturer
Resources
Available via Moodle
Of 52 hours, 22 (42.3%) hours available to students:
30 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.