Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
0% found this document useful (0 votes)
34 views

(Coding Big Data) - Week 13 - Business Process Analysis Part 2

1. Identify start and end points using initial and final states 2. Add activity or action states to represent steps 3. Connect states with action flows to show the flow of activities 4. Add decision points, forks, joins to model choices or parallel activities 5. Include swimlanes if modeling responsibilities across roles

Uploaded by

danielbayu288
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
34 views

(Coding Big Data) - Week 13 - Business Process Analysis Part 2

1. Identify start and end points using initial and final states 2. Add activity or action states to represent steps 3. Connect states with action flows to show the flow of activities 4. Add decision points, forks, joins to model choices or parallel activities 5. Include swimlanes if modeling responsibilities across roles

Uploaded by

danielbayu288
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 33

1

CODING & BIG DATA


Week 13 : Business Process Analysis – Part 2
Process Modeling

Created by Coding & Big Data Team


President University
2

Coding & Big Data


Coding & Big Data course is aimed for students
in various study backgrounds to learn about the
nature of programming as human activity & big
data as new data science for observation,
analysis, prediction, and behavior related
patterns and trends.
3

Weekly Schedule

Normal Class Lab Class


Mentor Lecturer Assistant Lecturer
Content Lecture & Theory Practice
- Basic Coding with Python
- Roblox
- Microsoft Power BI
- Google Developer Student
Club
Day Normal Class Saturday
4

WEEK 13
Business Process Analysis
Part 02
Process Modelling
Unified Modelling Language (UML)
Use Case Diagram
Activity Diagram
5

Process
Modeling
What is? 6

Definition (https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-uml/)

• Process modeling
• Used in various contexts
• Is a method to illustrate or visualize a process that consists of activities
or events.
• Process modeling in business -> Business Process Modeling (BPM)
• BPM is used to identify current business process (as is) and create a more
efficient / effective business process (to be).
• BPM is represented using Business Process Model and Notation
(BPMN).
• Process modeling in Software Engineering is used to identify the
requirement, the flow, the integration of software components.
• Process modeling in software engineering is represented using UML.
7

UML
What is?
Definition (https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-uml/)

• UML
• Unified Modeling Language
• a standardized modeling language consisting of an integrated set of
diagrams, developed to help system and software developers for
specifying, visualizing, constructing, and documenting the artifacts of
software systems, as well as for business modeling and other
non-software systems.
• History:
• Initiated by Rational Software Corporation (1994 – 1995)
• Adopted as standard by the Object Management Group / OMG (UML 1.0
in 1997)
• Currently managed by OMG (UML 2.0 in 2005)
UML
Diagrams (https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-uml/)

Structure Diagrams Behavior Diagrams


• Class Diagram • Activity Diagram
• Component Diagram • Use Case Diagram
• Deployment Diagram • State Machine Diagram
• Object Diagram • Sequence Diagram
• Package Diagram • Communication Diagram
• Composite Structure Diagram • Interaction Overview Diagram
• Profile Diagram • Timing Diagram
UML
Diagrams (https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-uml/)
Use Case
Diagram
Use Case Diagram
Definition: https://www.lucidchart.com/pages/uml-use-case-diagram/
http://www.tutorialspoint.com/uml/uml_use_case_diagram.htm

• Use Case Diagram: used to summarized the detail of a system. It describes the
interaction between the users (actors) and the system.
• Use Case Diagram represents:
• Scenarios in which your system or application interacts with people, organizations,
or external systems
• Goals that your system or application helps those entities (known as actors)
achieve
• The scope of your system
• Why we use Case Diagram?:
• Used to gather the requirements of a system
• Used to get an outside view of a system
• Identify the external and internal factors influencing the system
• Show the interaction among the requirements are actors
Use Case Diagram
Example:
Use Case Diagram
How to create: Notation

• Use Case
• Oval shape with the name of a use case
written inside the oval shape.
• Actor
• Stick figures that represent the people
actually employing the use cases.
• Association
• A line between actors and use cases. It
represents which actors are associated
with which use cases.
• System boundary boxes
• A box that sets a system scope
Use Case Diagram
How to create: Steps

1. Define the subject (scope / boundary)


2. Identify and list all actors Step 1

3. Identify the user goal. What the user requires


or try to achieve.
Step 2
4. Create use case for every goal inside the box
5. Structure the use case. Create association.

Step 4
Use Case Diagram
How to create: Tips for drawing Use Case Diagram

