UML 2 For Real-Time Software Engineers

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 since 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 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 course introduces UML 2 to developers of real-time systems.

Duration and Construction

The course lasts three days and comprises a mixture of lecture, discussion and questions.

Intended Audience

Participants will be developers of real-time systems. They will be wanting to know what the Unified Modelling Language offers for the portrayal of requirements, specifications and designs for real-time systems.

Aims

• To understand where the UML came from, its agenda and how it has been shaped over the years
• To provide a common language for the expression of real-time requirements, specifications and designs
• To bring real-time software engineers to a common understanding of what the UML can portray and what it cannot
• To bring real-time software engineers to a point where the issues involved in adopting the UML for real-time specification and designs can be debated
• To be aware of the differences between UML 1.x and UML 2.0

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
• A typical software development process
• A brief survey of objects and object-orientation
• A very brief introduction to the structure of UML 2.0 (infrastructure and superstructure)
• Requirements and UML use cases
• Analysis and UML structure diagrams
• Analysis and UML state machine diagrams
• Design and UML structure diagrams ("class" diagrams)
• Design and UML sequence diagrams
• UML activity diagrams
• UML timing diagrams
• UML composite structure diagrams
• UML communication diagrams
• UML component diagrams
• UML deployment diagrams

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.