Process Modelling (BPMN and Flowcharts)

Introduction

Process modelling is a critical skill in business analysis and requirements engineering. It provides a visual representation of how business processes work, making complex workflows easy to understand and communicate. This guide will help you master Process Modelling using BPMN (Business Process Model and Notation) and Flowcharts for your CBAP exam.

Why is Process Modelling Important?

Process modelling is essential for several reasons:

• Clarity and Communication: Visual representations help stakeholders understand complex business processes quickly and clearly.
• Identifying Inefficiencies: By mapping out processes, you can spot bottlenecks, redundancies, and areas for improvement.
• Standardization: BPMN provides a standardized notation that professionals worldwide understand, facilitating consistent communication.
• Requirements Validation: Process models help validate that business requirements are complete and correctly understood.
• Change Management: Models serve as baseline documentation for process improvements and organizational change.
• Training and Documentation: Process models become valuable training tools and process documentation for new employees.

What is Process Modelling?

Process modelling is the activity of representing a business process in a structured, visual format. It captures the sequence of activities, decisions, actors, and systems involved in completing a business objective.

Key Definitions

Business Process: A sequence of activities performed by one or more actors (people or systems) to achieve a specific business outcome.

BPMN (Business Process Model and Notation): An international standard notation developed by the Object Management Group (OMG) for creating visual representations of business processes. BPMN 2.0 is the current standard.

Flowchart: A simpler, more general form of process diagram using basic shapes to represent process steps, decisions, and flow direction.

How Process Modelling Works

Core BPMN Elements

1. Events
Events are something that happens during a business process. They have a cause (trigger) and an effect (result).

• Start Event: Represented by a circle. Indicates the beginning of a process.
• End Event: Represented by a circle with a bold border. Indicates the completion of a process.
• Intermediate Event: Represented by a circle with a double border. Occurs between start and end events.

2. Activities/Tasks
Activities are work that needs to be performed. Represented by rounded rectangles.

• Task: A single activity that cannot be broken down further.
• Subprocess: A compound activity containing multiple tasks within it (shown with a '+' symbol).

3. Gateways
Gateways control the flow of a process using decision logic. Represented by diamond shapes.

• Exclusive Gateway (XOR): Only one outgoing path is taken (either/or decision).
• Inclusive Gateway (OR): One or more outgoing paths are taken.
• Parallel Gateway (AND): All outgoing paths are taken simultaneously.
• Event-based Gateway: The path depends on which event occurs first.

4. Connectors
Connectors show the flow between elements.

• Sequence Flow: Shows the order of activities (solid arrow).
• Message Flow: Shows communication between separate participants (dashed arrow).

5. Swimlanes
Swimlanes represent different actors or departments. They help show who is responsible for each activity.

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

6. Artifacts
Additional elements that provide context.

• Data Objects: Represent information used or produced by activities.
• Annotations: Provide additional information about process elements.
• Groups: Cluster related elements visually.

Basic Flowchart Elements

While less formal than BPMN, flowcharts use standardized shapes:

• Oval/Circle: Start/End point
• Rectangle: Process/Activity step
• Diamond: Decision point
• Parallelogram: Input/Output
• Arrows: Flow direction

Step-by-Step Guide to Creating a Process Model

Step 1: Identify the Process Scope

Clearly define what process you're modelling. Determine the start and end points.

Step 2: Gather Information

Conduct interviews, workshops, and document reviews to understand the process flow, decision points, and actors involved.

Step 3: Identify Key Elements

• Start and end events
• Activities/tasks required
• Decision points and conditions
• Actors and swimlanes
• Data inputs and outputs

Step 4: Map the Sequence

Arrange activities in the order they occur, showing dependencies and parallel activities.

Step 5: Add Gateways and Decisions

Identify all decision points and conditions that determine process flow.

Step 6: Define Swimlanes

Assign responsibility for each activity to the appropriate actor or department.

