BPMN: Connecting Objects, Pools, Swimlanes and Artifacts

BPMN: Connecting Objects, Pools, Swimlanes and Artifacts

After having reviewed the general concept of BPMN and the various types of events, today, we are going to review connecting objects, pools, swimlanes and artifacts.

Connecting Objects:

These objects show some form of relationship between gateways, events, artifacts or just additional information. There are three types of connecting objects used:

Sequence Flow

This shows the sequence in which activities need to be performed. This can be shown as a straight line with an arrow. This might show a conditional flow or default flow.

No alt text provided for this image

Message Flow:

This type of object depicts the flow across pools or organization boundaries such as departments. It should not connect events or activities within a pool. It is represented by a dashed line with a circle at one end and an unfilled arrow head at the other end.

Association

This object is shown as a dotted line without any arrow head or circle. This can be used to associate an event, activity or gateway to an artifact.

Pools and Swimlanes

A pool represents a major group of participants in a process. A different pool might be a different company, department, etc, but might still be involved in the process. Swimlanes within a pool show the activities and flow for a certain role or participants, defining who is accountable for what action within the process. The swimlane can even be a system and need not necessarily be a department, role, etc.

No alt text provided for this image

Artifacts

Any additional information that a participant should read is shown in the form of an artifacts in the diagram. There are three types of artifacts.

No alt text provided for this image

  1. Data Object : These show what data is necessary for an activity. This can be further divided into data store which provides a source for information to be collected or inserted after a set of activities such that the data will persist beyond the end of the process. Data collection can be further divided into Data input or data output wherein data requirements are captured as data Inputs while data that is produced is captured as data output.
  2. Group: This shows a logical grouping of activities but doesn't change the diagram's flow. This just makes the product easier to understand.
  3. Annotation: This provides further description or detail to a specific part of the diagram.

No alt text provided for this image

In the next article, we will look at how to draw a BPMN.

Chelsea Bahvi Tiban-ye

FORMER HEAD OF ENDOWMENT FUND BOARD (UGBS-BHJCR) || ASPIRING AUDIT AND TAX CONSULTANT

1 年

This is very easy to follow and understand. Thank you.

要查看或添加评论,请登录

Krishna Krishnan的更多文章

  • Product Management 101- Part 1

    Product Management 101- Part 1

    Over time as my career has taken a trajectory, I have been discovering this field called product management more…

  • The process of building a BPMN

    The process of building a BPMN

    After reviewing BPMN and Connecting Objects, Pools, Swimlanes and Artifacts. The underlying concept of a BPMN is…

  • Business Process Modelling Notations

    Business Process Modelling Notations

    BPMN or Business Process Modeling Notations is a flow chart method that models the steps of a business process that is…

  • Basic Principles of Use cases

    Basic Principles of Use cases

    In the last article, I gave an overview of use cases to generically explain the structure of a use case. This time, I…

  • Use case Diagrams:

    Use case Diagrams:

    In order to define a system, it is important to define the behavior of the system when it is running/operator or in…

    5 条评论
  • User Story: An overview

    User Story: An overview

    This is a short extension to the article on Requirement organization. A user story is a tool used to capture…

    2 条评论
  • Requirement Analysis Part 3: Requirement Organization

    Requirement Analysis Part 3: Requirement Organization

    In the previous article, we talked about requirement prioritization. This article will cover requirement organization.

  • Requirement Analysis - Part 2 : Requirement Prioritization

    Requirement Analysis - Part 2 : Requirement Prioritization

    After having covered methods of requirement elicitation and types of requirements over the past few weeks, this week I…

    2 条评论
  • Difference between role of Product Owner and Business Analyst

    Difference between role of Product Owner and Business Analyst

    I am doing a quick turnabout here to focus on the difference between the roles of Product Owner and Business Analyst…

  • Requirement Analysis - Part 1: Types of Requirements

    Requirement Analysis - Part 1: Types of Requirements

    We have earlier had a look at methods of requirement elicitation. Once these requirements are gathered, it is time to…

社区洞察

其他会员也浏览了