SCENARIO1: PRODUCT-INSURANCE POLICY

SCENARIO2: UPLOAD MANDATORY DOCS

BUSINESS REQUIREMENTS DOCUMENT (BRD)

Version: 1.0
Version 1.0 Business Requirement Document: XYZ INSURANCE PVT. LTD

Authorization

DOCUMENT NAME REQUIREMENT DOCUMENT FOR SCENARIO-1, SCENARIO-1

DOCUMENT VERSION 1.0

EFFECTIVE DATE 27TH JULY, 2020

DOCUMENT OWNER BUSINESS SOLUTIONS GROUP (BSG)

DOCUMENT APPROVER PROCESS OWNER

DOCUMENT RESTRICTED
CLASSIFICATION

Version History

VERSION # DATE AUTHOR DESCRIPTION

1.0 27TH JULY, 2020 BUSINESS Initial Document prepared based on

Consultant the concept note received with inputs
from business users.

This document has been approved as the official Business Requirements Document for
‘Scenario-1’, ‘Scenario-2’, and accurately reflects the current understanding of
business requirements. Following approval of this document, requirement changes will
be governed by the project’s change management process, including impact analysis,
appropriate reviews and approvals.
Version 1.0 Business Requirement Document: XYZ INSURANCE PVT. LTD

Ownership

Business Solutions Group (BSG) is the owner of this document. Unless otherwise
specified, no part of this document may be reproduced or utilized in any form or by any
means, electronic or mechanical, including photocopying and microfilm, without
permission in writing from (BSG). Similarly, distribution of this document to a third party
is also prohibited unless specific approval is taken from (BSG).

Document Approvals

Approver Name Project Role Signature/Electroni Date

c Approval

ABC PROCESS OWNER 27TH JULY, 2020

Version 1.0 Business Requirement Document: XYZ INSURANCE PVT. LTD

Table of Content

PROJECT DETAILS..............................................................................................5
OVERVIEW..........................................................................................................5
GLOSSARY OF TERMS.........................................................................................5
1. REQUIREMENT OVERVIEW AND BACKGROUND............................................6
2. STAKEHOLDERS...........................................................................................8
3. BUSINESS REQUIREMENT............................................................................8
3.1. FUNCTIONAL REQUIREMENT........................................................................8
3.2 NON-FUNCTIONAL REQUIREMENT...............................................................9
4. USE CASES.................................................................................................10
5. KEY ASSUMPTIONS AND EXCLUSIONS.......................................................13
APPENDIX........................................................................................................14
Version 1.0 Business Requirement Document: XYZ INSURANCE PVT. LTD

PROJECT DETAILS

Project ID 123456

Scenario 1- Product-Insurance Policy

Project Name
Scenario 2- Mandatory Doc Upload
Project Type Process Enhancement

Project Scope  Website Enhancement

 External web apps
Project Start Date 1st August 2020

Project End Date TBD

Project Manager ABC

OVERVIEW
This document defines the high level requirements for ‘Scenario 1 & 2’. It will be
used as the basis for the following activities:

 Creating solution designs

 Developing test plans and test cases
 Determining project efforts
 Determining project delivery timelines

GLOSSARY OF TERMS

Term Explanation

ABC,XYZ,PQR,LM
Name representation
N

PG Payment Gateway
Version 1.0 Business Requirement Document: XYZ INSURANCE PVT. LTD

1. REQUIREMENT OVERVIEW AND BACKGROUND

This document covers the approach to provision XYZ INSURANCE to be able to sell
Insurance Policies to the customer base via their website and fulfil successful sales
transaction by uploading mandatory documents required for the purchase to
complete.

1.1.Current Process (As-Is):

The sale of insurance policies follows a traditional approach in current process

wherein a sales representative/executive connects with potential lead, showcases
various offering as per requirement and eligibility, later customize as per the
customer’s needs. The requirement is to enable the company’s website to have an
option to showcase their product and also support sales transactions post upload of
all required documents.

1.2.Proposed Process (To-Be):

 To Enable the Insurance Company to sell insurance policies offered online to
their customers via their website.
 To assist the customer in uploading mandatory documents required for policy
purchase and make payment via PG.
Version 1.0 Business Requirement Document: XYZ INSURANCE PVT. LTD

Process Flow Diagram (To-Be):

1.3.Key Pain areas:

 There is lot of manual processing involved due to which efficiency of the
complete process is hampered as it takes more time.
 The data updated may not be organic due to presence of human errors and
thus affecting the overall quality of the process.
 Lack of an online process, to showcases Insurance Company’s product and
offering to customer.
Version 1.0 Business Requirement Document: XYZ INSURANCE PVT. LTD

2. STAKEHOLDERS

The following comprises the internal and external stakeholders whose requirements
are represented by this document:

Sr.N Role
Stakeholders Name
o
1. ABC Business consultant

2. PQR Process Owner

3. XYZ User

4. LMN Development teams

3. BUSINESS REQUIREMENT
The requirements in this document are prioritized as follows:
Valu Description
Rating
e
1. Critical This requirement is critical to the success of the project. The
project will not be possible without this requirement.
2. High This requirement is high priority, but the project can be
implemented at a bare minimum without this requirement.
3. Medium This requirement is somewhat important, as it provides
some value but the project can proceed without it.