Step 7: Review and Validate

Verify the model with stakeholders to ensure accuracy and completeness.

Step 8: Document and Refine

Add annotations where necessary and create a legend for any non-standard elements.

Common Process Modelling Scenarios

Sequential Process

Activities occur one after another in a predetermined order. Use sequence flow arrows connecting tasks linearly.

Decision-Based Process

The process follows different paths based on specific conditions. Use exclusive gateways (XOR) to show either/or decisions.

Parallel Activities

Multiple activities occur simultaneously. Use parallel gateways (AND) to split the flow and join it back together.

Iterative Process

Activities may repeat based on certain conditions. Use feedback loops with sequence flows returning to earlier steps.

Exception Handling

Additional paths for handling errors or exceptions. Use intermediate events and multiple paths to show alternative flows.

How to Answer Exam Questions on Process Modelling

Understanding Question Types

Type 1: Scenario-Based Questions
You're given a business scenario and asked to:

• Identify missing elements in a partial process model
• Correct errors in an existing model
• Choose the appropriate gateway type for a decision
• Determine the next step in a process

Type 2: Knowledge Questions
Direct questions about:

• BPMN notation and symbols
• When to use specific gateways
• Differences between flowcharts and BPMN
• Best practices in process modelling

Type 3: Application Questions
You must:

Strategic Approach to Answering

1. Read Carefully
Understand exactly what the question is asking. Look for keywords like 'which gateway', 'identify the error', 'what happens next'.

2. Identify the Process Context
Determine if the question involves sequential flow, decisions, parallel activities, or exception handling.

3. Consider All Elements
Think about start/end events, swimlanes, data objects, and decision criteria.

4. Apply BPMN Rules
Ensure your answer follows BPMN standards and conventions.

5. Verify Logic Flow
Trace through the process to ensure your answer makes logical sense.

Exam Tips: Answering Questions on Process Modelling (BPMN and Flowcharts)

Tip 1: Master Gateway Selection

This is a frequent exam topic. Remember:

• Exclusive Gateway (XOR): When you need 'one and only one' path. Example: Is the invoice amount over $5,000? Yes → Manager approval | No → Auto-approve
• Inclusive Gateway (OR): When you need 'one or more' paths. Example: Send notification to customer, supervisor, and/or compliance team based on conditions.
• Parallel Gateway (AND): When activities happen simultaneously. Example: Prepare documentation AND schedule meeting both happen at the same time.

Exam Tip: If a question asks 'what type of gateway', look for keywords: 'one path' suggests XOR, 'simultaneously' suggests AND, 'may or may not' suggests OR.

Tip 2: Swimlane Responsibility

Questions often test whether you understand who is responsible for each activity.

• Each activity should fall within one swimlane (person or department responsible)
• Message flows show communication between swimlanes
• Avoid activities 'floating' between swimlanes

Exam Tip: When analyzing a model, verify that every activity is properly assigned to a swimlane. If an activity spans multiple swimlanes, it should be broken into separate tasks.

Tip 3: Recognize Common Errors

Watch for these frequent mistakes in exam models:

• Dead-end paths: A sequence flow that doesn't lead to an end event
• Improper gateway usage: Using parallel gateway when exclusive gateway is needed, or vice versa
• Missing conditions: Decision gateways without clear condition labels on outgoing paths
• Unclear swimlane ownership: Activities not clearly assigned to a responsible party
• Incomplete start/end: Missing clear start or end events

Exam Tip: When reviewing a model, trace every path from start to end. If any path doesn't reach an end event, the model is incomplete.

Tip 4: Understand Data Flow

Questions may ask about data objects and their relationship to activities.

• Data objects show inputs (what's needed) and outputs (what's created)
• Distinguish between a task name (what's being done) and data objects (what's being processed)
• Multiple tasks may use or produce the same data object

Exam Tip: If a question mentions information flow, consider whether data objects are properly documented in the model.

