Vous êtes sur la page 1sur 7

Aim: To study different types of UML Diagrams.

Theory:
Types of UML Diagrams.
UML 2 has many types of diagrams which are divided into two categories.
[3]
Some types
represent structural information, and the rest represent general types of behavior, including a few
that represent different aspects of interactions. These diagrams can be categorized hierarchically as
shown in the following class diagram:
[3]
These diagrams may all contain comments or notes explaining usage, constraint, or intent.
Structure diagrams.
Structure diagrams emphasize the things that must be present in the system being modeled. Since
structure diagrams represent the structure, they are used extensively in documenting the software
architecture of software systems. For example, the component diagram which describes how
a software system is split up into components and shows the dependencies among these
components.
Behavior diagrams.
Behavior diagrams emphasize what must happen in the system being modeled. Since behavior
diagrams illustrate the behavior of a system, they are used extensively to describe the functionality
of software systems. As an example, the activity diagram describes the business and operational
step-by-step activities of the components in a system.
Interaction diagrams.
Interaction diagrams, a subset of behavior diagrams, emphasize the flow of control and data among
the things in the system being modeled. For example, the sequence diagram which shows how
objects communicate with each other in terms of a sequence of messages.
Component Diagrams.
In the Unified Modeling Language, a component diagram depicts how components are wired
together to form larger components and or software systems. They are used to illustrate the
structure of arbitrarily complex systems.
Activity Diagram.
Activity diagrams are graphical representations of workflows of stepwise activities and actions
[1]
with support for choice, iteration and concurrency. In the Unified Modeling Language, activity
diagrams are intended to model both computational and organisational processes (i.e. workflows).
[2]
[3]
Activity diagrams show the overall flow of control.
Activity diagrams are constructed from a limited number of shapes, connected with arrows.
[4]
The
most important shape types:
rounded rectangles represent actions;
diamonds represent decisions;
bars represent the start (split) or end (join) of concurrent activities;
a black circle represents the start (initial state) of the workflow;
an encircled black circle represents the end (final state).
Arrows run from the start towards the end and represent the order in which activities happen.
Hence they can be regarded as a form offlowchart. Typical flowchart techniques lack constructs
for expressing concurrency
[citation needed]
. However, the join and split symbols in activity diagrams
only resolve this for simple cases; the meaning of the model is not clear when they are arbitrarily
combined with decisions or loops.
While in UML 1.x, activity diagrams were a specialized form of state diagrams,
[5]
in UML 2.x, the
activity diagrams were reformalized to be based on Petri net-like semantics, increasing the scope
of situations that can be modeled using activity diagrams.
[6]
These changes cause many UML 1.x
activity diagrams to be interpreted differently in UML 2.x
Sequence Diagram.
A 'Sequence diagram' is an interaction diagramthat shows how processes operate with one another
and in what order. It is a construct of aMessage Sequence Chart. A sequence diagram shows object
interactions arranged in time sequence. It depicts the objects and classes involved in the scenario
and the sequence of messages exchanged between the objects needed to carry out the functionality
of the scenario. Sequence diagrams are typically associated with use case realizations in the
Logical View of the system under development. Sequence diagrams are sometimes called event
diagrams, event scenarios
A sequence diagram shows, as parallel vertical lines (lifelines), different processes or objects that
live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order
in which they occur. This allows the specification of simple runtime scenarios in a graphical manner.
Class Diagram.
In software engineering, a class diagram in theUnified Modeling Language (UML) is a type of static
structure diagram that describes the structure of a system by showing the system's classes, their
attributes, operations (or methods), and the relationships among objects.
Use Case Diagram.
A use case diagram at its simplest is a representation of a user's interaction with the system and
depicting the specifications of a use case. A use case diagram can portray the different types of
users of a system and the various ways that they interact with the system. This type of diagram is
typically used in conjunction with the textual use case and will often be accompanied by other types
of diagrams as well.
Communication Diagram.
A communication diagram in the Unified Modeling Language (UML) 2.0, is a simplified version of
the UML 1.x collaboration diagram.
UML has four types of interaction diagrams:
Sequence diagram
Communication diagram
Interaction overview diagram
Timing diagram
A Communication diagram models the interactions between objects or parts in terms of
sequenced messages. Communication diagrams represent a combination of information taken
from Class, Sequence, and Use Case Diagrams describing both the static structure and dynamic
behavior of a system.
However, communication diagrams use the free-form arrangement of objects and links as used
in Object diagrams. In order to maintain the ordering of messages in such a free-form diagram,
messages are labeled with a chronological number and placed near the link the message is sent
over. Reading a communication diagram involves starting at message 1.0, and following the
messages from object to object.
Communication diagrams show a lot of the same information as sequence diagrams, but because
of how the information is presented, some of it is easier to find in one diagram than the other.
Communication diagrams show which elements each one interacts with better, but sequence
diagrams show the order in which the interactions take place more clearly.
Conclusion: Hence we have studied types of UML Diagram.

Vous aimerez peut-être aussi