1.2. Core BPMN 2.0 Elements

🟢 Flow Objects

• Event: Something that happens (start, end, etc.)
• Activity: A task or subprocess that must be performed.
• Gateway: Decision points, splits, or merges.

In BPMN 2.0, Flow Objects are the core components that describe actions within a process. There are three main types:

1. Events indicate occurrences in the process, such as the start or end of a workflow.
2. Activities are tasks that must be completed, which can also include subprocesses that contribute to the overall workflow.
3. Gateways are decision points that allow the process to split into different paths based on certain conditions. For example, a gateway can determine if a task should proceed based on whether a condition is met—like checking stock availability before proceeding with an order.

Think of Flow Objects like a traffic control system. Events are like traffic lights indicating when to stop or go, Activities are the cars that move through intersections (tasks being completed), and Gateways are the stop signs that determine whether drivers can go left or right depending on certain traffic conditions.

🟦 Connecting Objects

• Sequence Flows: Show the order of activities.
• Message Flows: Represent communication between participants.
• Associations: Link text annotations or artifacts.

Connecting Objects in BPMN 2.0 are vital as they link Flow Objects together to convey the flow of a process:

1. Sequence Flows indicate the order in which activities take place, showing how one task leads to the next.
2. Message Flows illustrate how different participants or entities communicate with each other, important for understanding interdependencies.
3. Associations help to connect annotations or additional information to elements in the diagram, providing context without disrupting the flow of the process.

Imagine a relay race where each runner represents an activity (Sequence Flows) passing the baton (communicating messages) to the next runner. Just as additional coaches might be on the sidelines giving helpful advice (Associations), annotations in BPMN provide clarity to the process.

🟨 Swimlanes

• Pool: Represents an organization or participant.
• Lane: Divides a pool into roles/departments to show responsibility.

Swimlanes are visual elements in BPMN that organize a diagram into 'pools' and 'lanes':

• A Pool signifies a significant entity involved in the process, often an organization or a participant's role.
• Lanes further divide the pool into specific roles or departments, clarifying who is responsible for which part of the process. This structure helps to visualize accountability and interaction within complex workflows.

Consider a company as a swimming pool where each department uses a lane to swim. Each lane represents a specific role within that pool, allowing everyone to see their responsibilities clearly, just like Swimlanes in BPMN show who is accountable for which tasks.

📄 Artifacts

• Data Objects: Represent inputs or outputs.
• Text Annotations: Add notes or comments.
• Groups: Visual grouping without affecting flow.

Artifacts in BPMN 2.0 enrich the diagram by providing additional context:

• Data Objects depict the inputs required for activities and outputs generated, essential for understanding resource flow.
• Text Annotations offer a way to include explanatory notes, which help clarify complex parts of the process without cluttering the main flow.
• Groups can visually bundle elements together to indicate relationships or categorizations without altering how the process flows.

Think of Artifacts as the supporting materials in a presentation. Data Objects are like the data charts that show results, Text Annotations are the speaker’s notes that clarify a point, and Groups are slides that are thematically connected, but do not affect the overall sequence of the presentation.

🔁 Example BPMN Flow (Simple Order Process):

(Start) → [Receive Order] → [Validate Order] → ◇ (Stock Available?) → Yes → [Pack & Ship] → (End) → No → [Notify Customer] → (End).

This example of a BPMN flow illustrates a basic order processing scenario. It starts with an event: 'Receive Order.' From there, activities follow in sequence. The decision point (gateway) checks stock availability:

• If stock is available, the process continues to 'Pack & Ship' leading to the end of the process.
• If not, it directs to 'Notify Customer', which also leads to the end. This simple flow showcases how BPMN efficiently documents and visualizes business processes.

Imagine this order process like making a sandwich. First, you get your ingredients ('Receive Order'), then you check if you have everything you need ('Validate Order'). If you do ('Stock Available? Yes'), you proceed to make the sandwich ('Pack & Ship'). If not ('Stock Available? No'), you need to inform someone that you are missing ingredients ('Notify Customer'). The BPMN flow gives a clear picture of how you move through the process.

--