LABORATORIUM ENSYSe Document

No.
Form No.
ARTICLE 3RD MODULE Effectively
Apply
Module Name Use Case and Activity Diagram
Lab Work Analysis and Design of Information Systems Practicum
Student Outcomes
Learning Outcomes LO5. Students are able to model and design business processes
and database design in an integrated system

Unified Modeling Language (UML)

The Unified Modeling Language (UML) is a visual modeling language dominant in object-
oriented software development. UML includes a set of graphical notation techniques to create
abstract models of specific systems. It is used for visual modeling of object-oriented systems. This
language was adopted by the Object Management Group (OMG) as its standard modeling language
in 1997. UML is a method to analyze business process and model the business process in the
specific notation. UML is a widely used method for visualizing and documenting the software
design of a system. Modeling—especially modeling in a way that’s easily understood— allows
the developer to concentrate on the big picture. The UML represents a collection of best
engineering practices that have proven successful in the modeling of large and complex systems.
(Greeff & Ghoshal, 2004).
As a visual modeling language, UML relies heavily on graphical constructs. These graphical
constructs form the foundation of the various UML diagrams. UML defines notation and syntax /
semantics. UML notation is a set of special form for describing various software diagrams. Each
form has a specific meaning, and the UML syntax defines how the forms can be combined.
The purpose or function of UML:
1. Can provide a visual modeling language to user of various types of program or engineer
processes.
2. Can relate to the best available method in modeling.
3. Can share ready-to-use models, which is an expressive visual modeling language to easily
share models and extend programs.
4. Can be useful as a blue print, because its complete and detailed in design.
5. Can model systems with object-oriented concept, so it’s not only useful for modeling software
only.
6. Can create a modeling language that later can be used by human and machine.

The tools used in object-oriented design based on UML are as follows.

A. Use Case Diagram
Use case is an activity the system performs, usually in response to a request by a use that
represent the step-in specific business function or process. Use case allow you to understand
and communicate the purpose of a system or its components. The use case diagram is the UML
model used to graphically show the use cases and their relationship to users (Satzinger et al.,
2011). A UML use case diagram is the primary form of system/software requirements for a
new software program underdeveloped. A use case diagram normally concentrates on showing
the purposes of the system (use case) and the users (actors).
Use case diagram are typically developed in early stage of development and people often apply
use case modeling for some purposes:
1. Specify the context of a system
2. Capture the requirements of a system
3. Validate a systems architecture
4. Drive implementation and generate test cases

The symbols of use case diagram area as follows.

Symbol Description
Actor
Someone interacts with use case (system function) that
has a responsibility toward the system (inputs) and has
expectations from the system (outputs).
Use Case
A use case represents a function or an action within the
system. It’s drawn as an oval and named with the
function.
Association
A line between actors and use cases. Actors may be
connected to use cases by associations, indicating that
the actor and the use case communicate with one another
using messages.
Generalization
Generalization is a parent-child relationship in use case,
where one of them is in a more general form the other.
The child use case is connected to the parent use case.
Include
Include is the relationship between use cases, when a use
case is depicted as using the functionality of another use
case. An additional use case relation to a use case where
an added use case requires this use case to carry out its
functions or as a condition for running this use case. A
use case includes the functionality described in another
use case as a part of its business process flow.
Extend
Extend described the relationship between use cases,
where a use case is another use case is another use case
functionality if certain conditions are met. An additional
use case relation to a use case where the added use case
can stand alone even without the additional use case.
B. Activity Diagram
UML activity diagrams are behavioral diagrams which depict the internal behavior of different
operations of a program with the help of nodes and edges. UML activity diagrams have been
used in different domains for work-flow representation. Activity diagram describe the various
user (or system) activities, the person who does each activity, and the sequential flow of these
activities (Satzinger, er al., 2012). Activity diagram is essentially an advanced version of flow
chart that modeling the flow from one activity to another activity. An activity diagram starts
with one start activity and ends at one final activity. An Activity diagram resembles a
horizontal flowchart that shows the action and events as they occur.
The symbols of activity diagram area as follows.
Symbol Description
Initial state
Initial state is represented by filled circle.
Initial state is portray’s the beginning of a set
of actions or activities
Activity Final State
Activity final state is portray’s the end or
stop all control flows in a set of actions or
activities

