UML 2 Briefing

Introduction

The Unified Modelling Language (UML) was one of the previous decade's most important contributions to software engineering. The good news was that we had a standard software engineering notation at long last and that it was being adopted just about everywhere. The bad news was that there were all manner of dusty corners and sharp edges to perplex and confuse creators and users of UML-based specifications.

Several revisions were made following the original appearance of the UML, partly during the time the UML was in the custody of its original creators, and partly since the Object Management Group (OMG) took over stewardship of the UML. We have reached version 1.5 by this route. In parallel with this steady evolution of UML 1, a revision task force of the OMG has been working on a major revision, UML 2, which is now complete, bar a final beating of the documentation into shape.

UML 2.0 brings several improvements. It is more sensible and more consistent. In particular, the activity diagrams, which had suffered from both motivational and existential crises, settled down to doing a job that was better defined, and doing it in a way that was a little more sensible. The state machines also benefited from some needed clarifications. There were many smaller scale revisions to the structure and sequence diagrams.

This briefing describes some of the more serious shortcomings of UML 1, and introduces the changed and new provisions of UML 2.0.

Duration and Construction

The briefing lasts one day and comprises a mixture of lecture, discussion and questions.

Intended Audience

Participants will be developers or project managers. They may or may not already be familiar with the Unified Modelling Language. They will be wanting to acquaint themselves with UML 2.0 and its impact.

Aims

• To understand where the UML came from and how it was shaped
• To appreciate what the troublesome aspects of the UML were
• To appreciate the infrastructure within which the UML is now defined (metamodels, meta-metamodels and MOF)
• To understand the changes that UML 2.0 has made
• To understand the new provisions of UML 2.0
• To consider the impact of UML 2.0 on projects

Deliverables

• Lecture
• Facilitation of discussions
• Copies of the lecture slides
• 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.

Contents

• A brief history of UML 1.x
• The problems with state machines
• The problems with activity diagrams
• The problems with deployment diagrams
• Other troublesome areas
• The structure of UML 2.0 (infrastructure and superstructure)
• Changes to structure diagrams and sequence diagrams
• Changes to state machine diagrams
• The new activity diagrams
• Other new provisions of UML 2.0
• The impacts of UML 2.0

Site Requirements

• Data projector with a real 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, 15-Mar-2007.
Copyright © 2007 John Deacon. All rights reserved.