Module 18191 (2012)

Module Description - Software Engineering

The Module Description is a strict subset of the Syllabus Page, which gives more information

Module TitleSoftware Engineering
SchoolComputer Science
Module Code06-18191
DescriptorCOMP/06-18191/LI
Member of StaffRami Bahsoon (coordinator), Joan Jackson:10, Rami Bahsoon:10
LevelI
Credits20
Semester1+2
Pre-requisites06-11224 (Introduction to Software Engineering) (or equivalent)
Co-requisitesNone
RestrictionsNone
Contact hours48
Delivery2 hrs/week, conventional lectures and tutorials.
NOTE: This module is taught in 2 parts. Part I Sem1. Part II (Sem2).
DescriptionManagement of the software development process, including: how projects arise, choosing the right project, software life cycles, human factors in project management, basic project management techniques (e.g. planning, estimating, monitoring progress), advanced project management techniques (e.g. risk management, configuration management, quality management, process improvement). Overview of requirements engineering, requirements elicitation & analysis, requirements definition & specification, requirements validation, requirements management, overview of specification techniques. Object-oriented analysis and design using Unified Modeling Language (UML) and patterns.
Outcomes
On successful completion of this module, the student should be able to:Assessed by:
explain the basic principles of project management, including the role of the project manager Continuous assessment, examination
apply standard techniques in project management Continuous assessment, examination
analyse the organizational issues surrounding the development and implementation of systems solutionsContinuous assessment, examination
identify appropriate interpersonal skills to manage and perform the systems development process more effectivelyContinuous assessment, examination
explain the importance of successful requirements definition in commercial software development, identifying the difficulties involvedContinuous assessment, examination
explain and apply appropriate techniques which help to define clear and unambiguous requirementsContinuous assessment, examination
explain and apply the knowledge and skills required to act as a contributing junior analyst in a project team working within a disciplined project environment Continuous assessment, examination
use UML to describe analysis and design modelsContinuous assessment, examination
apply important design techniques and patterns where it helps to improve design modelsContinuous assessment, examination
explain current methods used for system developmentExamination
AssessmentSessional: 2 hr examination (50%), continuous assessment (50%).
Supplementary (where allowed): By examination only.
Continuous assessment (assessed exercises or assignments): Part I (5 exercises [20% in total] + 1 assignment [30% in total]) and Part II (1 assignment worth 50%).
TextsField & Keller, Project Management,
Ian Sommerville, Software Engineering (8th ed.),
S Bennett, S McRobb & R Farmer, Object Oriented Systems Analysis and Design using UML (3rd edition), 2006
J Jackson, Lecture Notes,
E Gamma, R Helm, R Johnson & J Vlissides, Design Patterns: Elements of Reusable Object-Oriented Software, 1995
C Britton & J Doake, Object Oriented Systems Development -- A Gentle Approach,
S & J Robertson, Mastering the requirements process (2nd ed.), 1999