Introduction to UML Modeling Concepts
Uploaded by
ScribdTranslationsIntroduction to UML Modeling Concepts
Uploaded by
ScribdTranslationsChapter I: Introduction to UML
I-Introduction :
The objective of this course is to introduce you to the concepts of modeling computer systems.
to say systems in which the software part is predominant.
This course introduces object-oriented modeling of computer systems using the language
(graphic) UML.
The object-oriented approach is a way of tackling a problem and breaking it down into smaller sub-problems.
We start by researching the objects of the system and then their interactions.
II- Basic concepts:
1- General definitions
Domain: field of application
modeling element: representation of an abstraction from the problem domain
subject:
Entity with a well-defined boundary and identity that encapsulates a state and behavior
system: a set of connected and organized objects to achieve a specific goal
A model is an abstraction of reality that allows for a better understanding of the system. It is therefore
a simplification of the real world.
Life cycle: stages of the development of a computer system
Analysis: understanding the needs of the system
Conception: describes the solution (how the problem is solved), conception = THE-HOW
Modeling: synonym of analysis, and by extension, development of models (including in
conception
Specification: exhaustive description of a modeling element
Diagram: graphical representation of modeling elements
Notation: set of signs and symbols that make up the UML language
2-Definition of UML (Unified Modeling Language)
UML is an object modeling language, it allows to formalize a set in the form of diagrams.
concepts that can be used during all phases of the software life cycle analysis (definition of
needs, specifications, general design and detailed design.
Unlike MERISE, which is a modeling method with which a global study can be
Led for the life cycle of a project, UML is merely a language and not a method; it must be
accompanied by an object development process to conduct a comprehensive study.
3-History of UML:
The methods used in the 1980s to organize imperative programming (Merise) were
based on the separate modeling of data and processes.
When object-oriented programming gained importance in the early 1990s, the need for a
the method that suits him becomes evident. More than fifty methods appeared between 1990 and 1995
(Booch, Class-Relation, Fusion, HOOD, OMT, OOA, OOD, OOM, OOSE,…) but none succeed
to impose itself. In 1994, consensus was formed around three methods:
OMT by James Rumbaugh (General Electric) provides a graphical representation of the aspects
static, dynamic and functional of a system;
-OOD by Grady Booch, defined for the Department of Defense, introduces the concept of packaging
- OOSE by Ivar Jacobson (Ericsson) is based on analyzing the description of user needs (use cases)
of use).
The three gurus who each ruled over one of the three methods agreed to define a
a common method that would bring together their respective contributions (they are nicknamed since then "the Amigos"). UML is
born from this effort of convergence. The adjective unified is there to indicate that UML unifies, and thus replaces.
1
The diagram below shows the evolution of UML:
4- UML Diagram:
A UML diagram is a graphical representation that focuses on a specific aspect of the model.
Each type of UML diagram has a structure and conveys a specific semantics.
Combined, the different types of UML diagrams provide a comprehensive view of the static aspects and
dynamiques d'un système. Les diagrammes permettent donc d'inspecter un modèle selon différentes
perspectives and guide the use of modeling elements (object concepts), as they possess a
structure.
III- The different UML diagrams:
UML 2.3 proposes 14 types of diagrams (9 in UML 1.3) representing as many distinct views for
Represent specific concepts of the information system. They are divided into two groups:
Structural diagrams or static diagrams (UML Structure)
. class diagram
. Object diagram
. component diagram
. deployment diagram
. package diagram
. Composite structure diagram
Behavioral diagrams or dynamic diagrams (UML Behavior)
. use case diagram
. Activity diagram
. State machine diagram
. Interaction diagrams
. sequence diagram
. Communication diagram
2
. global interaction diagram
. Timing diagram
There are UML works that divide UML modeling into the three axes below, unlike the
the diagram below, the dynamic axis is divided into two axes namely, the functional axis and the axis
dynamic, below is the representation.
3
IV- The phases of modeling:
Below is the V-cycle diagram
The diagram presents the V model of software development. The V model has already been introduced to you.
familiar because you met it for procedural programming. It is also used in object-oriented
The computerization begins with the establishment of the specifications with the client followed by the analysis which
is intended to model the problem. Then, the design models the technical solution; it is followed by the
implementation of the software in accordance with the solution.
The right part consists of verifying the software built through a series of tests and the acceptance by the client.
of the finished product.
III- The analysis phase
The UML analysis phase is conducted as follows:
1- The description of use cases.
For each use case, create from one to n interaction diagrams (the interaction diagrams of
sequence first to decide on the features with the client; then, move on to the diagrams
collaboration to continue the analysis with the project team.
3- Each collaboration diagram corresponds to a draft class diagram. Specify.
when creating a class, to which package it belongs.
4- Summarize the class diagrams for a given package.
5- For each class in the class diagram, create a state-transition diagram (optional).
IV- The contributions of visual modeling:
Visual modeling:
- Allows for a better understanding of needs
- Facilitate the understanding of the problem
- Facilitate communication between people (clients, domain experts, analysts, designers,
...)
- Improve the readability of design diagrams
- Prepare the documentation and the programs
- Facilitates maintenance