UML Behavioral Diagrams

1. [ WEEK 5 ]
[ LECTURE 9]
Behavioral Diagrams
-
Software Engineering
By
Prof. Dr. S. Khan

2. Course Outline
WEEK No. Lecture Topic
1 Software Engineering
2 Requirements Engineering
3 and 4 Structural Diagrams
5 and 6 Behavioral Diagrams
7 Design Patterns
8 Testing
9 & 10 Test Driven Development
11 & 12 Agile Process Models

3. Objectives of the Lecture
• At the end of this lectures the students will be able to understand:
• The basic concepts and definitions of all the behavioral diagram
• The sample behavioral diagrams

4. Behavioral Diagram
• UML behavioral diagrams visualize, specify, construct, and document
the dynamic aspects of a system.
• UML Behavioral Diagrams depict the elements of a system that are
dependent on time
• that convey the dynamic concepts of the system and how they relate to
each other.
• The elements in these diagrams resemble the verbs in a natural language
and the relationships that connect them typically convey the passage of
time.
• For example, a behavioral diagram of a vehicle reservation system might
contain elements such as Make a Reservation, Rent a Car, and Provide
Credit Card Details.

5. Behavioral Diagram
• A behavior diagram is intended to provide clarity, for example, about
internal processes, business processes or the interaction of different
systems.
• Depending on the diagram used, a selected aspect is shown.
• In the Unified Modeling Language (UML), objects are modeled that
can change their states through behavior.

7. Activity Diagrams
• Activity diagrams model the behaviors of a system, and the way in
which these behaviors are related in an overall flow of the system.
• The logical paths a process follows, based on various conditions,
concurrent processing, data access, interruptions and other logical
path distinctions, are all used to construct a process, system or
procedure.
• Activity diagram is essentially an advanced version of flow chart that
modeling the flow from one activity to another activity.

8. Activity
Diagram

9. Activity Diagram

10. Use Case Diagrams
• Use Case diagrams capture Use Cases and relationships among Actors
and the system; t
• They describes the functional requirements of the system, the manner
in which external operators interact at the system boundary, and the
response of the system.
• Use case diagrams are typically developed in the early stage of
development and people often apply use case modeling for Specifying
the context of a system and Capturing the requirements of a system

11. Use Case Diagrams

12. StateMachine Diagrams
• StateMachine diagrams illustrate how an element can move between
states, classifying its behavior according to transition triggers and
constraining guards.
• State machine diagram typically are used to describe state-dependent
behavior for an object.
• An object responds differently to the same event depending on what state
it is in.
• State machine diagrams are usually applied to objects but can be applied to
any element that has behavior to other entities such as: actors, use cases,
methods, subsystems systems and etc. and they are typically used in
conjunction with interaction diagrams (usually sequence diagrams).

13. StateMachine
Diagrams

14. StateMachine Diagrams

15. Timing Diagrams
• Timing diagrams define the behavior of different objects within a
time-scale, providing a visual representation of objects changing state
and interacting over time.
• Timing diagrams focus on conditions changing within and among
lifelines along a linear time axis.
• Timing Diagrams describe behavior of both individual classifiers and
interactions of classifiers, focusing attention on time of occurrence of
events causing changes in the modeled conditions of the Lifelines.

16. Timing
Diagrams

17. Sequence Diagrams
• Sequence diagrams are structured representations of behavior as a
series of sequential steps over time.
• They are used to depict workflow, Message passing and how elements
in general cooperate over time to achieve a result.
• the interaction that takes place in a collaboration that either realizes a
use case or an operation
• high-level interactions between user of the system and the system,
between the system and other systems, or between subsystems
(sometimes known as system sequence diagrams)

18. Sequence
Diagrams

19. Sequence Diagrams

20. Communication Diagrams
• Communication diagrams show the interactions between elements at
run-time, visualizing inter-object relationships.
• These are similar to sequence diagrams, however, Communication
diagrams are used to visualize inter-object relationships, while
Sequence diagrams are more effective at visualizing processing over
time.

21. Communication Diagrams

22. From Sequence Diagram to Communication Diagram

23. Interaction Overview Diagrams
• UML Interaction Overview Diagrams provide a high level of
abstraction an interaction model.
• It is a variant of the Activity Diagram where the nodes are the
interactions or interaction occurrences.
• The Interaction Overview Diagram focuses on the overview of the flow
of control of the interactions which can also show the flow of activity
between diagrams.

24. Interaction
Overview
Diagrams

25. Interaction
Overview
Diagrams

26. SUMMARY &
Q A

27. THANKS