NOIDA INTERNATIONAL

UNIVERSITY

SOFTWARE ENGINEERING

NAME : SWATI SHARMA

ROLL NO : BT/CS/1401/006

MODELING
LANGUAGE

UNIFIED

L
M

CONTENTS :

What is UML
History of UML
Object oriented concepts
Overview of UML diagrams
Class diagram
Object diagram
Use case diagram
State diagram

What is UML ?
UML is a standard language for specifying ,
visualizing , constructing and documenting the
artefacts of the software systems.
UML is pictorial language used to make software
blueprints.
UML is not a language(c , c++ , java .) and does
not have a set of command keywords.
UML is basically a presentation method ,
providing for different views to detail the
software system under design.

History of UML :

Industrialization

June 99

Public
Feedback

OMG accepts the UML as the

official industrial standard for
software modeling notations
as 17th Nov. 97
Submission to OMG, Sept 97
Submission to OMG, Jan 97
Beta version OOPSLA 96
www June 96
OOPSLA 95

Method Wars
Various methods

UML 1.3

Standardization

UML 1.1
Unification

UML 1.0
UML 0.9
Unified Method 0.8
Booch 93
Booch 91

Fragmentation

OMT-2
OMT -1

OOSE

Object Oriented Concepts :

UML can be described as the successor of object oriented
analysis and design.
UML diagrams are representation of object oriented concepts
only.
OBJECT : objects represent an entity and the basic building
block.
CLASS : class is the blueprint of an object.
ABSTRACTION : abstraction represents the behaviour of an
real world entity.
ENCAPSULATION : it is the mechanism of binding the data
together and hiding them from outside world.
INHERITANCE : it is the mechanism of making new class
from existing one.
POLYMORPHISM : it defines the mechanism to exists in
different forms.

Overview of UML diagrams:

STRUCTURAL :

BEHAVIORAL :

It captures the static features

Of a system.
It contains following diagrams :
1.CLASS
2.OBJECT
3.COMPONENT
4.DEPLOYMENT
5.COMPOSITE STRUCTURE

It captures the dynamic

features of a system.
It contains following diagrams:
1. ACTIVITY
2. USE CASE
3. INTERACTION
4. STATE

ARCHITECTURAL :
It contains both structural and behavioral modelling
and can be defined as blueprint of entire system.
It contains package diagram.

Class Diagram :
Class diagrams are the most common diagrams used in
UML. Class diagram consists of classes , interfaces ,
associations and collaboration.
It is generally used for development purpose.
STUDENT
Public
Protected
Private

+name : string
#roll : integer
-section : string
+display()
-add()
-edit()
#delete()

NAME
ATTRIBUTES

OPERATIONS

CLASS DIAGRAM are used for :

Describing the static view of the system.
Showing the collaboration among the elements of
the static view.
Describing the functionalities performed by the
system.
Construction of software applications using
object oriented languages.

Object Diagram :
Object diagram can be described as an instance of
class diagram useful for exploring real world
examples of objects and the relationship between
them.
This static view is a snapshot of the system at a
particular moment.
The name of class underlined in object diagram
which makes it different from class diagram

OBJECT DIAGRAM are used for :

Making a prototype of a system
Reverse and forward engineering
Modelling complex data structure
Understanding the system from practical perspective.

Use
Case
Diagram
:
Use case diagrams are a set of use case , actors

and their relationship.

Use case diagrams are dynamic in nature there
should be some internal or external factors for
making the interaction.

ACTOR

USE CASE

Check ticket
availability
Pay fare amount
User

Admin
Book ticket
Fill personal and
travel details
Cancel ticket

Clerk

Refund money

USE CASE DIAGRAMS are used for :

Requirement analysis and high level design
Model the context of a system
Reverse and forward engineering

State Diagram :
It describes different states of a component in a a
system. These states are controlled by external or
internal events.
It describes the flow of control from one state to
another state.
States are defined as a condition in which an object
exists and it changes when some events is triggered.

STATE DIAGRAMS are used for :

To model reactive system
To model object states of a system
To identify events responsible for state changes
Forward and reverse engineering

Thank You