Activity
Activity Activity is used to represent a set of actions
Decision

Condition
Decision represents a test condition to ensure
that the control flow or object flow only goes
down one path
Fork Node
Fork node used to split behavior into a set of
parallel or concurrent flows of
activities/actions.
 Join Node
Join node show combined activities

Swimlane
Swimlane is a separate the business
organization that is responsible for the
activities that occur.
Control Flow & Object Flow
Control flow shows the sequence of
execution. Object flow shows the flow of an
object from one activity/action to another
activity/action

C. Sequence Diagram
A sequence diagram is a dynamic diagram that shows what happens during the time. In this
diagram, all the details of the operations are specified, and the messages that each object
involved in the operation sends to the others is detailed together with the time instant at which
it happens. The diagram is built with time that progresses from up to down, and the objects are
ordered from left to right according to the time instant in which they appear in the sequence of
messages.
A sequence diagram is a time-based representation on messages in the system because it shows
time line of events that happen in the system. Sequence diagram shows what happens when a
particular flow through a use case or activity diagram is executed. It also shows set of
collaborating objects, in addition to showing the messages that pass between them.
The symbols of sequence diagram area as follows.
1. Lifeline Notation
A sequence diagram is made up of several of these lifeline notations that should be arranged
horizontally across the top of the diagram. In a sequence diagram, it is shown as a vertical
dashed line, parallel to the time axis, with a head symbol showing its name and type.
Vertical line illustrates the life span of an object within the context of a single interaction.
 A lifeline notation with an actor element symbol is used when the particular sequence
diagram is owned by a use case.

2. Activation Bars
Activation bar is the box placed on the lifeline. It is used to indicate that an object is active
(or instantiated) during an interaction between two objects. The length of the rectangle
indicates the duration of the objects staying active.

3. Message Arrows
An arrow from the Message Caller to the Message Receiver specifies a message in a
sequence diagram. A message can flow in any direction; from left to right, right to left or
back to the Message Caller itself.
Symbol Description
Synchronous message symbol
Represented by a solid line with a solid
arrowhead. This symbol is used when a sender
must wait for a response to a message before it
continues. The diagram should show both the
call and the reply.
Reply message symbol
Represented by a dashed line with a lined
arrowhead, these messages are replies to calls.
 DAFTAR PUSTAKA

Alhumaidan, F. (2012). A Critical Analysis and Treatment of Important UML Diagrams

Enhancing Modeling Power. Intelligent Information Management, 04(06), 231–237.
https://doi.org/10.4236/iim.2012.46034

Booch, G., Rumbaugh, J., & Jacobson, I. (1999). The Unified Modeling Language User Guide.
California: Addison Wesley Longman Publishing Co., Inc.

Chonoles, M. J., & Schardt, J. A. (2003). UML 2 for Dummies. For Dummies.

Grgec, M., & Mužar, R. (2007). Role of UML sequence diagram constructs in object lifecycle
concept. Journal of Information and Organizational Sciences, 31(1), 63–74.

Kurniawan, T. A. (2018). Pemodelan Use Case (UML): Evaluasi Terhadap beberapa Kesalahan
dalam Praktik. Jurnal Teknologi Informasi Dan Ilmu Komputer, 5(1), 77.
https://doi.org/10.25126/jtiik.201851610

Satzinger, J., Jackson, R., & Burd, S. (2011). Systems Analysis and Design in a Changing Worlf
(6th Ed). Boston: Cengage Learning.

Shelly, G., & Rosenblatt, H. (2012). Essentials of Systems Analysis and Design 9th Ed. Boston:
Cengage Learning.

Siau, K. (2010). An analysis of unified modeling language (UML) graphical constructs based on
BWW ontology. Journal of Database Management, 21(1).

Touseef, M., Anwer, N., Hussain, A., & Nadeem, A. (2015). Testing from UML Design using
Activity Diagram: A Comparison of Techniques. International Journal of Computer
Applications, 131(5), 41–47. https://doi.org/10.5120/ijca2015907354.