Business System Analysis Practical Toolkit

Business System Analysis:

Practical Tools and

Techniques

BY MOHSIN BAIG

Target Audience

Individuals seeking to work as a Business or System Analysts in any Investment Banking or Retail Banking organisation or in any large organisation.

Existing Business or System Analysis seeking to widen their Business System Analysis techniques.

Business Analyst seeking to become Senior or Lead BA’s

Individuals seeking to develop a superior level of Business and System Analysis skillset that will enable them to speedily get sign offs from there project stakeholders for there Business Requirements and System Requirements Documentations.

Individuals seeking a practical Business System Analysis course that trains techniques which are utilised in a project environment.

Training Objectives

Empower Professional, Experience, Entry Level and Mid Level

Business and System Analysts to develop effective practical tools

and techniques that can be used a project environment.

Coach Business and System Analysis in the usage of the

techniques through Guidance and Principles.

Demonstrate the effectiveness of the Techniques and Tools

through Practical Case Study Examples and Solutions for a project

environment

Business System Analysis Training

Syllabus

Section 1


Syllabus

MODULE: 1

Business Process Modelling (Baseline Viewpoint)

Practical Work Based Guidance and Principles

Case Study 1: Online Banking Loan Application

MODULE : 2

Business Process Modelling (Target Viewpoint)


Cast Study 2: Online Banking Loan Application


Syllabus

MODULE: 3

Functional Requirements Elicitation (Baseline Viewpoint)



MODULE: 4

Functional Requirements Elicitation (Target Viewpoint)




Syllabus

MODULE : 5

Use Case Modelling


Case Study 1: Payment Trading Plc

MODULE: 6

Functional Gap Analysis


Case Study 2: Payment Trading Plc


Syllabus

MODULE: 7

Business Requirements Elicitation (Target Viewpoint)


Case Study 1: Moore Financial Services


Syllabus

Section 2


SyllabusMODULE: 8

Business System Requirements Workshop


MODULE: 9

Application Screenshot Modelling



Syllabus

MODULE: 10

Reverse Engineering

Practical Project Guidance and Principles

MODULE: 11

Target Operating Model



Syllabus

MODULE: 12

Business Process Catalogue


MODULE: 13

System Process Catalogue



Syllabus

MODULE: 14

Requirements Traceability Matrix


MODULE: 15

Swimlane Diagram (Horizontal or Vertical)



Syllabus

MODULE: 16

Agile User Stories


MODULE: 17


Syllabus

MODULE: 17

Requirements Scoping


MODULE: 18

Sequence Diagram



Syllabus

MODULE: 19

Structured Walkthrough


Course Structure and Contextual

Definition The Technique section of the course incorporates the following

framework to put contextual definition around all of the business

system analysis techniques:

“High Level Description”: This area defines the attributes of the technique.

“Pre-Condition” : This area defines the necessary requirements or criteria in order to effectively use the technique

“Benefits Realisation”: This area describes the value add of using the technique.

“Documentation”. This area defines the name of the typical work document in which the technique often is arranged in.

“Stakeholder Dependency”. This area defines which project stakeholders within the project are often dependent on the output of the technique.

Course Structure and Framework

The “Practical Project Guidance and Principles” section defines the work steps that Business System Analysts can implement in a Project environment

The Case Study Section which is only applicable in Section 1 techniquesdraws practical guidelines from the User Steps highlighted in the Practical Guidance and Principles based on the given Case studies.

The Exercise Section lists a case studies and tasks which attempts to rigorously reinforce learning of all the business and system analysis techniques.

Module 1

Technique Section:

Business Process Modelling

(Baseline Viewpoint)

Learning Objectives

Develop a high level business system understanding of the “As Is” Process mapping viewpoint.

Develop an understanding of the required steps that will enable you to deliver a “As Is” Process Map(s) to your target stakeholders

Develop an understanding of all the attributes and requirements that need to be elicited from business stakeholders in order to produce a baseline viewpoint of the Business Processes in scope.

Develop quality control guidelines and stakeholder management tactics to achieve the signing off of Business Process Map(s) signed off by stakeholders.

Develop an insight in how technique can be practically applied and utilised based on a Case Study narrative.

Develop “As Is” Process Modelling skills.

High Level

Description