3.1.FUNCTIONAL REQUIREMENT

Following are functional requirements:

REq Priority Description Impacted Stakeholders
ID
General / Base Functionality

FR-01
1 The User should be able to Development teams
Browse the product catalog
hierarchically sorted by
alphabetically by product name,
Category, rating, etc.
FR-02
1 The user should be able to do Development teams
full document upload, modify
and view upload, see upload Integration engineers
status and submit request
Version 1.0 Business Requirement Document: XYZ INSURANCE PVT. LTD

REq Priority Description Impacted Stakeholders

ID
FR-03
3 The user should be able to view Development teams
transaction status, approval
status, policy details and cancel Integration engineers
or re-new.

Security Requirements
FR-04 2
Since we are performing Development teams
commercial translations and
dealing with confidential data. Integration engineers
All transactions should be
3rd party Vendors
secure.

3.2 NON-FUNCTIONAL REQUIREMENT

Following are Non-functional requirements:

Requirement
REq ID

NFR-01 The technical requirements may address the page display

speed, compatibility with browsers and hardware platforms.

NFR-02 The technical requirements may address download or response times,

application access, redundancy procedures, Load, number of users etc.

NFR-03 The system should be very much user-friendly for end users.

NFR-04 The final system should support high traffic loads.

NFR-05 The system should be able to handle various upload file extensions, Ex:
.pdf,.tiff,.png,.jpeg, etc.

NFR-06 The final system should support storing the uploaded documents until
retention period.

NFR-07 The system should support pushing the uploaded documents to destination
system pre-purge period.

NFR-08 The system should support retrieving the uploaded documents and
requests raised for from source system post-purge period in case any
inquiry.
Version 1.0 Business Requirement Document: XYZ INSURANCE PVT. LTD

4. USE CASES
Listed below are the use cases describing the interaction between actors and the
different system.
The primary purpose of this Use Case is to capture the required system behavior
from the perspective of the end-user in achieving one or more desired goals.

Use Case ID: UC-1

Use Case Name: Browse the product (Insurance Policy) on Website
Created By: Rishu Sinha Last Updated By:
Date Created: 27/07/20 Date Last Updated:

Actors: User
Description: This use case describes the main way the policy selection
will occur on company’s website. The user accesses the
appropriate URL and interacts with the functionality made
available.
Preconditions: Internet Connectivity, Web browser opened, and website
URL accessed.
Post conditions: User navigates through product offerings on web site.
Normal Course: 1. Open browser
2. Navigate to website via click on URL
3. Interact with the website using available functionality of
customer identification
4. Select relevant policy as per eligibility and upon compare
5. Proceed to premium and sum insured selection
6. Upload relevant documents upload, Complete the
payment online.
Alternative Courses: None
Exceptions: 1. Closing browser Midway
2. Network Failure
3. Click on any external links
Includes:
Priority: High
Frequency of Use: Once per visit.
Business Rules TBD…
Special Requirements:  24/7 access
 Response times comparable to common web based
solutions (e.g. Reliance general Insurance)
 User to be assisted by representative in case an enquiry
is raised
 User to be notified via Email and SMS Communications.
Version 1.0 Business Requirement Document: XYZ INSURANCE PVT. LTD

Use Case ID: UC-2

Use Case Name: Payment for the product (Insurance Policy) selected
Created By: Rishu Sinha Last Updated By:
Date Created: 27/07/20 Date Last Updated:

Actors: User
Description: This use case describes the main way post policy selection
payment to be processed via partnered payment gateway
website. The user accesses the appropriate URL and
interacts with the functionality made available.
Preconditions: Internet Connectivity, Web browser opened, and gateway
URL accessed.
Post conditions: User navigates through payment offerings on web site and
establishes connection with payment gateway.
Normal Course: 1. Open browser
2. Navigate to website via click on URL
3. Interact with the website using available functionality of
customer identification
4. Filter Your Search According to Your Requirement.
5. Compare Your Shortlisted Plans.
6. Proceed to premium and sum insured selection
7. Complete the Documentation.
8. Select from the payment options available
9. Complete the payment online via payment gateway
10. Land on details page, with order status
Alternative Courses: None
Exceptions: 1. Closing browser Midway
2. Pressing back of browser refresh during payment
3. Network Failure
4. Click on any external links
Includes:
Priority: High
Frequency of Use: Once per visit.
Business Rules TBD…
Special Requirements:  24/7 access
 Response times comparable to common web based
solutions (e.g. Reliance general Insurance)
 User to be assisted by representative in case an enquiry
is raised
 User to be notified via Email and SMS Communications.
Version 1.0 Business Requirement Document: XYZ INSURANCE PVT. LTD

5. KEY ASSUMPTIONS AND EXCLUSIONS

Following are few assumptions and exclusion w.r.t this requirement:

# Assumptions

Using existing resources and partners.

Sharing XYZ ecommerce website for payment processing

Using ABC external system to fetch relevant customer offers

Using LMN external service to validate customer records ‘if existing’

# Exclusions

No data massaging will be done as part of this enhancement

All the systems involved must be functional and provide real-time response

Any network failure will lead to loss of current progress and journey will be needed
to restart from initiation point
Version 1.0 Business Requirement Document: XYZ INSURANCE PVT. LTD

APPENDIX
A. Document Upload Process Flow: