Professional Documents
Culture Documents
OUTLINE
2
3
3
4
• Decision Node
Test condition using decision criteria (labelled with guard condition)
• Merge Node
Integration decision
• Fork Node
Split concurrent flows of activities
• Join Node
Integrate fork
• Swimlane
Combined two or more activity diagram
6
Action 1 Action 2
initial Action 3
[C] Action 4
fork [~C]
decision
Final -
activity
join
7
7
8
8
9
9
10
Activity Diagram
untuk Use Case
Registrasi
10
11
11
12
Main Components
• Object/Class/Lifeline
• Interface/Boundary
• Control
• Entity/Database
• Message
• Synchronous message
• Return message
• Self message
• Recursive message
• Activation Bar
• Actor
12
13
AN ACTOR
AN OBJECT
anObject:aClass
A LIFELINE
A FOCUS OF CONTROL
A MESSAGE aMessage()
OBJECT DESTRUCTION x
Slide
13
14
14
15
15
16
16
17
17
18
18
19
Summary
• Activity diagram can be used to graphically describes activities in a use case scenario and
also activities in the whole system (connectivity among use cases)
• Sequence diagram is a diagram that represent sequence of messages among classes
• graphically describes how system work involving objects related in a use case
• Sequence diagram is developed referring to activity diagram for each use case or activities in
use case scenario. Objects called in sequence diagram should be depicted in Class diagram
19
20
References
Main
Kenneth E. Kendall, Julie E. Kendall (2014), Systems Analysis and Design, 9th Edition,
Prentice Hall
Support
Howard Podeswa (2010), UML for IT Business Analyst, Second Edition, Cengage Learning
Whitten & Bentley (2007) Systems Analysis and Design Methods, 7th Edition, McGraw-Hill
Alan Dennis, Barbara H Wixom, David Tegarden (2005), System Analysis and Design with
UML Version 2.0