Business Requirement Specification

<Blaze>

Business Requirements Specification

For
<Equation Module for All Motor products (package & liability
only)>

Page 1 of 22

Business Requirement Specification

<Blaze>

Table of contents

1
2
3
3.1
3.2
3.3
3.4
4
4.1
4.2
4.3
4.4
4.5
4.6
5
5.1
5.2
6

Introduction
Business Process Overview
Business Processes
List of business processes impacted
Details of the business processes impacted
Business need and reason for change
Business Benefits
Detailed Business Requirements
Functional requirements
Non-functional requirements
UI requirements
Reporting requirements
Legal and compliance requirements
Other requirements
Additional Information
Impact of CR on other interfaces or systems
Type of Change
Appendix

Page 2 of 22

4
4
5
5
5
5
5
6
6
6
6
6
6
6
7
7
7
7

Business Requirement Specification

<Blaze>

DOCUMENT CONTROL
Application: <Blaze>
Whizible Number

CR-8036-31810

Author

Mr.Neyaz Ahmed

Reviewed by
To be approved by

Mr.Udayan Joshi
Mr.Amitabh Jain

Initiator Name

Mr.Neyaz Ahmed

Initiating Vertical Name

Customer Service Motor

Business Process/Product

Motor-All Products

Cost Center details

099-54900

Priority (High/ Low/ Medium)

High

Contact person from initiating

group. In case of doubts/
clarifications

Neyaz Ahmed/Ankit Parekh

Version History
Version

Amendment(s)

Date

Amended By

Reviewed By

Signed Off By

0.1
0.2
Related Documents
Ref.:

Document Name

Title

Distribution List and Sign-Off

Name

Role

Vertical

Sign-Off Required

Sign-off Obtained

Amitabh Jain

VP

CS-Motor

Yes/No
Yes/No
Yes/No

Yes/No
Yes/No
Yes/No

Page 3 of 22

Business Requirement Specification

<Blaze>

1. Introduction
Introduction of the Equation Module & renewal rule engine for Motor products in
blaze & pathfinder
Transaction type-All
Policy type Package & Liability only

2. Business Process Overview

There will be change in the calculation logic of Basic OD rate for all motor
products.
The current logic of Grid I ,II,III,IV & V to be removed for ascertain of basic OD
rate. Other calculation post deriving of Basic OD rate will remain unchanged.
Basic TP premium will also be computed in blaze

3. Business Processes
3.1

List of business processes impacted

The below business process will be impacted

All webservices (Iagent/ILPOS/Echannel/SOA/Renewal to Motor policy
issuance)
Renewal
Endorsement
Premium Calculator

3.2

Details of the business processes impacted

There will be change in all motor webservices due to change in the calculation logic
of basic OD.
During renewal & endorsement of the policy , impact of changes should be
considered (details provided in functional requirement section)

3.3

Business need and reason for change

Giving the flexibility for the pricing as per the define parameters & to have a risk
base pricing module.
Automation of the renewal policy through allied system

Page 4 of 22

Business Requirement Specification

<Blaze>

3.4

Business Benefits

Flexibility in pricing & UW control with exceptional call configurability through

system

Page 5 of 22

Business Requirement Specification

<Blaze>

4. Detailed Business Requirements

4.1
Req.
ID

Functional requirements

Requirement Description

Notes/
Issues

Page 6 of 22

Business Requirement Specification

<Blaze>
FR1.0

For Blaze changes

<If
Any>

With the introduction of Equation Module , the Basic OD rate & Basic TP premium will be derive from the
define parameters
The equation will be base on the below categories
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.

Parameter master
Relative of parameters
Severity master
Target Loss Rate (TLR) master
Fixed factor master
Additional charge master (Grid 1)
Equation of Own Damage
Exceptional rules
IL_Tariff
IMT-Tariff (Grid 1)
File Product Reference (Validation)
NCB Masters & count of claim
Endorsement
Add-on Applicability
Third party premium
IDV master

