November 1, 2022
Business Process Modeling
What is Process? (Goal and Value)
Start point
Sequence of actions
End point
Business
Sales and Marketing
Finance and accounting
HR
Core Business Activity Team
Public Relations
How the business is happening currently?
Project context
What is the domain of the business?
What is the scope of the project?
(Project context within business – domain
context)
Hospital – Providers or physician services
Health Insurance – Insurance companies that are
offering health policies
Pharmaceuticals – Researchers, manufacturing,
distribution
Discovery Session (Initial meeting)
What are the business processes involved in
this project?
Who are all the stakeholders involved in this
project?
Applying a Bank Loan (Personal) – Process Name (Verb)
Business Language – terminologies
Subject + Verb + Object
Start Point – What is the intention to start this process?
When a customer intended to get a loan from the bank.
Step 1: Customer walks into the bank
Customer asks for the form
Bank Rep gives the form
Customer fills the form
Bank Rep verified the form
Bank Rep submits the form to bank manager
Bank Manager initiates verification
Verification team completes verification process
Verification team submits report to Bank manager.
Bank Manager approves the loan.
End Point
What is the value
Customer is getting a loan
Bank is getting some business
Who are stakeholders involved in this process?
1. Customer
2. Bank Rep
3. Verification Team
4. Bank Manager
Exercise: Write Business process
UML – Unified Model Language
BPMN – Business Process Modeling Notation
Notations – symbols
Visual representation
Any of the tools that BA uses, you need to understand
that these tools will be having their own saving formats.
Save them in their own format first and then later you
will be having the options to convert them into png, jpg,
pdf formats.
Installation based application
License based
Web-based applications
MS Visio - licensed
BPMN -
Bizagi – installation-based
Draw.io – web-based
Lucidchart – web-based
Process Flow Diagram/Activity Diagram/Flow
Charts/Swimline diagrams
Notations
Start point
Action
Control Flow
Decision
Join
Fork
End Point
November 2, 2022
November 3, 2022
Fork
Join
Swimlane Diagram/ Swimlane Process Diagram
AS-IS BUSINESS PROCESS FLOW
S. No BR No Description FR No
1 BR001 walks into
the bank
2 BR002 asks for
the form
3 BR003 fills the
form
4 BR004 gives the
form
Converting or translating BR into FR
What system can do?
C - Create
R - Retrieve
U - Update
D – Delete
There is an action that is there BR, system can do
the same action
There is an action that is there BR, system can do it
alternatively
There is an action that is there BR, system cannot
do it
Customer opens the system (app/url)
Customer clicks on “Apply Loan”
Customer navigates to Loan Details page.
System opens the form
Customer fills the form
Exercise: Create Swimlane diagram for the above
process
November 4, 2022
Any business is going to have a business process
1) Studying existing (AS-IS business process)
a. Business is not at all having any system, looking
for IT solution (new system)
b.Business is partially having system, looking for
IT solution (Enhancement)
c. Business is having system, looking for IT
upgradation (FE/BE/DB)
2) Futuristic state of business process (TO-BE process)
Functional Requirements
Register
Login
Forgot Password
Reset Password
Customer opens the system (app/url)
Customer clicks on “Apply Loan”
Customer navigates to Loan Details page.
System opens the form
Customer fills the form and submits
Bank Rep verified the form = accept or deny (sends
message to customer for additional documentation)
Bank Manager initiates verification
Verification team updates the verification process
Bank Manager approves/deny the loan.
Role configuration
What system can do
Register
Login
Forgot Password
Reset Password
All functional requirements are nothing but use cases.
What is a Use case?
Use case is an interaction between system and user.
Use Case Diagram
UC No Use Case Description
(verb)
UC001 Register
UC002 Login
How system will do this action?
Use Case Description
Use Case ID UC001
Use Case Name Register
Created By BA Last Updated By
Date Created Last Revision Date
Actor Customer, Bank Manager
Description This use case describes how user registers with the system
Trigger Point This use case starts when user intends apply for a loan
Pre-condition User should have an internet connection
User should have an internet browser (Chrome)
User should have a valid registered email ID
Post-condition User successfully registered
Normal Flow of Step 1: User clicks on internet browser
events/Basic Step 2: System opens the internet browser
Flow/Happy Path Step 3: User enters URL of the application and clicks on enter button
(As if it is going to Step 4: System navigates the user to home page of the application
happen) Step 5: User clicks on Register button that is available on the right hand top
corner.
Step 6: System navigates the user to “Registration page.”
Step 7: User fills the form (attributes to written) and clicks on “Submit”
button.
Step 8: System validates the information and displays message “Successfully
Registered.”
Step 9: Basic Flow ends here
Alternative Flow At step 5, user can alternatively click on “Register” available under the menu
of “XXXXX”. Step 6 to 9 follows.
At step 7, if user is not filling any of the mandatory fields, system displays
message “* indicates mandatory.”
At step 7, if user is filling the form and clicking on “Cancel” or “Close (x)
button”, system navigates the user to home page of the application.
At step 8, if system fails to validate the info, displays message as “user
already exists, please login.”
Exceptions If user lost the internet connection, system displays message “check your
internet connectivity”
Frequency of Use High
Assumptions It is assumed that name is going to be as a single field
It is assumed that SMS integration is going to happen
Business Logics User receives SMS on successful registration
Not supposed to use words: Some, Few, Etc.
Exercise: Write Use Case description for Login
Create use case diagram
November 7, 2022
User Interface (UI) – whatever the end user sees in the
application
What is a use case?
Interaction between user and system.
Mockups (visual representation of the requirement) will
be created for the User Interfaces that user sees
Mockup Tools
Balsamiq, Axure Pro, Pencil, SmartDraw, draw.io
Data Table
Field Input Type Lengt Mandato Remark
Name/Attrib h ry s
ute
First Name Alphabets 20 No Allow
special
characte
rs (-, ‘)
Last Name Alphabets 20 No Allow
special
characte
rs (-, ‘)
Email ID alphanume 50 Yes Should
ric be a
valid
email,
@,
domain
Country Drop Down Yes
Code
Phone Numeric Yes 10 digit
Number number
Date of Birth Date Picker
Submit Button
Cancel Button
Input Types
Alphabets
Text
Numerics
Alphanumerics
Date Picker
Free Text (500 char)
Project context (I want a mobile banking application)
Process/People (stakeholder/user or personas –
friction)
Identifying Business process
Listing out the stakeholders and actions
BR – All business requirements
FR – Identifying whether a BR can be converted into FR
FR are nothing but Use Cases.
User stories are the functional
requirements from the user perspective
FR/Use Case/User Stories
Use Case Description (complete details) – Pre
condition/Post condition/Basic Flow/Alternative Flow
Acceptance Criteria (complete details) – is
identifying the conditions in which the user story gets
satisfied
Given the situation
When doing
Then what is going to happen
Positive scenario/negative/Alternate
Process flow diagrams/use case diagram or any other
diagrams – agile?
No
Doing the documentation will help you in reducing
interactions
REQUIREMENT ENGINEERING
Identifying and listing Stakeholders
Facilitating Meeting
Elicitation techniques
Sorting the requirements
Prioritizing the requirements
Verifying the requirements
Validating the requirements
Enterprise Analysis
PESTLE
Root cause analysis (Fish Bone Analysis)
SWOT
POLDAT