0% found this document useful (0 votes)
65 views

DBM Unit 3 - Activity Diagram

UML (Unified Modeling Language) is an industry-standard modeling language used to specify, visualize, and document software systems. It provides various diagram types for different views of a system, such as structural diagrams (class, component), behavioral diagrams (activity, state machine), and interaction diagrams (sequence, communication). Activity diagrams specifically model system workflows and business processes by showing the flow between activities and decisions. Common notations in activity diagrams include activities, transitions, decisions, joins, forks, swimlanes, and more.

Uploaded by

Deepa Shelke
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
0% found this document useful (0 votes)
65 views

DBM Unit 3 - Activity Diagram

UML (Unified Modeling Language) is an industry-standard modeling language used to specify, visualize, and document software systems. It provides various diagram types for different views of a system, such as structural diagrams (class, component), behavioral diagrams (activity, state machine), and interaction diagrams (sequence, communication). Activity diagrams specifically model system workflows and business processes by showing the flow between activities and decisions. Common notations in activity diagrams include activities, transitions, decisions, joins, forks, swimlanes, and more.

Uploaded by

Deepa Shelke
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/ 16

What is UML

Diagram…?
 UML stands for “Unified Modeling Language”.

 It is a industry-standard graphical language for specifying,


visualizing, constructing and documenting the artifacts of software
system.

 The UML uses mostly graphical notation to express the ‘analysis’


and ‘design’ of software projects.

 The UML represent a collection of best engineering practices that are


very
helpful in the modeling o large and complex system.

09/19/20 1
20
Why UML for
modeling..?
 It is mostly use for simplifies the complex process of software design.

 The UML is very important part of developing object oriented software


and the software development process.

 The UML helps project teams communicate, explore design and


validate the architectural design of the software.

09/19/2020 2
Types of
UML
UML

Structural Behavioral Interaction


Class Diagram Activity Communication
Component State Machine Sequence
Object Use Case Timing
Deployment
Composite
Structure
Package

09/19/2020 3
Activity
Diagram…
 Activity diagrams represent the dynamic (behavioral) view of a system.

 Activity diagrams are typically used for business (transaction) process


modeling and modeling the logic captured by a single use-case or usage
scenario.

 Activity diagram is used to represent the flow across use cases or to


represent flow within a particular use case.

 UML activity diagrams are the object oriented equivalent of flow chart and
data flow diagrams in function-oriented design approach.

 Activity diagram contains activities, transitions between activities, decision


points, synchronization bars, swim lanes and many more…
09/19/2020 4
Activity
Diagram…
 Describes how activities are coordinated.

 Is particularly useful when you know that an operation has to achieve


a number of different things, and you want to model what the
essential dependencies between them are, before you decide in what
order to do them.

 Records the dependencies between activities, such as which things can


happen in parallel and what must be finished before something else
can start.

 Represents the workflow of the process.

09/19/2020 5
Activity Diagram…(Notations)
1.
Activity

 The Core symbol is used for Activities.

Activity

 An activity is some task which needs to be done.

 Each activity can be followed by another activity (sequencing).

09/19/2020 6
 An activity may be a manual thing, so that it’s not necessarily in a program.
Activity Diagram…(Notations)
2. Transmission (Flow)

 When the action or activity of a state completes, flow of control


passes immediately to the next action or activity state

 The flow of control is shown by arrow symbol.

09/19/2020 7
Activity Diagram…(Notations)
3. Starting and Ending Nodes

 The source of flow of control is known as ‘Initial Node or


Starting Node’.

Starting Node(Mark)

 Destination of flow of control is called ‘Ending Node or Final


Node’.

Ending Node

09/19/2020 8
Activity Diagram…
(Notations)
4. Join and Fork
 Join
A block bar with several flows entering in it and one leaving from it. this denotes
the end of parallel activities

4.1 Synch. Bar (Join)

 Fork
A black bar ( horizontal/vertical ) with one flow going into it and several leaving
it. This denotes the beginning of parallel activities

4.2 Splitting Bar (Fork)


09/19/2020 9
Activity Diagram…(Notations)

5. Decision and Merge


 Decision
– A diamond with one flow entering
and several leaving. The flow leaving
includes conditions as yes/ no state.

 Merge
– A diamond with several flows entering
and one leaving. The implication is that
all incoming flow to reach this point
until processing continues

09/19/2020 10
Activity Diagram…(Notations)
6.Flow Finaland Swimlane

 Flow final
– The circle with X though it. This indicates
that Process stop at this point

 Swim lane
Received

– A partition in activity diagram by means of form

dashed line, called swim lane. This swim


lane may be horizontal or vertical Payment
fees
Hostel
allotmen
t
Medical
check

– Each zone represents the responsibilities of


a particular class or department Issue identity
card
Issue
library
card

09/19/2020 11
Activity Diagram…(Notations)
Difference between Join and Merge

 A join is different from a merge in that the join synchronizes two inflows
and produces a single outflow. The outflow from a join cannot execute
until all inflows have been received

 A merge passes any control flows straight through it. If two or


more inflows are received by a merge symbol, the action pointed
to by its outflow is executed two or more times

09/19/2020 12
Example of Activity
Diagram…

09/19/2020 13
Example of Activity
Diagram…
Student

Fill-
in
form Verify the [Found]

[Incorrect]
applications
[Not Found]

Check
Regret message
Registrar

form
[Correct]

Display student
screen

Create record
Input student
System

information
[Match]
1
Search for Student
selection list [No
Match]
Regret
09/19/2020
registratio 14

n
Drawback of Activity
Diagram…
 Activity diagrams tell you what is happening, but not who does what.

 In domain modelling, this diagram type does not convey which people
or departments are responsible for each activity.

 In programming, it does not convey which class is responsible for


each activity

09/19/2020 15
Refere
nce
 Books:
 Software Engineering, A Practitioner’s Approach, By Roger
S. Pressman..
 System Analysis and Design, By Elias M. Awad.

 Web Source:
 www.google.co.in
 www.tutorialspoint.com
 www.slideshare.com
 www.wikipedia.com

09/19/2020 16

You might also like