1.Parameter-There will be defined parameters for the calculation of basic own damage rate along with the
relation with the Severity/LR masters. Parameters to be used for basic TP premium computation also

Case sensitive to be ignore in the parameter name

List of parameters are as per the attachment
Descriptions

Mand
atory

IL product code eg.3001, 3001/A,3003,3003/A

Type Of Business

Direct/Intermediary

Transaction type

New/Rollover/Used/Renewal

Manufacture code of the vehicle.

Model cluster of the vehicle.

Model code

Vehicle sub class code(is applicable for

commercial products only)

*N

Gross Vehicle weight of the vehicle (applicable

for GCV products only)

*N

Carrying capacity

*Mandatory for PCV Products

*N

Seating Capacity

*Mandatory for PCV Products

*N

Public/Private carrier(applicable for GCV

products only)

*N

Parameters
Product (Product CODE)

VEHICLE MANUFACTURER CODE

Model Cluster
Model code
Vehicle Subclass

Gross Vehicle Weight

Policy class
Cubic Capacity

NUMBER OF WHEELS

Page 7 of 22

Business Requirement Specification

<Blaze>
FR2.0

2.Relativity
Relativity stance can be define on the basis of different parameters which are define above
Example as below

DT_Relativity_Privatecar_Rollovertransaction
paramter parameter Relati
policyStartDate
Name
Value
vity
Oct 19, 2011 <= ..<=
NCB%
35%
Oct 19, 2020
-0.915
Oct 19, 2011 <= ..<=
NCB%
45%
Oct 19, 2020
1.0509
Oct 19, 2011 <= ..<=
NCB%
=>50%
Oct 19, 2020
1.6833
Oct 19, 2011 <= ..<=
Age
4 <= ..< 5
Oct 19, 2020
0.35
Oct 19, 2011 <= ..<=
Age
5 <= ..< 6
Oct 19, 2020
0.2621
Oct 19, 2011 <= ..<=
Age
6 <= ..< 7
Oct 19, 2020
0.1766
Oct 19, 2011 <= ..<=
Age
7<=
Oct 19, 2020
0
Oct 19, 2011 <= ..<=
ModelCLus
PM1
Oct 19, 2020
tor
1.1422
Oct 19, 2011 <= ..<=
ModelCLus
PM2
Oct 19, 2020
tor
1.1422
Oct 19, 2011 <= ..<=
RTOClustor PL1
Oct 19, 2020
0.9749
Oct 19, 2011 <= ..<=
RTOClustor PL2
Oct 19, 2020
0.7259
In the above example: Relativity define for Private car Rollover transaction
There should be option to define the relativity on the basis of different parameter as an instance
Example of instance : DT_Relativity_Privatecar_Rollovertransaction_Age >3.1_Echannel
Under the parameter value there should be option to define the value with the below conditions, default
condition should be AND if no codition mentioned
1.
2.
3.
4.
5.
6.
7.

Between
Equal to (=)
Not equal to (<>)
>
=>
<
<=

Note:Effective date will be considered on the basis of policy start date

FR3.0

Severity Master (SR)

There should be instance for defining the Severity amount on the basis of different parameter.
Instance can be define on the basis of Product, transction type & other parameters .

Page 8 of 22

<If
Any>

Business Requirement Specification

<Blaze>
There should not be any limits select the no. of parameters while define the instance
Severity amount will be provided by the UW in the rules of the severity on the basis of different parameters
Under the parameter value there should be option to define the value with the below conditions, default
condition should be AND if no codition mentioned

1.
2.
3.
4.
5.
6.
7.

Between
Equal to (=)
Not equal to (<>)
>
=>
<
<=

Example table attached

Severity master.xls

Note:Effective date will be considered on the basis of policy start date

FR4.0

Target Loss Ratio (TLR) Master

