UML--Unified Modeling Language / English

Fidelcash 14 views 39 slides Jun 22, 2024
Slide 1
Slide 1 of 39
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19
Slide 20
20
Slide 21
21
Slide 22
22
Slide 23
23
Slide 24
24
Slide 25
25
Slide 26
26
Slide 27
27
Slide 28
28
Slide 29
29
Slide 30
30
Slide 31
31
Slide 32
32
Slide 33
33
Slide 34
34
Slide 35
35
Slide 36
36
Slide 37
37
Slide 38
38
Slide 39
39

About This Presentation

Introduction to UML - Unified-Modeling-Language , Anglais Technique-2, Systems Analysis and design


Slide Content

ANGLAIS TECHNIQUE -2 / L2 LMD
GESTION INFORMATIQUE
PRESENTED BY L’Ir Fidel MUMBERE
ASSISTANT-1
Mumbere Vulere Fidel
Contact:
+243973738945
E-mail: [email protected]

INTRODUCTION TO UML
Lecture # 1
Section de Gestion Informatique
Institut Superieur de Commerce (ISC -Beni)
Prepared by Mr. Fidel Mumbere,
based on the book Applying UML and Patterns (3rd ed.)
by C. Larman (2005).
MODELLING AND SIMULATION, 2024

COURSE OUTLINE
COURSE INFORMATION
Aims And Objectives
Assessment
Books
UML
Structure Diagrams
Behaviour Diagrams
Interaction Diagrams
MODELLING
Use Case
SUMMARY

AIMS AND OBJECTIVES
Aims
To understand the process of modelling real world problems and systems using UML,
Course Objectives
To understand the software development process, including requirement specication,
analysis, design, implementation and testing.
To learn and use various methodologies in software development,
To understand the process of modelling real world problems and systems using UML,
To develop skills on object oriented software development (OOSD).

ASSESMENT
Assignment:
Home works-50%
Exam:
Final exam -50%

***RÈGLES D’ENSEIGNEMENT***
Conduite dans la classe:
Il faut être polie et respectueux envers tout le monde. Eteindre les téléphones cellulaires ou bien les mettre sou
vibreurs.
L‘utilisation des téléphones pendant l‘examen ou l‘interrogation résultera par une réduction de la note finale.
Les retards repetitifs annulera la participation au cours chaques etudiant dois avoir les notes de cours
Participation:
Vous devez participer à toutes les sessions dans l‘auditoire. Si vous serez absent, notifier l‘enseignant ou le chef
de promotion.
C‘est votre responsabilité d‘avoir une copie des explications du cours de votre collègue qui était au cours pour
que vous soyez en « jour ».
Vous devriez planifier d‘être en classe en temps et y rester pendant tout le cours. Si vous arrivez en retard ou bien
cherchez à sortir ; faites cela sans bruit pour ne pas déranger les autres.
Tricherie :
Il ne faut pas tricher. Par exemple, il ne faut pas parler ou consulter d‘autres étudiants pendant
l‘examen ou bien utiliser des matériels refusés.
Si vous êtes attrapés vous aurez une réduction total de votre cote.

BOOKS/RESOURCES
Applying UML and patterns by Craig Larman
Object-Oriented Software Engineering -a use case
driven approach (revised edition) by Ivar Jacobson
UML Distilled (2nd Edition) by Martin Fowler
Software Engineering (4th Edition) by Ian
Sommerville
Developing Applications with Java and UML by
Paul R and Reed Jr

What is UML?
UML stands for Unified Modelling Language.
An industry standard modelling language for object-
oriented software engineering.
Developed in the mid-1990's and standardised in 1997
(UML 1.1).
UML 2.x is the current revision in use (we will focus on
UML 2.0, revision from 2005).
UML includes a set of graphic notation techniques to
create visual models of object-oriented software-
intensive systems.

LIST OF OBJECT-ORIENTED PROGRAMMING LANGUAGES
Languages designed mainly for object-oriented programming :
C++
Java
C#
Python
Languages with some object-oriented features:
Visual Basic
Fortran
Perl
PHP

List of Unified Modelling Language tools

UML 2.0 defines thirteen types of diagrams:
divided into three categories:
Six diagram types represent static application
structure;
Three diagram types represent general types of
behaviour;
Four diagram types represent different aspects of
interactions.

Depicts the components that compose an application, system, or enterprise. The
components, their interrelationships, interactions, and their public interfaces are
depicted.

Describes the states an object or interaction may be in, as well as the transitions
between states. Formerly referred to as a state diagram, state chart diagram, or a
state-transition diagram.