CE202-5-AU-CO:
Software Engineering
2023/24
Computer Science and Electronic Engineering (School of)
Colchester Campus
Autumn
Undergraduate: Level 5
Current
Thursday 05 October 2023
Friday 15 December 2023
15
02 December 2022
Requisites for this module
(none)
(none)
(none)
(none)
(none)
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 G111 Computing,
BSC G112 Computing (Including Year Abroad),
BSC G113 Computing (Including Placement Year),
BSC I400 Artificial Intelligence,
BSC I401 Artificial Intelligence (Including Foundation Year),
BSC I402 Artificial Intelligence (including Placement Year),
BSC I403 Artificial Intelligence (including Year Abroad)
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.
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.
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
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
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 |
Progress Test |
|
50% |
| Coursework |
Assignment 1 Requirements Analysis |
|
50% |
| Exam |
Main exam: In-Person, Open Book (Restricted), 120 minutes during Summer (Main Period)
|
| Exam |
Reassessment Main exam: In-Person, Open Book (Restricted), 120 minutes during September (Reassessment 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
Reassessment
Module supervisor and teaching staff
Dr Cunjin Luo, email: cunjin.luo@essex.ac.uk.
Dr Cunjin Luo
School Office, email: csee-schooloffice (non-Essex users should add @essex.ac.uk to create full e-mail address), Telephone 01206 872770(non-Essex users should add @essex.ac.uk to create full e-mail address), Telephone 01206 872770
Yes
No
Yes
Dr Adam Chester
University Of Warwick
Associate Professor
Available via Moodle
Of 57 hours, 20 (35.1%) hours available to students:
36 hours not recorded due to service coverage or fault;
1 hours not recorded due to opt-out by lecturer(s), module, or event type.
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.