Unified Modeling Language

introduction class diagrams use cases interaction packages state and activity discussion

The Unified Modeling Language (UML) resulted from a joint effort of leading experts in object-oriented analysis and design, Grady Booch, Jim Rumbaugh and Ivar Jacobson, also known as the three amigos, all currently employees of Rational.

UML provides (graphical) notations to express functional, structural and behavioral properties of (object-oriented) systems. UML is not a method. It does not prescribe the steps to be taken in development. UML may best be regarded as a toolbox, from which the developer can choose a notation or technique as the need occurs.

Unified Modeling Language

UML

class diagrams -- conceptual structure
use cases -- functional requirements
interaction diagrams -- operational characteristics
package and deployment diagrams -- implementation
state and activity diagrams -- dynamic behavior

See http://www.rational.com/uml and UML Distilled, [Fowler97]

slide: UML

In this section we will look at a selection of the notational tools provided in the UML, as indicated in slide uml. For additional information see Rational's Web site. I also strongly recommend [Fowler97].

[F] - [up] [top] - [I] [II] [III] [IV] - [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] - [A] [R]

Hush Online Technology

hush@cs.vu.nl
12/29/99