Introduction to UML

Jayant Shrivastava, TCS

September 6, 2010 TCS Public

Overview

 What is Modeling?
 What is UML?
 A brief history of UML
 Understanding the basics of UML
 UML diagrams
 UML Modeling tools

September 6, 2010 2
Modeling

Describing a system at a high level of abstraction

 A model of the system
 Used for requirements and specifications

 Is it necessary to model software systems?

 Necessary to manage complexity
 Good for quick understanding of the systems
 Less chances of conflicting views b/w end-user and system designers

September 6, 2010 3
What is UML?

 UML stands for “Unified Modeling Language”

 It is a industry-standard graphical language for specifying, visualizing,

constructing and documenting the artifacts of software systems

 The UML uses mostly graphical notations to express the OO analysis

and design of software projects. 

 Simplifies the complex process of software design

September 6, 2010 4
Why UML for Modeling ?

 Use graphical notation to communicate more clearly than natural language

(imprecise) and code (too detailed).

 Help acquire an overall view of a system.

 UML is not dependent on any one language or technology.

 UML moves us from fragmentation to standardization.

September 6, 2010 5
History of UML

September 6, 2010 6
Types of UML Diagrams
 Use Case Diagram

 Class Diagram

 Sequence Diagram

 Collaboration Diagram

 State Diagram

This is only a subset of diagrams … but are most widely used

September 6, 2010 7
Use Case Diagram

 Used for describing a set of user scenarios

 Mainly used for capturing user requirements

 Work like a contract between end user and software developers

September 6, 2010 8
Use Case Diagram (core components)

 Actors: A role that a user plays with respect to the system,including human
users and other systems. e.g.,inanimate physical objects (e.g. robot); an
external system that needs some information from the current system.

 Use case: A set of scenarios that describing an interaction between a user and
a system, including alternatives.

System boundary: rectangle diagram representing the boundary between the

actors and the system.

September 6, 2010 9
Use Case Diagram (core relationship)
 Include: a dotted line labeled <<include>> beginning at base use case and
ending with an arrows pointing to the include use case. The include relationship
occurs when a chunk of behavior is similar across more than one use case. Use
“include” in stead of copying the description of that behavior.

<<include>>

 Extend: a dotted line labeled <<extend>> with an arrow toward the base case.
The extending use case may add behavior to the base use case. The base class
declares “extension points”.

<<extend>>

September 6, 2010 10
Use Case Diagram (core relationship)

 Association: communication between an actor and a use case; Represented by

a solid line.

 Generalization: relationship between one general use case and a special use
case (used for defining special alternatives), Represented by a line with a
triangular arrow head toward the parent use case.

September 6, 2010 11
Use Case Diagrams
 A generalized description of how a system will be used. 
 Provides an overview of the intended functionality of the system
Boundary Use Case
Actor
Library System

Borrow
Employee
Client

Order Title

Fine Remittance

Supervisor

September 6, 2010 12
Use Case Diagrams (cont.)

September 6, 2010 13
Use Case Diagrams (cont.)
 Pay Bill is a parent use case and Bill Insurance is the child use case.
(generalization)

 Both Make Appointment and Request Medication include Check Patient

Record as a subtask.(include)

 The extension point is written inside the base case

 Pay bill; the extending class Defer payment adds the behavior of this extension
point. (extend)

September 6, 2010 14
Class diagram
 Used for describing structure and behavior in the use cases

 Provide a conceptual model of the system in terms of entities and their

relationships

 Used for requirement capture, end-user interaction

 Detailed class diagrams are used for developers

September 6, 2010 15
Class representation

 Each class is represented by a rectangle subdivided into three compartments

 Name
 Attributes
 Operations
 Modifiers are used to indicate visibility of attributes and operations.
 ‘+’ is used to denote Public visibility (everyone)
 ‘#’ is used to denote Protected visibility (friends and derived)
 ‘-’ is used to denote Private visibility (no one)
 By default, attributes are hidden and operations are visible.

September 6, 2010 16
An example of Class

Name
Account_Name
- Customer_Name
Attributes
- Balance
+addFunds( ) Operations
+withDraw( )
+transfer( )

September 6, 2010 17
OO Relationships

 There are two kinds of Relationships

 Generalization (parent-child relationship)
 Association (student enrolls in course)
 Associations can be further classified as
 Aggregation
 Composition

September 6, 2010 18
OO Relationships: Generalization

Supertype Example: Customer

Regular Loyalty
Customer Customer
Subtype1 Subtype2

or: Customer

 Generalization expresses a parent/child

relationship among related classes.
 Used for abstracting details in several Regular Loyalty
Customer Customer
layers

September 6, 2010 19
OO Relationships: Association

 Represent relationship between instances of classes

 Student enrolls in a course
 Courses have students
 Courses have exams
 Etc.
 Association has two ends
 Role names (e.g. enrolls)
 Multiplicity (e.g. One course can have many students)
 Navigability (unidirectional, bidirectional)

September 6, 2010 20
Association: Multiplicity and Roles

student
1 *

University Person

0..1 *
employer teacher

Multiplicity Role
Symbol Meaning
1 One and only one
Role
0..1 Zero or one “A given university groups many people;
some act as students, others as teachers.
M..N From M to N (natural language)
A given student belongs to a single
* From zero to any positive integer university; a given teacher may or may not
0..* From zero to any positive integer be working for the university at a particular
1..* From one to any positive integer time.”

