Business Analysis 101: Requirements Analysis and Design Definition - Process Modeling, BPMN, Flowcharts, SIPOC

Process Modeling (BPMN, Flowcharts, SIPOC)

What This Is

Process modeling is the practice of visualising “how work gets done” so that everyone—stakeholders, developers, testers, and managers—can see the same picture of a business activity. In the BA lifecycle it belongs to Analysis (and later to Solution Evaluation) because the model becomes a key artifact for eliciting, validating, and communicating requirements.

Real?world example: A financial services firm wants to replace its legacy CRM. The BA creates BPMN diagrams of the “Lead?to?Opportunity” flow, a simple flowchart of the “Contact?Creation” screen, and a SIPOC map of the entire “Customer?On?boarding” process to show who does what, where hand?offs occur, and where the new system must intervene.

Key Terms & Techniques

• BPMN (Business Process Model and Notation) – A standardized set of symbols (events, activities, gateways, flows) for detailed process diagrams. Knowledge Area: Analysis; Deliverable: BPMN diagram (often the “As?Is” and “To?Be” models).
• Flowchart – A simple, informal diagram using boxes and arrows (process, decision, start/end) to illustrate a sequence of steps. Knowledge Area: Analysis; Deliverable: Flowchart (quick?view for stakeholders).
• SIPOC (Suppliers?Inputs?Process?Outputs?Customers) – A high?level map that defines the boundaries of a process and its key elements. Knowledge Area: Strategy Analysis (often used in the Define Future State activity); Deliverable: SIPOC diagram.
• Swimlane Diagram – A BPMN or flowchart variant that groups activities by role, department, or system. Knowledge Area: Analysis; Deliverable: Swimlane diagram (helps clarify responsibilities).
• Gateway (BPMN) – Decision points (exclusive, inclusive, parallel) that control the flow. Knowledge Area: Analysis; Deliverable: BPMN diagram with gateways.
• Event (BPMN) – Anything that starts, ends, or interrupts a process (Start, End, Intermediate). Knowledge Area: Analysis; Deliverable: BPMN diagram with events.
• Process Decomposition – Breaking a complex process into sub?processes or activities to keep models manageable. Knowledge Area: Analysis; Deliverable: Hierarchical BPMN or flowchart set.
• Stakeholder Map – A visual of who influences or is impacted by the process; often attached to the model for context. Knowledge Area: Stakeholder Management; Deliverable: Stakeholder map (input to modeling).
• Verification & Validation – Checking that the model accurately reflects the real process (verification) and that it meets stakeholder needs (validation). Knowledge Area: Analysis; Deliverable: Signed?off model.
• Baseline Process – The “As?Is” model that becomes a reference point for measuring improvement. Knowledge Area: Analysis; Deliverable: Baseline BPMN/flowchart.

Step?by?Step / Process Flow

1. Identify & Scope the Process – Use a SIPOC or stakeholder interview to decide which end?to?end activity you will model (e.g., “New Customer On?boarding”).
2. Gather Detailed Information – Conduct workshops, observation, and document analysis to capture each step, decision, and hand?off.
3. Choose the Modeling Notation – Decide whether BPMN (for detailed, technical audiences), a simple flowchart (for quick stakeholder review), or a SIPOC (for high?level view) is most appropriate.
4. Create the “As?Is” Model – Draft the diagram, using swimlanes to show who does what; include events, activities, and gateways.
5. Validate With Stakeholders – Walk the diagram in a review session, capture feedback, and obtain sign?off.
6. Design the “To?Be” Model – Incorporate the new solution (e.g., CRM automation), remove waste, and highlight changes. Document the differences for the Requirements Specification and for later Solution Evaluation.

Common Mistakes

Certification Exam Tips

Quick Check Questions

1. Scenario: After a requirements workshop, the team cannot agree on which steps belong to the “order?fulfilment” process. Which technique should the BA use?
   Answer: SIPOC – it clarifies the process boundaries (Suppliers, Inputs, Process, Outputs, Customers) and helps the team agree on what is in?scope.

2. Scenario: A stakeholder asks for a visual that shows who does each activity in the “claims?adjustment” process. Which diagram is most appropriate?
   Answer: Swimlane diagram (BPMN or flowchart) – it groups activities by role or department, making responsibilities clear.

3. Scenario: The BA has an “As?Is” BPMN diagram but the project sponsor wants a quick?look version for the steering committee. What should the BA provide?
   Answer: Flowchart – a simplified, high?level view that omits technical gateways but still shows the sequence of major steps.

Last?Minute Cram Sheet (10 One?Liners)

1. BABOK Knowledge Area for Process Modeling: Analysis (plus occasional Strategy Analysis for SIPOC).
2. BPMN = Business Process Model and Notation – the standard set of symbols for detailed process diagrams.
3. Flowchart = informal, box?and?arrow diagram; best for quick stakeholder reviews.
4. SIPOC = high?level map; defines Suppliers, Inputs, Process, Outputs, Customers.
5. Swimlane = visual grouping by role/system; used in both BPMN and flowcharts.
6. Gateway = decision point in BPMN (exclusive, inclusive, parallel).
7. Event = start, end, or intermediate trigger in BPMN.
8. Verification vs. Validation – verification checks model accuracy; validation checks stakeholder fit.
9. Exam trap: “The BA creates the BPMN diagram.” The BA facilitates and ensures correctness; the diagram may be produced by a modeler.
10. Baseline Process = signed?off “As?Is” model; serves as the reference for measuring improvement.

Good luck—model your study plan as carefully as you model a process, and you’ll pass the exam!