Introduction to UML

 Modeling using UML

OOAD
1
What is modeling?
•Modeling is a simplified representation of reality
•It involves providing a blueprint of a system

Why Model?
•Visualize the system ‘as-is’ and ‘to-be’
•Document the design decisions
•Provide a template for constructing a system
•To better understand the system we are developing
•Describe the structure or behavior of the system
•Experiment by exploring multiple solutions

Modeling & benefits 2

• The model you create influences how the problem is
attacked and how the solution is shaped
• Every model may be expressed at different levels of
precision
• The best models are connected to reality
• No single model is sufficient

Modeling
principles 3
• UML= Unified Modeling Language
• A language for visualizing, specifying, constructing and
documenting artifacts of software systems.
• UML is a modeling language, not a methodology or process
• Fuses the concepts of the Booch, OMT, OOSE methods
• One can model:
• Distributed web-based system
• Real-time embedded system
• Enterprise information systems
• Or any software based system

What is UML 4
• In 1996 the Unified Modeling Language was introduced as
UML 0.9 and then 0.91
• Input was obtained from many, including TI, IBM, Microsoft,
Oracle, and HP.
• This led to UML 1.0 in 1997
• Eventually, the semantics and flexibility was improved
resulting in UML 2.0 in 2003

Birth of UML 5
Three basic building blocks
•Elements: main components of the model
•Relationships: they tie elements together
•Diagrams: mechanisms to group interesting collections of
elements and relationships
They will be used to represent complex structures

UML Building
blocks 6
 • Diagrams
• Elements
• Class diagrams
• Structural elements • Object diagrams
• Behavioral • Use case diagrams
• Grouping • Behaviour diagrams
• Annotational • Implementation diagrams
• Relationships
• Dependency
• Association
• Generalization

UML Building
• Realization

blocks 7
• The nouns of UML Model; usually the static parts of the
system in question

Structural
elements 8
Structural
elements… 9
Structural
elements… 10
• The verbs of UML Models; usually the dynamic parts of the
system in question. Represent behavior over time & space
Construct Description
Interaction some behaviour constituted by messages exchanged
among objects; the exchange of messages is with a
view to achieving some purpose.

State machine behaviour that specifies the sequence of “states” an

object goes through, during its lifetime. A “state” is a
condition or situation during the lifetime of an object
during which it exhibits certain characteristics and/or
performs some function.

Behavioral
Element 11
• The organizational part of the UML Model; provides a
higher level of abstraction
• Organize diagrams
• Primary kind of grouping and decomposition
• Package - a general-purpose element that comprises
UML elements - structural, behavioral or even grouping
things. Packages are conceptual groupings of the system
and need not necessarily be implemented as cohesive
software modules

Grouping element 12
• The explanatory part of the UML Model; adds
information/meaning to the model elements.
• Note - a graphical notation for attaching constraints
and/or comments to elements of the model.

Annotation
Elements 13
• Articulate the meaning of the links between things on the
UML Model
Relationship description
Dependency semantic relationship where a change in one thing
(the independent thing) causes a change in the
semantics of the other thing (the dependent thing)

Association a structural relationship that describes the

connection between two things.

Generalization a relationship between a general thing (called

“parent” or “superclass”) and a more specific kind
of that thing (called the “child” or “subclass”), such
that the latter can substitute the former

14
Relationships
Relationship Description
Realization a semantic relationship between two things wherein
one specifies the behaviour to be carried out, and the
other carries out the behaviour.
Eg
a collaboration realizes a Use Case”
the Use Case specifies the behaviour (functionality) to
be carried out (provided), and the collaboration
actually implements that behaviour.

Relationships… 15
• The graphical presentation of the model.
Represented as a connected graph - vertices
(things) connected by arcs (relationships).
• UML includes nine diagrams - each capturing
a different dimension of a software-system
architecture
• Class Diagram • Statechart Diagram
• Object Diagram • Activity Diagram
• Use Case Diagram • Component Diagram
• Sequence Diagram • Deployment Diagram
• Collaboration Diagram

16
Diagrams
Questions?

17