There should be instance for defining the Target loss ratio on the basis of different parameter.
Instance can be define on the basis of Product, transction type & other parameters.
There should not be any limits select the no. of parameters while defining the instance
Value of the TLR will be provide by UW , in percentage value
Under the parameter value there should be option to define the value with the below conditions, default
condition should be AND if no codition mentioned
1.
2.
3.
4.
5.
6.
7.

Between
Equal to (=)
Not equal to (<>)
>
=>
<
<=

LR master.xls

Note:Effective date will be considered on the basis of policy start date

FR5.0

Fixed Factor Master (FF)

There should be instance for defining the Fixedfactor on the basis of different parameter.
Instance can be define on the basis of Product, transction type & other parameters.
There should not be any limits select the no. of parameters while defining the instance

Page 9 of 22

Business Requirement Specification

<Blaze>
Value of the FF will be provide by UW , the same may be in percentage format or in decimal format both
positive & negative numbers
Under the parameter value there should be option to define the value with the below conditions, default
condition should be AND if no codition mentioned
1.
2.
3.
4.
5.
6.
7.

Between
Equal to (=)
Not equal to (<>)
>
=>
<
<=

Fixed factor
master.xls

Note:Effective date will be considered on the basis of policy start date

FR6.0

Routemaster
Under the Route master, UW can define the instance on the basis of parameters including product to define the
route for calculation of Basic OD rate & TP Premium
Under the parameter value there should be option to define the value with the below conditions, default
condition should be AND if no codition mentioned
1.
2.
3.
4.
5.
6.
7.

Between
Equal to (=)
Not equal to (<>)
>
=>
<
<=

UW should have the option to define instance for Routemaster on the basis of parameters for each products with
start date & end date logic

RouteMap_Instance.
xls

In routemap , there will be condition on the basis of which route map will be define
Change in the Routemaster of Add-on:
Route Master for Add-on covers should also be changed in line with the equation .
Route master of Add-on will be define on the basis of individual Add-on cover , product wise by defining in the

Page 10 of 22

Business Requirement Specification

<Blaze>
instance

Note: Effective date will be considered on the basis of policy start date
FR7.0

Fixed OD premium charges:

There will be master as Fixed OD premium charges which need to be sent to PF along with the basic OD
rates as an out put from blaze
The master will be define on the basis of Products & the calculation logic for the same will also be product
specific
For GCV calculation logic will be as below

effectiveDat
e
Jun 16, 2011
<= ..<= Jun
16, 2020

Fixed OD premium_GCV_Newtransction
param para
paramterName
eterVa mterN
lue
ame

GVW

>120
00

RTO_
Clust
or

param
eterVa
lue

All

Amo
unt

27

Fixed OD premium =((XXX-12000)*YY/100)*(Eq Rate/IMT rate)

Where ,
XXX is GVW of the model
YY is the amount from the above table
The additional charges will be discount/loaded on the basis of the overall discount/loading compute between
IMT_tariff & Final Basic OD rates
Other than GCV products, the below calculation logic will be as follows

Fixed OD premium =XXX*(Eq Rate/IMT rate)

Where Where XXX is the value from the above table
The additional charges will be discount/loaded on the basis of the overall discount/loading compute between
IMT_tariff & Final Basic OD rates

Fixed OD charge.xls

Under the parameter value there should be option to define the value with the below conditions, default
condition should be AND if no condition mentioned

Page 11 of 22

Business Requirement Specification

<Blaze>
1.
2.
3.
4.
5.
6.
7.

Between
Equal to (=)
Not equal to (<>)
>
=>
<
<=

Note:Effective date will be considered on the basis of policy start date

FR8.0

Vehicle Insured Declared Value (IDV)

There should be instance for defining the depreciation percentage on the basis of different parameter.
Instance can be define on the basis of Product, transction type & other parameters .
There should not be any limits select the no. of parameters while define the instance
Depreciation percentage will be provided by the UW in the rules of the IDV on the basis of different parameters
System has to depreciate the Showroom price & sent the vehicle IDV in the response after deduction of the
depreciation as per the rule define
Sample instance given below
IDV master_Privatecar_Newtransction_Echannel
effectiveDate

