Software Engineering

The details
Computer Science and Electronic Engineering (School of)
Colchester Campus
Undergraduate: Level 5
Thursday 03 October 2019
Saturday 14 December 2019
25 April 2019


Requisites for this module



Key module for

BSC G400 Computer Science,
BSC G401 Computer Science (Including Year Abroad),
BSC G403 Computer Science (Including Foundation Year),
BSC I101 Computer Science (Including Placement Year),
MSCIG402 Computer Science,
MSCII100 Computer Science (Integrated Masters, Including Placement Year),
BSC GH56 Information and Communication Technology,
BSC GH5P Information and Communication Technology (Including Year Abroad),
BSC I102 Information and Communication Technology (Including Placement Year),
BSC G111 Computing,
BSC G112 Computing (Including Year Abroad),
BSC G113 Computing (Including Placement Year)

Module description

This module will equip students with the main principles guiding the activities involved in software development throughout its lifecycle, including software requirements, object-oriented analysis and design, software validation and testing, software maintenance and software evolution, and configuration management processes and tools.

Module aims

The aims of this module are to guide students through the software development cycle including requirements, analysis, design, validation, testing, maintenance, and evolution. Students will understand the principles of software engineering, carry out object-orientated software requirement specification, understand object-orientated constructs, show understanding of architecture styles and demonstrate a strong understanding of software reliability.

Module learning outcomes

After completing this module, students will be expected to be able to:

1. demonstrate an understanding of the principles of software engineering
2. demonstrate an ability to carry out software requirements specification, object-oriented analysis and design, and software testing
3. demonstrate an understanding of object orientation and relate object-oriented models to corresponding object-oriented programming constructs
4. represent the outcome of each stage in the software lifecycle using standard modeling notations
5. demonstrate a basic understanding of architectural styles and design patterns
6. demonstrate an understanding of software reliability issues

Module information

Outline Syllabus

Introduction to software engineering
Lifecycle models
Software modeling notations
Requirements analysis and specification
Principles of software design
Functional and non-functional requirements and the need to verify and validate them through a variety of techniques
Principles of object-oriented design
Introduction to design patterns and architectural styles
Validation and testing, including unit testing, and testing against requirements
Software reliability and quality
Evolution and maintenance
Configuration management processes and tools

Learning and teaching methods

Lectures and Classes


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 Weighting
Coursework Progress Test - Wk 11 50%
Coursework Assignment 1 Requirements Analysis 20/11/2019 50%
Exam 120 minutes during Summer (Main Period) (Main)

Overall assessment

Coursework Exam
40% 60%


Coursework Exam
40% 60%
Module supervisor and teaching staff
Dr Michael Gardner
CSEE School Office, email: csee-schooloffice (non-Essex users should add @essex.ac.uk to create full e-mail address), Telephone 01206 872770



External examiner

Dr Jeremy Ian Hiller Gow
Goldsmiths College
Available via Moodle
Of 42 hours, 38 (90.5%) hours available to students:
4 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.