Unified Modeling Language

• The Unified Modeling Language (UML) is used to specify,

visualize, modify, construct and document
the artifacts of an object-oriented software intensive
system under development. UML offers a standard way
to visualize a system's architectural blueprints, including
elements such as:
– Actors
– Business processes
– Components
– Activities
– Reusable software components
 UML Diagrams Classification
• Behaviour Diagrams : A type of diagram that depicts
behavioural features of a system or business process. This
includes Activity, State Machine, and Use Case Diagrams as
well as the Four interaction Diagrams
• Interaction Diagrams : A subset of behaviour diagrams which
emphasize object interactions. This includes Communication,
Interaction Overview, Sequence and Timing diagrams.
• Structure Diagrams : A type of diagram that depicts the
elements of a specification that are irrespective of time. This
includes Class, Composite Structure, Component,
Deployment, Object, and Package Diagrams
 Use Case Diagram
• A use case is a set of scenarios that describing
an interaction between a user and a system. 
• A use case diagram displays the relationship
among actors and use cases. 
• The two main components of a use case
diagram are use cases and actors.
• An actor is represents a user or another system that
will interact with the system you are modeling. 
• A use case is an external view of the system that
represents some action the user might perform in
order to complete a task.
 Use Case Relationships
The Relationships between Use Cases & Actors
• Associate Relationship / Communicate Relationship

Registration
 The Relationships between Use Cases
• Include : The base use case explicitly incorporates the
behavior of another use case.

de>> Check Inventory

cl u
<< i n

Oder Confirmation << i

ncl
ude
>>
Get Credit
Approval
• Extend : Shows the optional behavior of a use case

<<extend>>
Place Order Request Catalogue
• Generalization : Child use case inherits

Pay by Cash

Pay Bill

Pay by Credit Card

 Class Diagram
• Class diagrams are widely used to describe the
types of objects in a system and their
relationships.
• Classes are composed of three things. Below is
an example of a class.
 Object Diagram
• Depicts actual object instances and their relationships
at a point in time
• Use a notation similar to class diagrams
• Objects in a object diagram can be named using 3
conventions as follows,

1. Object Name : Class Name 2. Object Name

3. : Class Name
 Sequence Diagram
• Models the sequential logic, in effect of the
time ordering of ‘messages’ between
classifiers
• Depicts the sequence of actions that occur in a
system
S1 :Student BIT : Course

get courseDetails()
 Collaboration Diagram
• Shows the instances of classes, their
interrelationships, and the message flow
between them
• Focus on the structural organization of objects
that send and receive messages
• Also called as Communication Diagram
 State Diagram
• Describes the states of an object or
interaction may be in, as well as the
transitions between states.
• Also called as “State Chart Diagram”, “State
Machine Diagram”, “State Transition
Diagram”
 Activity Diagram
• Depicts high level business processes,
including data flow, or to model the logic of
complex logic within a system
• Graphical representations of workflows of
stepwise activities and actions with support
for choice, iteration and concurrency
 Insert Card
Enter Pin

Enter Amount Display Error Message

Release Cash Update Account

Print Receipt

Display Balance

Eject Card
 Component Diagram
• Depicts the components that compose an
application, system or enterprise.
• The components, their relationships,
interactions and their public interfaces are
depicted
 Oracle Database

Student Registration
Application
 Deployment Diagram

• Shows the execution architecture of the

system.
• This includes nodes, either hardware or
software execution environments as well as
the middleware connecting them