Tip 5: Event Types Matter

Different events signal different process points:

• Start Events: Only one per process (in simple models)
• Intermediate Events: Occur during the process; can trigger additional actions
• End Events: Multiple possible end events (success, error, cancellation)

Exam Tip: If a scenario describes 'something happens that affects the process', it's likely an intermediate event.

Tip 6: BPMN vs. Flowcharts

Know the differences for comparative questions:

• BPMN: Standardized, includes swimlanes, supports message flows, more detailed notation
• Flowcharts: Simpler, more general, uses basic shapes, easier for non-technical stakeholders

Exam Tip: If a question asks when to use which notation, BPMN is best for complex organizational processes; flowcharts for simple internal processes or technical documentation.

Tip 7: Subprocess vs. Task

Know when to use subprocess:

• Task: Single, atomic activity (cannot be decomposed)
• Subprocess: Complex activity containing multiple internal steps

Exam Tip: If a question describes multiple steps bundled together, it's a subprocess. If it's a single action, it's a task.

Tip 8: Read Condition Labels

Outgoing paths from gateways should have clear condition labels.

• Each path from an exclusive gateway should show a mutually exclusive condition
• Labels should be clear and testable (yes/no, approved/rejected)
• Avoid vague language like 'maybe' or 'perhaps'

Exam Tip: When a model shows conditions, verify they're mutually exclusive and collectively exhaustive.

Tip 9: Sequence Flow Rules

Remember fundamental rules:

• Sequence flows cannot cross swimlanes (that's a message flow)
• Every activity must have at least one incoming and one outgoing flow (except start and end events)
• Multiple outgoing flows require a gateway

Exam Tip: If a flow crosses swimlanes, it's wrong. Activities should be in the swimlane of the actor performing them.

Tip 10: Context is Key

Always consider the business context:

• Does the model logically represent how the business actually works?
• Are all decision points captured?
• Are all actors identified?
• Does the process have a clear start and end?

Exam Tip: If a model seems illogical or incomplete based on the scenario description, it likely contains an error that the question is testing.

Tip 11: Practice with Examples

For exam preparation:

• Study real-world process models from your industry
• Practice drawing simple processes (approval workflows, order processing, customer registration)
• Analyze process models and identify errors
• Explain why specific notations were chosen for given scenarios

Tip 12: Watch Your Language

When answering essay or short-answer questions about process modelling:

• Use proper terminology (gateway, swimlane, sequence flow, not 'arrow' or 'box')
• Be specific about BPMN elements
• Explain the 'why' behind your choices, not just the 'what'

Quick Reference: Common Exam Scenarios

Scenario: Approval Workflow

What to model: Decision gateway for approval conditions, separate swimlanes for requester and approver, possible rejection loop back to requester.

Key elements: Exclusive gateway (approval decision), message flows between swimlanes, potential intermediate event (rejection).

Scenario: Parallel Processing

What to model: Multiple activities happening at the same time, then coming back together.

Key elements: Parallel gateway to split, multiple parallel tasks, parallel gateway to rejoin before next step.

Scenario: Exception Handling

What to model: Normal flow with alternative paths for errors.

Key elements: Intermediate events to capture exceptions, separate swimlanes if different teams handle errors, decision gateways for error conditions.

Scenario: Multi-Step Approval

What to model: Sequential approval steps, each by different approvers.

Key elements: Multiple swimlanes, sequential approval tasks, decision gateways at each step with approval/rejection paths.

Conclusion

Process modelling using BPMN and flowcharts is a fundamental skill for business analysts. Master the notation, understand the rules, and practice applying them to real scenarios. Focus on understanding not just 'what' each element means, but 'why' and 'when' to use it. On exam day, read questions carefully, identify the process context, and apply the appropriate notation. With these tips and a solid understanding of BPMN fundamentals, you'll be well-prepared to answer process modelling questions confidently.