Download UML Behavioral Diagrams

Software Design and
Architecture
Lecture 07: UML Behavioral
Diagrams (Part 1)
1
UML Diagrams (cont…)
• Behavior Diagrams
– Use Case Diag.
2
BEHAVIOR DIAGRAMS
Behavior diagrams show the dynamic behavior of the objects in
a system, which can be described as a series of changes to the
system over time
3
Use Case Diagram
• Case of using the system
• Usage oriented view of system
• Two kinds: Business use case and system use case
4
Business Use Case Diagrams
• Business use cases were introduced in Rational
Unified Process (RUP) to represent business
function, process, or activity performed in the
modelled business.
• A business actor represents a role played by some
person or system external to the modelled business,
and interacting with the business.
• Business use case should produce a result of
observable value to a business actor.
5
Business Use Case Diagrams
6
System Use Case Diagram
7
Include
• The include relationship could be used:
– to simplify large use case by splitting it into several use cases,
– to extract common parts of the behaviors of two or more use cases.
• The purpose of this action is modularization of behaviors,
making them more manageable
<<include>>
<<include>>
Use case C is extracted from use cases A and B to be reused by both use
cases using UML include relationship.
8
Extend
• Extending use case can be optionally inserted into
the behavior defined in the extended use case
• Extended use case is meaningful on its own, it is
independent of the extending use case
Extended
Extending
9
END of Lecture
10