tutorials

11	sunday morning	Convention Centre, Room 13
11T	tuesday afternoon	Pan Pacific Hotel, Pavilion A

Exploring the Unified Modeling Language by Example

Charles Richter, Objective Engineering, Inc.

As the "unification" of the OMT and Booch notations, the Unified Modeling Language (UML) is emerging as the standard object-oriented analysis and design notation because it attempts to provide notation for most aspects of object-oriented design. However, UML is a rich and complex language. This tutorial uses the design of a small problem to explore many of UML's more advanced features, including use case diagrams, activity diagrams, and concurrency and distribution constructs.

Upon completion of this tutorial, attendees should have a deeper understanding of the UML and its application to real, everyday problems. Attendees will also be exposed to some of the more advanced and unusual features of the UML.

Attendee Background: This tutorial is aimed at developers who have at least a rudimentary knowledge of the Unified Modeling Language (UML) notation and are interested in a more detailed understanding of the application of that notation. The tutorial assumes the attendee understands basic object-oriented concepts such as classes, inheritance, and polymorphism, as well as the basic object-oriented modeling and design constructs such as class diagrams (object models) and object interaction diagrams.

Charles Richter has been involved in object-oriented development for over ten years, and has been teaching object-oriented methods for most of that time. He has considerable development and teaching experience with OMT, Booch, and more recently UML. He is the founder and a principal of Objective Engineering, Inc., a company dedicated to providing quality training and consulting in object-oriented analysis and design methods and Java programming.

Exploring the Unified Modeling Language by Example

Other tutorials in the UML thread are:

Related tutorials:

for beginners (yellow):
51*: Introduction to Visual Modeling and the UML 35, 35W: Software Architecture and the UML