1. A use case diagram should be as simple as possible.


2. A use case diagram should be complete.
3. A use case diagram should represent all interactions with the use case.
4. If there are too many use cases or actors, then only the essential use cases
should be represented.
5. A use case diagram should describe at least a single module of a system.
6. If the use case diagram is large, then it should be generalized.
Use Case Diagram
How to create: Association, Include, & Extend

1. After we finish with all association between


actors and the use cases, then we can define
the <<include>> and <<extend>> use case.
2. <<include>> is a direct relationship between
two use cases. The included use case is a use
case that is added as a part (sub) of the base
use case.
3. <<extend>> is a direct relationship between
two use cases to define a common / usual
supplementary. The extended use case is an
extension of the base use case.
Use Case Diagram
How to create: Example
Use Case Diagram
How to create: Example
Use Case Diagram
Practice and Examples

The diagram on the next represent Bank ATM use


cases. There are three actors associated with the
use case diagram.

Task: Create another use case diagram for Internet


Banking or Mobile Banking. You may implement
other relevant use cases using <<include>> or/and
<exclude>>.
Activity
Diagram
Activity Diagram
Definition: https://www.smartdraw.com/activity-diagram/
https://www.tutorialspoint.com/uml/uml_activity_diagram.htm

• Activity Diagram: presents a series of actions or flow of control in a system. It is similar


to a flowchart (swim lane diagram) or a data flow diagram. Used to describe the steps in
use case diagram.
• Activity Diagram vs Flow Chart (Swim Lane Diagram):
• Activity diagram is a behavior diagram to represent workflow of stepwise
activities of a system. Flow chart is a graphical diagram to represent the sequence
of steps to solve problems.
• Activity diagram represents business process while a flowchart represents an
algorithm.
• Activity diagram may have a swim lane or not, but when it has a swim lane then it
may look like a swim lane diagram.
Activity Diagram
Definition: https://www.smartdraw.com/activity-diagram/
https://www.tutorialspoint.com/uml/uml_activity_diagram.htm

• Activity Diagram is used to:


• Demonstrate the logic of an algorithm.
• Describe the steps performed in a UML use
case.
• Illustrate a business process or workflow
between users and the system.
• Simplify and improve any process by
clarifying complicated use cases.
• Model software architecture elements, such
as method, function, and operation.
Activity Diagram
How to: Notations
• Initial state / Start point & Final state / End point
• A small filled circle followed by an arrow that Initial / Start
indicates the start of a system flow (start point). An
arrow followed by a circle filled with a full circle Final / End
(final point).
• Activity or action state
• An action state represents the non-interruptible
action of objects. Represented using a rectangle
with rounded corners.
• Action flow
• An arrow line that represents the transition from one
action to the other.
• Object flow
• An arrow line that connect action to object. It
indicates the action creates or influence the object.
Activity Diagram
How to: Notations
• Decision / branching
• A diamond that represents a decision with alternate
paths.
• Synchronization
• A thicker horizontal line used to split single flow to
concurrent flow (fork node). The concurrent flows
then will be joined using the join node to back to a
single flow.

• Time event
• An hour glass symbol that represent the stop event
of a flow.
• Merge event
• A merge event joins multiple flows that are not
concurrent.
Activity Diagram
Example: Login page
Activity Diagram
Example: Banking System
Activity Diagram
Example: Student Enrollment Case

Process & Procedures


1. An applicant wants to enroll in the university.
2. The applicant hands a filled out copy of Enrollment Form.
3. The registrar inspects the forms.
4. The registrar determines that the forms have been filled out properly.
5. The registrar informs student to attend in university overview
presentation.
6. The registrar helps the student to enroll in seminars
7. The registrar asks the student to pay for the initial tuition.

How to put these process into an activity diagram?


Activity Diagram
Example: Student Enrollment Case – Activity Diagram
Activity Diagram
Example: Student Enrollment Case – Activity Diagram with Swimlanes
Activity Diagram
Case: Process Order

Process Order - Problem Description


Once the order is received, the activities split into two parallel sets of activities.
One side fills and sends the order while the other handles the billing.

On the Fill Order side, the method of delivery is decided conditionally. Depending
on the condition either the Overnight Delivery activity or the Regular Delivery
activity is performed.

Finally the parallel activities combine to close the order.

Task: Create an activity diagram that represent the above process.


Is the process effective / efficient? How to make it more effective / efficient?
NEXT WEEK DISCUSSION
Software Development Life Cycle

You might also like