Object-Oriented Design using UML

Introduction

Object technology only delivers its promised benefits when the right objects are used--a bad object is worse than no objects at all. This course is all about choosing, planning and presenting the right set of objects in the right architecture. The notation used is that of the Unified Modelling Language (UML).

Duration and Construction

The course lasts three days. Each day will start at 09.30 and finish at 16.30. The delivery is via lecture, exercise and discussion.

The days consist of two morning sessions and three, shorter afternoon sessions, with one hour for lunch. Time will be available after 16.30 for extended discussions or related issues.

Intended Audience

Participants will probably already have some knowledge of object technology although not necessarily at a detailed level. Participants will normally know, and will have used, at least one high-level programming language. They will be wanting to know how to plan their use of object technology. It will be helpful if they have read a little about the reasons for, and expected benefits from, object technology.

Aims

To experience the insights that are necessary in order to obtain the maximum benefit from object technology
To understand the rôle of the requirements and analysis inputs, and the way in which they should be used
To learn architecture and class design techniques
To learn one way of staging the design process
To become aware of some of the myths of object-oriented design
To learn the criteria for assessing the quality of a design
To learn a design notation--the UML
To become aware of known design patterns and their sources
To get to a position where the object-oriented designs that are produced are reliable, robust, extensible and efficient

Deliverables

Lectures
Facilitation of discussions
Direction, assistance and feedback on exercises
Proposed solutions to the exercises
Copies of lecture slides, plus explanatory text and summaries
Reference list of books and sources

Numbers

We recommend that there are no more than 12 participants, with the best results usually obtained when there are at least 8 participants. It is possible, by negotiation and mutual agreement, for more than 12 participants to be present.

Introduction to objects and object technology
Exploring and choosing types
First services
The nature of object relationships
Inter-object dynamics
Internal class dynamics
Class management (libraries and other packagings)
Class design
Relationship design
Class implementation detail
Patterns and pattern languages

Site Requirements

Data projector of at least 1024 x 768 resolution, and suitable screen
White-board, preferably not doubling up as the OHP's screen; blackboard and chalk are acceptable
Flip-chart and easel, with additional flip-chart paper
It is best if the seating is not fixed. Auditorium style seating, for example, makes it difficult to switch from lecture to group work.

Contacting

Please contact Matrice by telephone on +44 7010 704705; by fax on +44 7010 704706; by emailing bookings@matrice.co.uk; or by visiting http://www.matrice.co.uk