The Unified Modeling Language
Pournima Sonawane
Department of Electronics
University of Limerick
The Unified Modeling Language
The UML was conceived during the 90’s by Rumbaugh, Grady
Booch and Ivar Jacobson. In 1997 Object Management
Group(OMG) standardized the UML.
The UML is a language for specifying, visualizing, constructing
and documenting the artifacts of a software system.
The UML is a modeling language requiring vocabulary and the
rules for combining words for the purpose of communication
A Model
Models
Help us to visualize a system as it is or as we want it to
be.
Permit us to specify the specific needs or requirements
concerning the system.
Give us a template that guides us in constructing a
system.
Document the decisions we have made.
Principles of Modeling
The choice of the model
The level of abstraction
Connections to reality
Independent views of the system
Modeling
UML modeling consists of nine diagrams to model a software
system.
Each UML diagram is designed to let developers and
customers view a software system from a different
perspective and in varying degrees of abstraction
There are two types of Models exists in UML:
Static
Behavioral
Models State
State
Diagrams
Class
Diagrams
Use Case Diagrams
Use Case
Diagrams State
Use Case Use Case
Diagrams State
Diagrams
Use Case
Diagrams Diagrams Object
Diagrams
Sequence
Diagrams Diagrams
Diagrams
Scenario State
Scenario
Diagrams State
Diagrams
Collaboration
Diagrams Component
Diagrams
Models
Diagrams Diagrams
Scenario Component
Scenario
Diagrams
Component
Diagrams
Deployment
Statechart
Diagrams Diagrams
Diagrams Diagrams
Activity
Diagrams
Static Models
Static model shows the things or entities in a system and the
relationships between them.
Class Diagram – shows how the different entities relate to
each other
Object diagram – represents instances of class
Component diagram – provides a physical view of the system
Deployment diagram – shows how a system will be physically
deployed in the hardware environment
Behavioral Models
Behavioral Model tells us, how the interactions occur within the
system.
Use case diagrams – organizes the behaviours of the system
Sequence diagram – focused on the time ordering of messages
Activity diagrams – focused on the structural organization of
objects that send and receive messages
Statechart diagram – focused on the changing state of a system
Collaboration diagram – focused on the flow of control from
activity to activity
A Good Model
Characteristics of good models are:
A well-formed model should be semantically consistent and
in harmony with all its related models.
Models during development tend to evolve and hence the
models should be flexible to accommodate changes.
Wrap Up
The UML has wide applications in the software-
intensive systems.
Biggest advantage of using UML is non-propriety
nature.
The End
Thank You for Attention!