Object-Oriented Analysis and Design

Introduction

Programming with the right objects can greatly improve the dependability and malleability of software intensive systems. Bad objects, on the other hand, are probably worse than no objects at all. This course is about the planning and design of the right objects, classes and type system for software intensive systems.

The course presents techniques for the technical design of good object classes and architectures, and for the understanding, modelling and use of the subject matter and requirements.

There are several areas of potential confusion in analysis and design for object technology, and the course is careful to distinguish the various stages--requirements capture, subject and systems analysis, subject-oriented design and object-oriented design--and to present the impact that an eventual object implementation has on each.

The notation used is the Unified Modelling Language. The UML has quickly become the standard software engineering notation.

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 normally know, and will have used, at least one high-level programming language. They will have worked with specifications and designs, either creating them or implementing them. They will be wanting to know what object technology means for analysis and design. It will perhaps be helpful if they have read a little on the reasons for, and expected benefits from, object technology.

Aims

• To experience the insights necessary to obtain maximum benefit from object technology
• To understand the need for, the place of, and aims of, requirements, analysis and design
• To become familiar with a common, standard notation--UML
• To understand the iterative process of model design, evolution and presentation
• To be ready to apply object-oriented techniques appropriately to the production of specifications and designs

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.

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

Contents

• Objects and object-orientation
• Development stages
• Requirements capture
• Analysing the subject matter
• Finding entities
• Using inter-entity relationships
• Starting design
• Inter-object dynamics (CRC)
• Class packaging
• Class design
• Relationship design
• Interaction diagrams
• Implementing classes

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 John Deacon by telephone on +44 20 7498 3773; by fax on +44 20 7498 3747; by emailing  jdeacon@jdl.co.uk; or by visiting http://www.jdl.co.uk

[ Home page | Courses List ]

Last modified: Thursday, 08-Feb-2007.
Copyright © 2007 John Deacon. All rights reserved.