Object Modeling
UML
1
UML - Unified Modeling
Language
What is the UML?
The UML is a common diagrammatic language
developed by Rational
([Link]
with the support of all the big computer
companies. It is now maintained by the Object
Management Group. Rational was bought by
IBM who now provides many tools .
2
UML cont.
Why use the UML?
• Picture can express a lot of ideas in a quick
way.
• UML is a standard way to draw various views
of a piece of software: the user's view, the
architecture, the internal structure of the
software, the source code, and the hardware
involved.
• UML is becoming valuable in the job market .
3
UML cont.
• UML is an industry standard language for
specifying, visualizing, constructing, and
documenting the artifacts of system software.
• UML uses graphical notations to express the OO
analysis and design of software projects
• UML is not a programming language but tools can
be used to generate code in various languages using
UML diagrams. 4
Advantages of Unified Modelling
Language(UML)
• Advantages:
1. Providing the basic for understanding the modelling
language.
2. Easy to learn.
3. Visual modelling language.
4. Independent of other programming language.
5. Encourages the growth of the OO tools market.
6. Managing complex projects.
7. UML diagrams are not only made for developers but
5
also for business users, common people, and anybody
interested to understand the system
Object Modeling
• Object Modelling Approach describes the use of
methodologies and diagramming notations that are
different from the ones used for data modelling and
process modelling.
• Object Modelling is a technique for defining business
requirements for a new system by identifying objects
within the systems environment and the relationships
6
between those objects.
Introduction to Object Oriented Approach
• The object oriented approach to system development is
based on the concept that objects exists within the
system's environment.
• An Object
1. Is something that is or capable of being seen,
touched or both, or otherwise sensed.
2. Users need to store data and associate behaviour.
7
Introduction to Object Oriented Approach
• The types of Objects may include:
• Person
Example: an employee, customer, vendor, and
student
• Place
Example: warehouse, building, and room.
• Thing
Example: product, and equipment
• Event
Example: order, payment, invoice, registration,
and reservation. 8
Introduction to Object Oriented Approach
• The data term in object definition refers to what are called
Attributes.
• Attributes: are the data that represents characteristics of
an object.
•Behaviour: last part in the object definition refers to the
behaviour of an object.
1. refers to things that the object can do and that
corresponds to functions that act on the object’s data
(attributes).
2. In object oriented, object’s behaviour is referred to as a 9
method, operation, or service.
Introduction to Object Oriented Approach
• Examples on Behaviours:
• Behaviours are associated with a person:
person can walk, jump, talk, sleep, eat,
and…etc…..
• Behaviours are associated with a phone:
phone that are voice activated,
answer, dial, hang up, and…etc…
• Behaviours are associated with a door:
door can open, lock, unlock, and…etc… 10
UML DIAGRAMS
• UML Diagrams: are a graphical representation of
a set of elements, connected graph of things and
relationships.
• There are two major kinds of UML diagram:
1. Behavioral diagrams :
2. Structural diagrams :
11
UML Diagrams
Behavioral diagrams :
• Used to show the system functionality and how
the system evolves over time (responds to
requests, events, etc.)
• Define the dynamics of a system„
• show the dynamic behavior of the objects in a
system, which can be described as a series of
changes to the system over time.
• To model: interactions among objects, states
changes within a model as it 'executes' over time.
12
UML Diagrams
Structural diagrams :
• Used to describe the building blocks of the system,
features that do not change with time.
• show the static structure of the system and it's parts
on different implementation levels and how they are
related to each other.
• To model: classes, objects, interfaces and physical
components and the relationships & dependencies
between those elements.
13
UML Diagrams Views
Behavioral Diagrams
▪ Use Case Diagram
▪ Sequence Diagram
▪ Activity Diagram
▪ State chart Diagram
▪ Collaboration Diagram
Structural diagrams
▪ Class Diagram
▪ Object Diagram
▪ Component Diagram
14
▪ Deployment Diagram
Thank you
15