Department of Mathematics & Computer Science

CO2006 Software Engineering and System Development

Explanation of Pre-requisites

Course Description

Aims

Objectives

• analyse customer requirements;
• produce a design based on an object oriented specification;
• use VDM for specification of some classes, objects, and their operations,
• implement a design; and
• be very clear about activities to carry out and the artifacts to produce in a software development,
• use UML for consistent specifications the models at different levels of abstraction in the development of a system of a moderate size;
• have a sound grasp of the basic principles and techniques in object-oriented software development.

Transferable Skills

• the skill and ability in customer requirements analysis;
• the skill and ability in to write precise and abstract requirement specification;
• the skill and ability in transforming a requirement specification into a design, and in coding a design.
• the understanding of system development process;
• the principles and techniques of software development.

Syllabus

Software Development Process: Requirement analysis; system design; implementation and unit testing; integration and system testing; operation and maintenance; the waterfall model; evolutionary development.

Introduction to OO Development: The inherent complexity of software; mastering complex systems; examples of complex systems; function oriented vs object-oriented methods.

Object-oriented requirement capture and analysis: Case study; requirement specification; use cases; conceptual models, use case based project planning; testing based on use cases.

System Behaviour: System Sequence Diagrams and Operations: System input events and system operations; system sequence diagrams (SSD); contracts; from analysis to design.

OO Design: Interaction diagrams; UML notational issues. creating interaction diagrams, patterns for assigning responsibilities; a design of POST; connecting user interface objects to domain object; design class diagrams; use interaction for testing plan.

Implementing a Design: UML notation for interface details; mapping a design to code; container/collection classes in code.

Advanced Modelling Concepts and Design Techniques: Iterative development process; generalization; abstract classes; associative classes; UML notation for packages; modelling behaviour in state diagrams; VDM specification of classes and objects; Configuration Control

Summing Up and Revision

Reading list

Essential:

Recommended:

I. Jacobson, G. Booch, and J. Rumbaugh, The Unified Software Development Process, Addison-Wesley, 1999.

C. Larman, Applying UML and Patterns, Prentice-Hall International, 1998.

R. Pooley and P. Stevens, Using UML: Software Engineering with Objects and Components, Addison-Wesley, 1999.

Background:

B. Meyer, Object-oriented Software Construction (2nd Edition), Prentice Hall PTR, 1997.

R. Pressman, Software Engineering - A Practitioner's Approach (4th Edition), McGraw Hill, 1997.

S.R. Schach, Classical and Object-Oriented Software Engineering (3rd Edition), IRWIN, 1996.

I. Sommerville, Software Engineering (5th Edition), Addison-Wesley, 1995.

Details of Assessment

The written January examination contains six questions, and candidates can obtain full marks from four good questions.

Author: S. J. Ambler, tel: +44 (0)116 252 3884
Last updated: 2002-07-11
MCS Web Maintainer
This document has been approved by the Head of Department.
© University of Leicester.