Universit´ du Littoral Cˆte d’Opale e o
L3 Info

M´thode de e Conception
Orient´e Objet e MCOO – Diagrammes UML

M´thode de e Conception
Orient´e Objet e Introduction ` UML a A. Lewandowski

A. Lewandowski

Pr´sentation des diff´rents diagrammes e e

[Vue Fonctionnelle]

case might require simultaneous (concurrent) action by two separate actors (e.g., in launching a nuclear missile) or it might require complementary and successive actions by the actors (e.g., one actor starting something and the other one stopping it).

Diagramme de cas d’utilisation
(Use case)
Notation

Diagramme

Introduction

Introduction

Concepts de base

Concepts de base
Diagramme
Structurel

Diagrammes UML
Introduction ` UML a Diagramme de cas d’utilisation Diagramme de classes
Diagramme de packages Diagramme d’objets
Diagramme de communication Diagramme de s´quence e
Diagramme d’activit´ e Diagramme d’´tats e Autres diagrammes

A use case is shown as an ellipse, either containing the name of the use case or with the name of the use case placed below the ellipse. An optional stereotype keyword may be placed above the name and a list of properties included below the name. If a subject (or system boundary) is displayed, the use case ellipse is visually located inside the system boundary rectangle. Note that this does not necessarily mean that the subject classifier owns the contained use cases, but merely that the use case applies to that classifier. For example, the use cases shown in Figure 16.5 on page 592 apply to the “ATMsystem” classifier but are owned by various packages as shown in Figure 16.7.

Diagramme de classes Diagramme de composants Diagramme de structure composite

Diagramme
Comportemental

Diagramme d'objets Diagramme de packages Diagramme d'activités Diagramme de déploiement Diagramme de cas d'utilisation

Introduction ` UML a Diagramme de cas
d’utilisation