September 6, 2010 21
Class Diagram
Name Order class
-dateReceived
Multiplicity: mandatory
Attributes -isPrepaid Customer
-number :String
-price : Money
* 1 -name
-address
+dispatch() Association +creditRating() : String()
Operations +close()

1
{if Order.customer.creditRating is Generalization
"poor", then Order.isPrepaid must
be true }

Corporate Customer Personal Customer

-contactName -creditCard#
Constraint -creditRating
-creditLimit
Multiplicity: (inside braces{}}
+remind()
+billForMonth(Integer)
Many value
0..1
Multiplicity:
optional *
Employee
*
OrderLine
-quantity: Integer 1
-price: Money * Product
-isSatisfied: Boolean

September 6, 2010 22
Association: Model to Implementation

* 4
Student Course
has enrolls

• Class Student {
• Course enrolls[4];
•}

• Class Course {
• Student have[];
•}

September 6, 2010 23
OO Relationships: Composition
 Composition: expresses a relationship among instances
 of related classes. It is a specific kind of Whole-Part Whole Class
relationship. Class W

 It expresses a relationship where an instance of the

Whole-class has the responsibility to create and initialize
instances of each Part-class.

It may also be used to express a relationship where instances Class P1 Class P2

of the Part-classes have privileged access or visibility to
certain attributes and/or behaviors defined by the
Whole-class.
Part Classes
Composition should also be used to express relationship where
instances of the Whole-class have exclusive access to and
control of instances of the Part-classes. Example
Automobile
 Composition should be used to express a relationship where
the behavior of Part instances is undefined without being
related to an instance of the Whole. And, conversely, the
 behavior of the Whole is ill-defined or incomplete if one or
more of the Part instances are undefined. Engine Transmission

September 6, 2010 24
OO Relationships: Aggregation
 Aggregation: expresses a relationship among instances Container Class
 of related classes. It is a specific kind of Container-Containee
relationship. Class C

AGGREGATION
 It expresses a relationship where an instance of the
Container-class has the responsibility to hold and maintain
instances of each Containee-class that have been created
outside the auspices of the Container-class. Class E1 Class E2

Aggregation should be used to express a more informal

relationship than composition expresses. That is, it is an Containee Classes
appropriate relationship where the Container and its
Containees can be manipulated independently.

 Aggregation is appropriate when Container and Containees

Example
have no special access privileges to each other. Bag

Apples Milk

September 6, 2010 25
Aggregation vs. Composition

 Composition is really a strong form of aggregation

 components have only one owner
 components cannot exist independent of their owner
 components live or die with their owner
e.g. Each car has an engine that can not be shared with other cars.

 Aggregations may form "part of" the aggregate, but may not be essential
to it. They may also exist independent of the aggregate.
e.g. Apples may exist independent of the bag.

September 6, 2010 26
Sequence Diagram (make a phone call)
Caller Phone Recipient

Picks up

Dial tone

Dial

Ring notification Ring

Picks up

Hello

September 6, 2010 27
Sequence Diagram :Object interaction

 Self-Call:
Self-Call A message that an A B
 Object sends to itself.
Synchronous

 Condition: indicates when a message is sent.

 The message is sent only if the condition is true. Asynchronous

Transmission
delayed

[condition] remove()
Condition
*[for each] remove()
Iteration

Self-Call

September 6, 2010 28
Sequence Diagrams – Object Life Spans

 Creation A
 Create message
 Object life starts at that point
 Activation Create
B
 Symbolized by rectangular stripes
 Place on the lifeline where object is activated.
 Rectangle also denotes when object is deactivated.
 Deletion
 Placing an ‘X’ on lifeline
 Object’s life ends at that point
Activation bar
X
Return
Deletion
Lifeline

September 6, 2010 29
Sequence Diagram
 Sequence diagrams demonstrate the Us er Catalog Res ervations

behavior of objects in a use case

1: look up ()
 by describing the objects and the
2: title data ()
messages they pass.
 The horizontal dimension shows 3: [not available] res erve title ()

the objects participating in the 4 : title returned ()

interaction.
5: hold title ()
 The vertical arrangement of
5 : title available ()
messages indicates their order.
 The labels may contain the seq. 6 : borrow title ()

# to indicate concurrency. 6 : rem ove res ervation ()

September 6, 2010 30
Interaction Diagrams: Collaboration diagrams
start
6: remove reservation

3 : [not available] reserve title

User Reservations

5: title available
6 : borrow title
1: look up
2: title data

4 : title returned
Catalog

5 : hold title

 Shows the relationship between objects and the order of messages passed between them.
 The objects are listed as rectangles and arrows indicate the messages being passed
 The numbers next to the messages are called sequence numbers. They show the sequence
 of the messages as they are passed between the objects. 
 convey the same information as sequence diagrams, but focus on object roles instead of the time sequence.

September 6, 2010 31
State Diagram (Billing Example)
State Diagrams show the sequences of states an object goes through during its life cycle
in response to stimuli, together with its responses and actions; an abstraction of all
possible behaviors.

Start End
Unpaid Paid
Invoice created payin Invoice destroying
g

September 6, 2010 32
State Diagrams (Traffic light example)

Traffic Light Start

State
Transition Red

Yellow

Green

Event

September 6, 2010 33
UML Modeling Tools

 Rational Rose (www.rational.com) by IBM

 TogetherSoft Control Center, Borland (http://

www.borland.com/together/index.html)

 ArgoUML (free software) (http://argouml.tigris.org/ )

 OpenSource; written in java

 Others (http://www.objectsbydesign.com/tools/umltools_byCompany.html )

September 6, 2010 34
THANK YOU

September 6, 2010 35