Course Name: The Unified Modeling Language (UML) Notation
Course Overview: The Unified Modeling Language (UML) is
the language of choice for object-oriented business models, analysis models,
and designs. Some analysts, managers, testers, and other individuals
must be able to read and comprehend UML diagrams without understanding
how to develop those diagrams. Put another way, they must review
models and designs, but they are not modelers or developers. This
course explains how to interpret basic UML notation. It explains
the fundamental concepts and notational conventions for the UML's seven
diagrams.
Course Audience: This course is beneficial to individuals
who must understand the UML notation. Note that this is not an object-oriented
design course and hence is inappropriate for individuals whose goal is
to learn how to conduct object-oriented modeling or object-oriented design.
Those individuals should take our couse,
Object-Oriented
Analysis and Design Using the Unified Modeling Language (UML).
Course Duration: Two days.
Course Prerequisites: Attendees should have some exposure
to the business or development side of software, but need not have any
knowledge of object-oriented concepts or of the UML notation.
Course Outline:
Introduction: A discussion of what the UML is, of some
basic object-oriented concepts, and of source references for the UML.
Use Case Diagrams: Actors and use cases. Actor and
use case relationships.
Activity Diagrams: The use of activity diagrams to depict
the temporal sequencing of activities.
Class Diagrams: Basic concepts and notation for class diagrams.
Classes, attributes, and methods. Associations, aggregation, composition,
and specialization.
Interaction Diagrams: Communication diagrams and sequence
diagrams. The relationship of interaction diagrams to scenarios and
to class diagrams. Branching, iteration, and object creation and
destruction.
Statechart Diagrams: Using a statechart diagram to model
the state-based behavior of objects. Composite and parallel states.
Component, Deployment, and Package Diagrams: Depicting physical architecture
with component diagrams and deployment diagrams. Package diagrams for logical architecture.
Concurrency: Introducing concurrency and synchronization
requirements in class diagrams and interaction diagrams.
Extension Mechanisms: UML mechanisms for extending the
UML notation.
Return to OO Course Catalog
|