UML

2thyear Engineer Cycle

GLSID & IIBDCC
2020/2021

Prof. Bouchra BOUIHI

 1.
General Introduction

2
 Introduction
Programming technologies have continued to evolve since the emergence of
computers. This evolution is strongly demanded to meet an incessant need for
to produce more complex applications.

The main advancement of the last twenty years lies in object-oriented programming.
object (P.O.O.).In the face of this new programming paradigm, many methods
were born like Booch, OMT ...

In this context and in the face of the proliferation of new design methods
object-oriented", the Object Management Group (OMG) aimed to define a
standard notation usable in object-based software development.

This is how UML appeared...

3
 Definition

“
The Unified Modeling Language, in English Unified Modeling
UML, is a graphical modeling language based
of pictograms designed to provide standardized templates for
visualize the design of a system. It is commonly used
in software development and object-oriented design

4
HISTORY
5
UML is the result of the merging of previous object modeling languages: Booch, OMT, OOSE.
Mainly stemming from the work of Grady Booch, James Rumbaugh, and Ivar Jacobson. Because each
the method has its own means of representation (graphic, diagram, plan, flowchart).

Problem: incompatibility, redundancy, different notation or terminology

1997
OMG

UML is the proposed solution to have a unified language adopted as a standard by

The Object Management Group (OMG). UML 1.0 was standardized in January 1997.
6
 In 2020

Maps

7
 UML Versions
2.5.1 December 2017

2.4.1 July 2011

2.3 May 2010

2.2 January 2009

2.1.2 October 2007

2.0 July 2005

1.5 March 2003

1.4 September 2001

1.3 February 2000

1.2 July 1999

1.1 December 1997

8
 UML in action
UML is not a method. It is a modeling language to provide a
unified object-oriented design patterns in order to:
§ Visualize
Each graphic symbol has a semantics.
§ Specify
In a precise and complete manner, without ambiguity.
§ Build
A part of the class code can be generated automatically.
§ Documenter
The different diagrams, notes, constraints, and requirements are stored in
a document. 9
 What is a model?

“
A model is an abstraction of reality. It defines a boundary between
the reality and the perspective of the observer. It is not 'the reality', but
a very subjective view of reality. Although a model does not represent
an absolute reality, a model reflects important aspects of the
reality, it therefore provides a fair and relevant view

10
 Importance of modeling

▷ The model can replace a long textual description with a diagram.

a diagram easier and faster to interpret.

▷ Code alone is not enough. Clear documentation is needed.

and not ambiguous to ensure good communication between the
different stakeholders.

▷ Modeling allows breaking an application into fragments.

manageable.

11
UML is a communication tool.

Performance of its graphical notation

It allows one to express oneself clearly using object concepts.

Limit ambiguities
Speak a common language, with precise vocabulary.

Independence
It is independent of programming languages, of the domain
of application, of the development process, etc., which makes it a
universal language. 12
UML is a communication tool

13
 The categories of UML diagrams

UML diagrams are all created based on the needs of the users and
can be grouped according to the following two aspects:

ü The functional aspects: Who will use the software and for what purpose?
How should the actions take place? What information
will be used for that?

ü Aspects related to architecture: What will be the different components

software to use (database, libraries, interfaces, etc.)? On which
material each of the components will be installed?
14
The categories of UML diagrams

15
UML diagrams since UML 2.3

16
UML
Behavior Diagrams

17
 UML: Behavior Diagrams
Behavior diagrams encompass:

qUse case diagram.

q State transition diagram (state machine diagram).
q Activity diagram

18
 UML: Behavior Diagrams

Use case diagram

use case diagram

It represents the interactions between

the system and the actors (interveners)
externals to the system), that is to say
all the features that must
provide the system.

19
 UML: Behavior Diagrams

State-transition diagram
state machine diagram

It represents in the form of a machine at

finite states the behavior of the system
or its components.

20
 UML: Behavior Diagrams

Activity diagram
(activity diagram)

It represents in the form of flow

or chaining activities the
behavior of the system or of
its components

21
UML
Static Diagrams

22
 UML: Static Diagrams
Static diagrams or structure diagrams
diagrams) gather:
qClass diagram.
qObject diagram.
qComponent diagram.

qDeployment diagram.
qPackage diagram.

qComposite structure diagram.

q Profile diagram

23
 UML: Static Diagrams

Class diagram
(class diagram)

It represents the intervening classes

in the system.

24
 UML: Static Diagrams

Object diagram
(class diagram)

It represents objects that are

instances of classes and their links for
give the states of these objects in a
execution context.

25
 UML: Activity diagrams

Component diagram
(component diagram)

It represents the
software components of
point system
physical views, such as they
are implemented
(files, libraries,
databases...)

26
 UML: Static Diagrams

Deployment diagram
(deployment diagram)

It represents elements
equipment (computers, peripherals,
networks, storage systems...) and the
way in which the components of the
systems are installed on these
material elements and interact
between them.

27
 UML: Diagrammes Statiques
Package Diagram
(package diagram)
It represents dependencies between packages (a package being a container
logic that allows grouping and organizing elements in the UML model
that is to say between the sets of definitions.

28
 UML: Static Diagrams

Composite structure diagram

(composite structure diagram)

It is represented in the form of a box

white relations between components
of a class (since UML 2.x).

29
 UML: Static Diagrams

Profile diagram
(profile diagram)

This diagram provides a

representation of concepts
used in the definition of
profiles (packages, stereotypes,
profile applications, etc.)

30
UML
Dynamic Diagrams

31
 UML: Dynamic Diagrams
Dynamic diagrams or interaction
diagrams) bring together:

qDiagramme de séquence (sequence diagram).

qCommunication diagram.

qGlobal interaction diagram (interaction overview diagram).

qTiming diagram.

32
 UML: Dynamic Diagrams

Sequence diagram
(sequence diagram)

Sequential representation
of the course of the treatments and of the
interactions between the elements of
system and/or its actors.

33
 UML: Dynamic Diagrams

Communication diagram
(communication diagram)

Simplified representation of a sequence diagram

focusing on message exchanges between objects (since UML 2.x).

34
 UML: Dynamic Diagrams

Global interaction diagram

(interaction overview diagram)

Representation of possible sequences between the scenarios

previously identified in the form of sequence diagrams.

35
 UML: Dynamic Diagrams

Time diagram
(timing diagram)

Representation of variations
from a data during the
temps (depuis UML 2.3).

36
UML in practice

37