paramter
Name

Jun 16, 2011 <= ..<= Jun 16, 2020

Age Band

Jun 16, 2011 <= ..<= Jun 16, 2020

Age Band

Jun 16, 2011 <= ..<= Jun 16, 2020

Age Band

Jun 16, 2011 <= ..<= Jun 16, 2020

Age Band

Jun 16, 2011 <= ..<= Jun 16, 2020

Age Band

Jun 16, 2011 <= ..<= Jun 16, 2020

Age Band

Jun 16, 2011 <= ..<= Jun 16, 2020

Age Band

Jun 16, 2011 <= ..<= Jun 16, 2020

Age Band

Jun 16, 2011 <= ..<= Jun 16, 2020

Age Band

parameter
Value

Depreci
ation
rate

0 <=
..<= .5
.6 <= ..<
=1.0
1.1<=
..<=2
2.1 <=
..<= 3
3.1 <=
..<= 4
4.1 <=
..<= .5
5.1<=
..<= 6
6.1<=
..<= 7
=>7.1

Age of the vehicle

2.3 yrs

5.4 yrs

Showroom price

100000

100000

0.3

0.55

70000

45000

Examples

Depreication rate as per

rule define above
IDV to sent in Response

0.05
0.15
0.20
0.30

0.40
0.50
0.55
0.60
0.65

Under the parameter value there should be option to define the value with the below conditions, default
condition should be AND if no condition mentioned

Page 12 of 22

Business Requirement Specification

<Blaze>
1.
2.
3.
4.
5.
6.
7.

Between
Equal to (=)
Not equal to (<>)
>
=>
<
<=

IDV master.xls

Page 13 of 22

Business Requirement Specification

<Blaze>
FR9.0

Equation of Basic Own damage

There will be 2 tables to defined the equation

a. Generic Table
b. Exception Table

Under Generic table:

