Scribd
Upload
9 views32 pages

cs711 slides

The document provides an overview of UML diagrams, categorizing them into static, dynamic, and implementation types, with a focus on activity diagrams. It explains the basic vocabulary and rules for creating activity diagrams, including concepts like initial state, activities, flow, joins, forks, branches, and merges. Additionally, it presents problem statements and scenarios to illustrate the application of activity diagrams in various workflows.

Uploaded by

Faizan Berlas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
9 views32 pages

cs711 slides

The document provides an overview of UML diagrams, categorizing them into static, dynamic, and implementation types, with a focus on activity diagrams. It explains the basic vocabulary and rules for creating activity diagrams, including concepts like initial state, activities, flow, joins, forks, branches, and merges. Additionally, it presents problem statements and scenarios to illustrate the application of activity diagrams in various workflows.

Uploaded by

Faizan Berlas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 32

1

Software Design

Lecture : 22
2

Categories of UML Diagrams


(3)
Static
Use case diagram
Class diagram

Dynamic

Activity diagram
Object diagram
State diagram
Sequence diagram
3

Implementation

Component diagram
Deployment diagram
4

Introduction to Activity
Diagram
 In many ways UML Activity diagrams are the
object-oriented equivalent of flow charts and data-
flow diagrams (DFDs). They are used to explore
the logic of:
 A complex operation
 A complex business rule
 A single use case
 Several use cases
 A business process
5

Activity Diagram – Dynamic Category

It shows the flow from activity to activity


within a single process i-e Work Flow.

With an activity diagram, you can also


model the flow of an object as it moves
from state to state
at different points in the flow of control
6

Basic Vocabulary of Activity Diagram

Diagrams are read from top to bottom


and have branches and forks to describe
conditions and parallel activities
7

Initial State
The filled in circle is the starting point of the
diagram. An initial node isn’t required
although it does make it significantly easier
to read the diagram

There will be only one initial state in the


activity diagram
8

Activity
An activity, also known as an activity state, on
a UML Activity diagram typically represents
the invocation of an operation, a step in a
business process, or an entire business
process.

The rounded rectangles represent activities


that occur
9

Flow / Edges

 The directed arrows on the diagram to

show the flow between activities to

complete a workflow
10

Vocabulary

Join

 A black bar with several flows entering it


and one leaving it. All flows going into
the join must reach it before processing
may continue. This denotes the end of
parallel processing.
11

Fork – Parallel Activities

A fork is used when multiple activities are


occurring at the same time

A black bar with one flow going into it and several


leaving it

A Fork Should Have a Corresponding Join. In


general, for every start (fork) there is an end (join)
12

Vocabulary of Activity Diagram

Branch - Decision:

 The branch describes what activities will take


place based on a set of conditions.

 It is represented by a diamond with one flow


entering and several leaving. The flows leaving
include conditions although some modelers will
not indicate the conditions if it is obvious.
13

Merging

 A diamond with several flows entering


and one leaving. The implication is that
one or more incoming flows must reach
this point until processing continues,
based on any guards on the outgoing flow.
14

Basic Vocabulary

Activity Final Node


 The filled circle with a border is the ending
point. An activity diagram can have zero or
more activity final nodes.
15

Rule of Activity Diagram

After the merge all of the parallel

activities must be combined by a join

before transitioning into the final activity

state.
16

Pictorial Representation of

Vocabulary of Activity Diagram


17
18

Problem Statement
19

Non-Computer Science
Scenario
 Consider the workflow associated with building a
house. First, you select a site. Next, you
commission an architect to design your house.
After you've settled on the plan, your developer
asks for bids to price the house. Once you agree
on a price and a plan, construction can begin.
Permits are secured, ground is broken, the
foundation is poured, the framing is erected, and
so on, until everything is done. You're then
handed the keys and a certificate of occupancy,
20
21

Problem Statement
22

In an order processing system, once the order


is received multiple activities are initiated to
complete the order process. On one side order
filing is initiated and on the other end billing
mechanism is initiated to receive the payment.
On the order filing side delivery mechanism is
finalized whether it is a rush delivery or
regular delivery. In the end all the activities
end to close an order.
23

Possible Solution
24

Swim Lanes
At times it useful, especially when you are
modeling workflows of business
processes, to
partition the activity states on an activity
diagram into groups

Each group representing the business


organization responsible for those
activities.

Each group is known as “Swim Lane”


25
26

Scenario
• In a typical customer services call centre scenario
where multiple people are sitting, when a call is
received it is first decided whether it’s a call from a
new customer or an existing customer, in parallel log of
the call is created to have record of the communication
between Call Centre Representative (CCR) for future
reference. If it is a call from a new customer then the
call is transferred to sales team and it the call is from
an existing customer then call is transferred to
helpdesk after this the process is completed
27
28

Problem Statement

• In a vehicle reservation system, first step is to find the


client id to determine whether the client is new or
existing one, after determining the type of client, the
request for the reservation of vehicle is initiated to find
the to be reserved car, if the car is available then the
inventory is updated along with updating the charges
to calculate the new total of the bill, after new bill is
generated and inventory is updated the process
reserving the car is completed. At each step otherwise
step is to be included.
29

Possible Solution
30
31

Tasks to Do
 Create Activity diagram of Use Case Diagram

and Class Diagram

 Reverse Engineered the activity diagram given in

the next slide to come up with Use Cases and

Use Case Diagram


32

Possible Solution

You might also like