COP4331 UML Lecture

Presented By: Antoniya Petkova

9/11/2009
Originally Prepared By: Pengju Shang
for EEL5881 Software Engineering I
Slides material
Slides material are taken from different sources
including:
 UML resource page http://www.uml.org

 Google: UML Tutorial/Diagrams

 Object-Oriented Classical Software Engineering,

seventh Edition, Stephen R. Schach
 the slides of Mr. Shiyuan Jin’s UML class, EEL
4884, Fall 2003
 the slides of Mr. Yi Luo’s UML class, EEL 5881, Fall
2007.
Outline
 What is UML?
 Why Use UML?
 UML Diagrams
 Resources
What is UML?
 UML → “Unified Modeling Language”
 Unified: UML has become a world
standard
 Modeling :Describing a software system
at a high level of abstraction
 Language: More comprehensible, ready-
to-use, expressive, and visualing.
What is UML?
 Goals of UML:
 Provide extensibility and specialization mechanisms to
extend the core concepts
 Be independent of particular programming languages and
development processes
 Provide a formal basis for understanding the modeling
language
 Encourage the growth of the OO tools market.
 Support higher-level development concepts such as
collaborations, frameworks, patterns and components.
What is UML?
 History of UML
 Object-Oriented modeling languages
began to appear between mid-1970 and
the late 1980s ;
 Identified modeling languages: < 10  >
50 (1989-1994 )
 Necessity and development
What is UML?
Year Version
2003: UML 2.0
2001: UML 1.4
1999: UML 1.3
1997: UML 1.0, 1.1
1996: UML 0.9 & 0.91
1995: Unified Method 0.8

Booch ‘93 OMT - 2

Other methods

Booch ‘91
OMT - 1
began in late 1994(unifying the Booch and OMT
(Object Modeling Technique) methods )
UML Diagrams
 Each UML diagram is designed to let developers
and customers view a software system from a
different perspective and in varying degrees of
abstraction
 Use Case Diagram
 Class Diagram
 Interaction Diagrams (Sequence Diagram / Collaboration
Diagram )
 State Diagram
 Activity Diagram
 …
Source:
http://en.wikipedia.org/wiki/Unified_Modeling_Language
Use-Case Diagrams
 Relationship between actors and use cases;
capturing user requirements.
 Actors: An actor is represents a user or another
system that will interact with the system you are
modeling
 Use cases: an external view of the system that
represents some actions the user might perform in
order to complete a task
Use-Case Diagrams
 When to use:
 Use cases are used in almost every project. 
 How to Draw
 Simplest
Use-Case Diagrams: Example

 A user placing an order with a sales

company might follow these steps :
 Browse catalog and select items.
 Call sales representative.
 Supply shipping information.
 Supply payment information.
 Receive conformation number from salesperson.
Use-Case Diagrams: Example
 The salesperson
could also be included
in this use case
diagram because the
salesperson is also
interacting with the
ordering system.
Use-Case Diagrams
 Relationships in Use Cases
 Include: a use case includes the
functionality described in another use
case. (directed arrow having a dotted shaft,
labeled <<include>> )
<<include>>
Use-Case Diagrams
 Extend: the child use case, the parents use
case.
<<extend>>

The "Perform Pathological Tests" use case

is a specialized version of the generic
"Perform medical tests" use case.
Use-Case Diagrams
 Generalizations: The child use case in the
generalization relationship has the
underlying business process meaning, but is
an enhancement of the parent use case.
(directed arrow with a triangle arrowhead )
you can replace any occurrence of
the "Store patient records (paper file)"
use case in the business flow of your
system with the "Store patient records
(computerized file)" use case without
impacting any business flow.
Class diagram
 Class diagrams are widely used to describe
the types of objects in a system and their
relationships
 Each class is represented by a rectangle
subdivided into three compartments
 Name
 Attributes
 Operations
Class diagram
 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)
Account_Name Name
- Customer_Name
- Balance
Attributes
+addFunds( )
Operations
+withDraw( )
+transfer( )
Class diagram
 There are two kinds of Relationships
 Generalization (parent-child relationship)
 Association (student enrolls in course)

 Associations can be further classified

as
 Aggregation
 Composition
 Generalization

Supertype Example: Customer

Regular Loyalty
Customer Customer

Subtype1 Subtype2
-Inheritance is a required feature of object orientation
-Generalization expresses a parent/child relationship among related classes.

-Used for abstracting details in several layers

Association
 Associations represent static
relationships between classes.
 (association names  filled arrow )
 (Place roles near the end of an association)
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.”
Association: Composition and Aggregation

 Association: Models the part–whole relationship

 Composition : (filled diamond)