There will be instance on the basis of different parameters for the same products eg, there may be instance of
GoodsCarryingVehicel_Rollovertransaction_PublicCarrier,etc
Basic own damage rate can be define by fetching the values from different master viz.Severity master,TLR
master, fixedfactor master,etc as define in the routemaster
Example of Basic Own damage rate :
Rate= if(Sourcesytem=genisys,{(EXP(FF+R1+R2+.)/(1+EXP(FF+R1+R2+.))*Severity/Target LR}/IDV
Where,
EXP stands for the function of Exponential
FF stands for the Fixedfactor value
R1,R2, stand for different parameters value
Severity stands for the value derived from severity master
Target LR stands for the value derived from LR master
IDV stands for vehicle insured value only

All the equation will be having a start date from which the same will be effective. If there is any modification in
the equation, it will be having an end date & the new modified equation will having a Start date as the date of
Modification.
Start date will be the Policy inception date
If there is any conflict for the duplication of same rules, system should provide an alert to the UW team.
In the backend the original Rates of the policy will always be stored; i.e. the transaction will always store the
rates at which that particular policy was issued.
Additonal Trailer OD rates for MISD & GCV product:
In MISD Product : If the No. of trailer > 0, OD rates for Additional trailer will be equal to basic OD rates
provided by the Generic table/Exceptional table/IL_Tariff as the case may be. Any loading or discount on
vehicle will also be applicable for trailer also
In GCV Product: For the OD rate of addional trailer in GCV Product, there will be separate table to update the
rates on the basis of different parameters.
No other loading or discount should be calculated on the OD rate of trailer.

Instance for Trailer

OD_GCV.xls

Exceptional Table
Under exceptional table , UW can define instance to the basis of different parameter on the basis of products
There should below conditions on the basis of which exceptional rules can be define using the different

Page 14 of 22

Business Requirement Specification

<Blaze>
FR10.
0

IL Tariff :
There will be master to upload the IL tariff in blaze.
If as per the route master, value to be fetch from IL tariff, the master should be refer
IL tariff will be define on the basis of instance as per below .
Instance example:ILTariff_Privatecar_Newtransaction_Echannel
Instance can be define with different parameters
The value in IL tariff will be the discount/loading % which need to refer the IMT tariff for final basic OD rate.

IMT
rate
0.033
14
0.033
14
0.033
14

IL tariff rate
loading/
(Discount)
(0.10)
.10
0.00

Final
basic
OD
rate
0.029
83
0.364
54
0.033
14

Remarks
IMT tariff rate reduced by
10%
IMT tariff rate increased by
10%
no loading or discount

ILTarifff_Sample.xls

FR11.
0

Reference to IMT Tariff & Validation master

The Final OD rates derived after all the exceptional calls , should be validate from the Validation master.
At any point of time the Final Rates should not be beyond the define limits of the Validation table.
In case of failed response due to validation of rate out of the min-max discount /loading rate in blaze , Pop up to
be given to PF as other loading/discount cannot exceed the tariff rate

Validationmaster.xls

There will be additional master as IMT_Tariffmaster.

Master for
IMT_Tariff.xls

.
All the discount/loading should refer the IMT tariff master for the addition/reduction of the equation rates.

Page 15 of 22

Business Requirement Specification

<Blaze>
FR12.
0

NCB master : (Applicable for Renewal transaction only)

There should be NCB master to evaluate the applicability of NCB to be given
Instance can be defined for the NCB applicability. Instance will be define on the basis of different parameters,
the result output will be as below

Yes
No
N/A

Where,
Yes implies NCB is applicable
No Implies NCB should is not applicable
N/A implies transaction should not be allowed, there should be option to provide the remarks by UW for N/A
status ,the tag should be NCBRemarks
If the Approved NCB flag received in request as True, by default in response, NCB applicability should be
sent as Yes, no NCB applicability rules to be check for such proposal
NCB applicability should be check on the basis of the previous policy
During endorsement, claim on the previous policy need to be check & value should be updated to status to be
updated to PF
Post deriving the NCB applicability, PF will calculate the NCB % as per the current logic.
In defining the instance for NCB , the below condition should be allowed to define the rules,
default condition should be AND if no condition mentioned .
1.
2.
3.
4.
5.
6.
7.
8.
9.

Max of
Min of
Between
Equal to (=)
Not equal to (<>)
>
=>
<
<=

NCB_Instance.xls

If there is no value found against the parameters of the proposal , the default value for NCB applicability to
be captured as YES
Count of Claim to be also sent hence there should be table to provide the No. of claim in previous policy .
UW should be able to define the different parameter for getting the summation of count of claim as per
below example where summation of Own damage+total theft+PA claim where no count of Paid& close
+Count of Pending > 0 to be sent as a response (Applicable for Renewal transaction only)
Count of claim to be provide for those case where NCB protect was taken in the previous policy

NCB_Applicable_Count of Claim_Private car_Renewal

Page 16 of 22

Business Requirement Specification

<Blaze>
effectiveD
ate
Jun 16,
2011
<= ..<=
Jun 16,
2020

paramterName

parameterValue

Count of Paid and Closed

+ Count of Pending
>0

Count of
claims
No.of Own
Damage
claim
+ No.of Total
Theft claim
+No. of
Personal
Accident
claim

Count of claim.xls

FR13.
0

Renewal calculation
There should be functionality to provide the Basic OD rate & TP premium for bulk proposal queries, which will
be utilized for the bulk calculation of Renewal cases
PF will sent the request in bulk on the basis of product, blaze to return the basic od rates considering the impact
as per the rules define under different masters in blaze

Response for All Package policy from blaze to PF

a. Basic OD Rate.
b. Basic OD rate of Trailer.
c. Fixed OD premium.
d. Basic TP Premium.
e. Basic TP premium for attached trailer in GCV & MISD products.
f. Discount/Loading rate on IMT tariff (Positive (+) value for loading & negative (-) for discount .
g. NCB Applicability.(if the Approved NCB flag received in request as True, by default in responser
NCB applicability should be sent as Yes, no NCB applicability rules to be check for such proposal ) Yes
If the response is given as N/A, Remarks should also be sent in Response under the tag NCBRemarks
h. Approval triggers flag for other Loading/discount (including dealer flexi)
i. No. of Claim in previous year policy ( to be sent if previous policy has NCB protection coverage).
j. Error message:
if the above value not calculate, in error message name of the master where value not define to be
sent to pathfinder.
Example: as per equation LR master to be refer but in the LR master the parameters are not found for the
proposal hence in error message below statement should be sent
Value in <xxxx> master not define,pls contact the underwriter
In case of failed response due to validation of rate out of the min-max discount /loading rate in
blaze , Pop up to be given to PF as
other loading/discount cannot exceed the tariff rate
k. Vehicle Insured Declared value (IDV) Only IDV of the vehicle to be sent in sent in the response
20000
l.Add-on cover response (including the existing Add-on covers)
i.
Rates for Engine Protect plus
ii.
Rates for Tyre protect
iii.
Rates for Key Protect
iv.
Rates for Loss of personal belonging
v.
Premium of Road side assistance

Page 17 of 22

Business Requirement Specification

<Blaze>
m. Exceptional scenario (as define in exceptional table . for OD)
n.Exceptional scenario (as define in exceptional table For TP)

Response for All liability only policy from blaze to PF

a. Basic TP Premium.
b. Basic TP premium for attached trailer in GCV & MISD products.
c.

Error message:
if the above value not calculate, in error message name of the master where value not define to be
sent to pathfinder.
Example: as per equation LR master to be refer but in the LR master the parameters are not found for the
proposal hence in error message below statement should be sent
Value in <xxxx> master not define,pls contact the underwriter
d. Exceptional scenario (as define in exceptional table . ) -As per the TP exceptional table

Dealer flexi discount/loading to be ignored at the time of bulk calculation of renewal

FR14.
0

If in the NCB applicable master N/A is define against the rules, rates for the same should also be
calculate but along with the rates, additional remarks should also be sent to PF which will be updated
by UW against the rules (optional).NCB Flag to be updated as No with NCBRemarks (For renewal
notice only)
Version manamgement
There should be option to export the reports of changes done in blaze.
Reports should be extract in excel format on the basis of date range along with the details of changes & the user
details who has made the changes with date & time

Version management
reports.xls

FR15.
0

Basic Third Party premium: Currently , Basic TP premium is calculated in PF which will be stopped & in
response from blaze Basic TP premium also to be provided to pathfinder.
There should be 2 table for Basic TP rates as below
Generic TP table
Exceptional TP table
Under Generic TP table: Instance for each product can be define on the basis of different parameters , there
should be 2 values to be define i.Fixed TP ii.Variable TP
Under Fixed TP: There will be fixed amount to be given
Under Variable TP: there will be reference to be the parameters value to calculate the premium . Variable TP
premium will be calculate on the value sent by the proposal against the parameters
Final Basic TP rates will be summation of Fixed TP & Variable TP.
Example
Fixed TP =1000
Variable TP : Upto 6 carrying capacity :Rate =200

Page 18 of 22

Business Requirement Specification

<Blaze>
In the proposal , carrying capacity = 3
Basic TP premium = Fixed TP +( carrying capacity *rate)
=1000+(3*200)
=1000+600
=1600
Sample Instance attached for PCV & Private car package policy

BasicTP.xls

Exceptional TP table:
There will be exceptional TP table which will be having the below dropdowm

Min or Max of Generic TP or Exceptional TP

Only Exceptional TP
Discount/Loading % on Fixed TP
Discount/Loading % on Variable TP
Discount/Loading % on Variable TP & Fixed TP
Discount/Loading Amount on Fixed TP
Discount/Loading on Amount on Variable TP
Discount/Loading on Amount Variable TP & Fixed TP

BasicTP_Exceptional.
xls

In defining the instance for basic TP , the below condition should be allowed to define the rules,
default condition should be AND if no condition mentioned .
1.
2.
3.
4.
5.
6.
7.

Between
Equal to (=)
Not equal to (<>)
>
=>
<
<=

There should be instance to define the Basic TP premium of trailer attached to GCV & MISD products which
should be multiplied with the No. of Trailer selected in PF
In response , TP premium of

BasicTPfor Trailer.xls

Page 19 of 22

Business Requirement Specification

<Blaze>
FR16.
0

Applicability for Add-on cover

In Add-on eligible master, there should be option to make the selection of Add-on covers on the condition of
selecting other add-on cover mandatorily
Scenario: RTI or Consumables can be selected only if Zero depreciation selected
Example 1 : User can select Return to invoice cover if Zero depreciation also selected in the proposal
Example 2. User can select consumable cover if Zero depreciation also selected in the proposal
Example 3. User can select stand alone cover of Zero depreciation only.
Hence as per the above example s, there should be option to select the cover on standalone basis or in package
with other add-on covers
DT_Add-onApplicability
effective
Date
Jun 16,
2011
<= ..<=
Jun 16,
2020
Jun 16,
2011
<= ..<=
Jun 16,
2020
Jun 16,
2011
<= ..<=
Jun 16,
2020

Covername

Covernam
e

Zero
depreciation

Consumab
les

Zero
depreciation

N/A

Zero
depreciation

ReturntoIn
voice

Applicablecov
er

ReturntoIn
voice
Consumble
s

Applicable
cover
NCBprotec
t

N/A

N/A

RSA

Applicability
master.xls

FR17.
0

Endorsement /Cancellation
During Non nil endorsement , proposal to be hit to blaze for the response as per the cut-off date logic applicable
for pathfinder.
During Nil Endorsement , proposal will not hit blaze
During Cancellation of the policy, proposal will not hit blaze

Fr18.
0

Simulator :
There should be simulator available in blaze to test the developed functionality. On the basis of parameters &
the functionality mentioned in the above FRs user should be able to get the corresponding response as per the
new response mentioned in the document + the existing response related to decline pool & add-on covers

4.2
Req. ID
NFR1.0

Non-functional requirements
Requirement Description
<Requirement Description >

Page 20 of 22

Notes/ Issues
<If Any>

Business Requirement Specification

<Blaze>
NFR2.0

4.3
Req. ID
UFR1.0
UFR2.0

4.4
Req. ID
RFR1.0
RFR2.0

4.5
Req. ID
LFR1.0
LFR2.0

<Requirement Description >

UI requirements
Requirement Description
<Requirement Description >
<Requirement Description >

Requirement Description
<Requirement Description >
<Requirement Description >

Notes/ Issues
<If Any>
<If Any>

Legal and compliance requirements

Requirement Description
<Requirement Description >
<Requirement Description >

Other requirements

Req. ID

Requirement Description
<Requirement Description >
<Requirement Description >

OFR2.0

Notes/ Issues
<If Any>
<If Any>

Reporting requirements

4.6
OFR1.0

<If Any>

Page 21 of 22

Notes/ Issues
<If Any>
<If Any>

Notes/ Issues
<If Any>
<If Any>

Business Requirement Specification

<Blaze>

5. Additional Information
5.1

Impact of CR on other interfaces or systems

<Provide the impact analysis on other interfaces/ systems>

5.2

Type of Change

Nature of Request
Function
Module
Report
Program

New/ Modify
Yes/ No
Yes/ No
Yes/ No
Yes/ No

6. Appendix

Page 22 of 22