(Coding Big Data) - Week 13 - Business Process Analysis Part 2
(Coding Big Data) - Week 13 - Business Process Analysis Part 2
Weekly Schedule
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/)
• 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
Step 4
Use Case Diagram
How to create: Tips for drawing Use Case Diagram
• 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
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.