“Every part may belong to only one whole, and If the
whole is deleted, so are the parts”
 Aggregation : (hollow diamond).
“It is a specific kind of Container-Containee
relationship”
Aggregation vs. Composition

 Composition is really a strong form of association

 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 association, but may not be
essential to it. They may also exist independent of the
aggregate. e.g. Employees may exist independent of the
team.
Association: Composition and Aggregation
Composition : (filled diamond)
Aggregation : (hollow diamond).
 Interaction Diagrams
 Interaction diagrams are used when you want to model the
behavior of several objects in a use case

 UML supports two types of interaction diagrams

 Sequence diagrams
Sequence diagrams generally show the sequence of events that occur

 Collaboration diagrams
Collaboration diagrams demonstrate how objects are statically connected.
Sequence Diagram:Object interaction

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

Condition: indicates when a

Asynchronous
message is sent. The message is
sent only if the condition is true. Transmission
delayed

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

Self-Call
Sequence Diagram(make a phone
call)

Caller Phone Recipient

Picks up

Dial tone

Dial

Ring notification Ring

Picks up

Hello
 Sequence Diagrams – Object Life Spans
 Creation
A
 Create message

 Object life starts at that point

Create
 Activation B
 Symbolized by rectangular stripes

 Place on the lifeline where object

is activated.
 Rectangle also denotes when

object is deactivated.
 Deletion Activation bar
X
Return
 Placing an ‘X’ on lifeline Deletion
 Object’s life ends at that point Lifeline
Sequence Diagrams – Object Life Spans
 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
Collaboration diagrams are equivalent to sequence diagrams. All the features of sequence
diagrams are equally applicable to collaboration diagrams

Use a sequence diagram when the transfer of information is the focus of attention

Use a collaboration diagram when concentrating on the classes

State Diagrams (Billing Example)

State Diagrams show the sequences of states an object

goes through during its life cycle in response to
stimulin, together with its responses and actions;
an abstraction of all possible behaviors.
Start End
Unpaid Paid
Invoice created payin Invoice destroying
g
State Diagrams (Traffic light example)

Traffic Light Start

State
Transition Red

Yellow

Green

Event
Activity Diagrams
 Activity diagrams describe the
workflow behavior of a system.
 similar to state diagrams because
activities are the state of doing something

 Activity diagrams can show activities

that are conditional or parallel.
Activity Diagrams
Conclusion
 UML is a standardized specification language for object
modeling
 Several UML diagrams:
 Use-case diagram: a number of use cases (use case models the
interaction between actors and software)
 Class diagram: a model of classes showing the static
relationships among them including association and
generalization.
 Sequence diagram: shows the way objects interact with one
another as messages are passed between them. Dynamic model
 State diagram: shows states, events that cause transitions
between states. Another dynamic model reflecting the behavior
of objects and how they react to specific event
 Activity diagram: describes the state of activities by showing the
sequence of activities performed.
UML Resources
 Books
 Martin Fowler, Kendall Scott: UML Distilled, Addison-Wesley
2000
 Grady Booch, et al: The Unified Modeling Language User
Guide, Addison-Wesley 
 James Rumbaugh, et al: The Unified Modeling Language
Reference Manual,  Addison-Wesley Ivar Jacobson, et al:
Unified Software Development Process, Addison-Wesley
 Online UML Resources
 Rational Software –
UML Resource Center (http://www.rational.com/uml/index.jsp),
UML Quick Reference
(http://www.rational.com/uml/resources/quick/index.jsp),
UML Whitepapers
(http://www.rational.com/uml/resources/whitepapers/index.jsp)
Recommended Books
(http://www.rational.com/uml/reading/index.jsp)
UML Cafe
(http://cafe.rational.com/HyperNews/get/hn/umlcafe.html)
UML Resources
 The Object Management Group -- UML resource Page
(http://www.omg.org/technology/uml/index.htm), UML Tutorial
(http://cgi.omg.org/news/pr97/umlprimer.html)
 The UML Center -- UML Information
(http://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/r
esources.htm#1)
UML Events
(http://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/r
esources.htm#evnts)
 The UML Zone -- UML FAQ
(http://www.uml-zone.com/umlfaq.asp)
UML Q&A
(http://news.devx.com/cgi-bin/dnewsweb.exe?
utag=&group=vb.oop&xrelated=8577&cmd_related.x=69&cmd_r
elated.y=6)
 GDpro -- UML Center(http://www.gdpro.com/uml_central.html)
UML Dictionary(http://softdocwiz.com/UML.htm)