"As Is" Business Process Maps are used to map out the existing business

users and the functionality within the business process. The "As Is" Business

Process defines the high level business scenario and encompasses all the

user and system touch points that take place within the business process.

Pre-Condition Business Analyst must collate the Analysis and User steps from the business

stakeholders who would most likely be the subject matter domain experts

on the process in scope.

Benefits Realisation Provides high level visual contextual description of the Requirements,

scenario and stakeholders impacted

Documentation Business Requirements Documentation (BRD)

Stakeholder

Dependency

System Analysts would use the high level business process maps to identify

the scope of the business process and all the impacted stakeholders.

Practical Project Guidance and

Principles Section

To Identify and Map out an existing “As Is” business process a Business System

Analyst could adopt the following steps:

Step 1: Conduct a Workshop with existing business and IT Stakeholders that have the domain

knowledge on the identified business processes.

Step 2: Identify all the Users that are involved in the Business Process.

Step 3: Identify all the business steps that are performed by the business users to complete the

business process at a high level.

Step 4: Identify all systems that are impacted in the business process at a high level.

Step 5: Identify all the business rules that are associated within the business process especially in

Step 3.

Step 6: Identify all the Manual Inputs and System Outputs.

Step 7: Identify all the business user dependencies.

Step 8: Map out a draft cut of the business process using a UML Diagram or BPMN Diagram.

Step 9: Circulate the draft cut of the “As Is” Process Map to the relevant business and IT

stakeholders in the project

Step 10: Collate the feedback on the “As Is” Process Map and apply the updates to the

process map.

Step 11: Circulate the Process Map to the relevant stakeholders to ensure all the necessary

changes have been applied.

Step 12: Conduct a 2nd workshop to baseline the “As Is” Process Map to ensure validation

for sign off purposes.

Step 13: Send out the updated Process Map from Step 12 to the relevant business and IT

stakeholders via email asking for sign off via e-mail confirmation as part of your

audit trail.

Step 14: “As Is” Process Map is complete insert it into a Business Requirements

Documentation.

Case Study Scenario

Problem Statement Map out how existing business customers complete an online

loan application using the existing online banking solution.

User Business Customer

Solution Online Banking Portal, Experian Solution

Business Rules Customer must be an existing banking customer.

Customer must have valid login credentials and password

Customer must have an existing personal business account

with the bank

Solution = Process Steps:

Step 1: Customer Logs into online portal.

Step 2: Customer selects business loan application.

Step 3: Customer completes personal details section.

Step 4: Customer completes the business section.

Step 5: Customer Read the Credit search statement.

Step 6: Customer accepts terms and conditions of the application.

Step 7: System performs Experian web services for credit checking and searching purposes

on client application.

Step 8 : Customer is approved or not approved for the Loan and is given online notification

of the status –End Process.

See the Next Slide for

the Example of the

Business Process Map

“As Is” Process Mapping Exercise

Barry Freeman works as a Lead Payment processor for Visio Bank Limited which is aretail bank that specialises in Credit and Debit transfers of International Payments forlocal UK customer who are sending payments to the European, US and Asian Markets.Barry is responsible for the processing of the payments in the back office for theEuropean Markets and delegates the remaining US and Asian market payments to hisx 10 team members. These are global payments which have failed to reach its marketdestination due to system failures and consequently have to be processed manuallyby an employee on behalf of the customer using the details from the systemgenerated report before the next working day. The payment reports contain thefollowing Field names and populated details : Source of payment, PaymentBeneficiary, Timestamp date, Source Bank, Destination Bank, Destination Date,Currency type, Currency Amount, Bank IBAN, Payment type, Payment reference ID.

Barry is also responsible for validation of all data contained with the reports. He is alsoresponsible for ensuring that his team members complete the payment transfersbefore the close of the working day. Barry and his team also needs to keep an audittrail of all the payments that have been processed, outstanding payments, paymentsthat have failed, accounts with insufficient funds.

Exercise Tasks

Task 1

Write out a high level textual description of all the Business User Steps

that are involved

Task 2

Develop an “As Is” Business Process Map that captures all the

Business User Steps and all the impacted Business and IT

stakeholders.

Module 2

Technique Section : Business Process

Modelling (Target Viewpoint)

Education

Business System Analysis Practical Toolkit