Module 26426 (2013)
Syllabus page 2013/2014
06-26426
Software Engineering II
Level 2/I
Links | Outline | Aims | Outcomes | Prerequisites | Teaching | Assessment | Books | Detailed Syllabus
The Module Description is a strict subset of this Syllabus Page. (The University module description has not yet been checked against the School's.)
Relevant Links
Further information about this module can be found on the
module web page
.
Outline
Overview of software lifecycle, Distributed software architectures: styles, quality attributes, design trade-offs, evaluation, specification and tools support; Object-oriented analysis and design using Unified Modelling Language (UML) and patterns.
Aims
The aims of this module are to:
- introduce some methods and techniques available to the software engineer for use in the requirements engineering process
- present standard object-oriented techniques for software analysis and design
- introduce key object-oriented design principles
- introduce design patterns and demonstrate how they can facilitate the overall development process
Learning Outcomes
| On successful completion of this module, the student should be able to: | Assessed by: | |
| 1 | explain the importance of architecture in distributed software systems, identify styles and patterns, and understand the design trade-offs involved | Examination, Continuous Assessment |
| 2 | use UML in the analysis, architecture, design of software systems | Examination, Continuous Assessment |
| 3 | Distinguish between various software lifecycle models and their use | Examination, Continuous Assessment |
Restrictions, Prerequisites and Corequisites
Restrictions:
None
Prerequisites:
06-11224 Introduction to Software Engineering
Co-requisites:
None
Teaching
Teaching Methods:
Lectures
Contact Hours:
Assessment
- Sessional: 1.5 hr examination (50%), continuous assessment (50%).
- Supplementary (where allowed): By 1.5 hr examination only (100%).
Recommended Books
| Title | Author(s) | Publisher, Date |
| , |
Detailed Syllabus
- To be confirmed
- To be confirmed
- To be confirmed
- To be confirmed
- To be confirmed
Last updated: 22 August 2013
Source file: /internal/modules/COMSCI/2013/xml/26426.xml
Links | Outline | Aims | Outcomes | Prerequisites | Teaching | Assessment | Books | Detailed Syllabus