Case Study On Policy Bazaar: Bachelor of Technology in
Case Study On Policy Bazaar: Bachelor of Technology in
Case Study On Policy Bazaar: Bachelor of Technology in
On
POLICY BAZAAR
BACHELOR OF TECHNOLOGY
in
By
Roll No: 30
Section: K17PJ
I hereby declare that the case study entitled "POLICY BAZAAR” submitted at Lovely Professional
University, Phagwara, Punjab is an authentic work and has not been submitted elsewhere.
I understand that the work presented herewith is in direct compliance with Lovely Professional
University’s Policy on plagiarism, intellectual property rights, and highest standards of moral and ethical
conduct. Therefore, to the best of my knowledge, the content of this case study represents authentic and
honest effort conducted, in its entirety, by me. I am fully responsible for the contents of my case study
report.
Signature of Candidate
GAYATHRI KILARU
R. No: 30
ACKNOWLEDGEMENT
1. Introduction.....................................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Document Conventions..................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Definitions, acronyms, abbreviations...........................................................................................1,2
1.5 Scope………………………………………………………………………………………………………………………………………….2
2. Overall Description...........................................................................................................................2
2.1 Product Perspective.....................................................................................................................2,3
2.2 Product Features.............................................................................................................................3
2.3 User Classes and Characteristics.....................................................................................................4
2.4 Operating Environment..................................................................................................................4
2.5 Design and Implementation Constraints.....................................................................................4,5
2.6 User Documentation.......................................................................................................................5
2.7 Assumptions and Dependencies.....................................................................................................5
3. System Features...............................................................................................................................6
3.1 System Feature 1.........................................................................................................................6,7
3.2 System Feature 2 (and so on).......................................................................................................7,8
Appendix A: Glossary...........................................................................................................................11
Revision History
Name Date Reason for Changes Version
Software Requirements Specification for <Project> Page 1
Introduction
Purpose
This document describes the software requirements and
specification about Policy Bazaar
Document Conventions
Font: Times New Roman 12
Definitions
• Insurance
An agreement in which a person makes regular payments to a company and the company
promises to pay money if the person is injured or dies, or to pay money equal to the value of
something (such as a house or car) if it is damaged, lost, or stolen
•Sell
Give or hand over (something)in exchange for money have a stock of (something) available for sale.
It is a type of transaction.
• Buy
Pay someone to give up an ownership, interest, or share. It is also a type of transaction.
• Policy
A course or principle of action adopted or proposed by a government, party, business, or by the companies
which provide various facilities.
• Clients
These are the persons who are using the services provided by the company or the organizations.
Software Requirements Specification for <Project> Page 2
Clients may of many types like as the sponsors and the customers are also termed as the clients.
•Transaction
A transaction is an agreement between a buyer and a seller to exchange goods, services or
financial instruments. Accrual accounting records transactions when revenues or expenses are
realized or incurred, while cash accounting records transactions when the business actually
spends or receives money.
Abbreviations
Throughout this document the following abbreviations are used:
Overall Description
Product Perspective
The PolicyBazaar.com is a portal where the clients are independent of the policies they
select whether it may be any policy such as the car insurance or any of the insurances
the online portal has a unique login Id of the client which stores the information of the
concerned client and all the transactions made by him/her.
Software Requirements Specification for <Project> Page 3
Communication interface
The information or all the data on this portal is shared by the internet around the globe
And they have their own backup of the data at some places.
.
Hardware interface
The software will run on the electronic devices such as tablets, smart phones, Desktops etc.
User interfaces
Customer
The customer user interface should be intuitive, such that
99.9% of all new Policy Bazaar users are able to complete the
transactions without any assistance.
Developers
Developers are responsible for failing transactions
Such as the buying and selling of the policy or the insurance. There should be a simple interface
that they can use to make the policy bazaar account whenever needed.
Maintainer
The maintainer is responsible for problem new login Id’s to the
network and servicing existing accounts. A maintainer should be
possible to resolve any issue of user login Id to the network within 1 hour.
Product Features
The portal of PolicyBazaar.com should work 24 hrs. The Policy Bazaar portal identifies
Its client by the unique login Id where all the information of the client’s transactions are saved. It
collects information about a simple transaction
(e.g., new insurance policy, revoke the policy, terminations of the policy, bill payment),
Software Requirements Specification for <Project> Page 4
information to the database of the policy bazaar.com, and ensures the fruit of policy
to the customer. The software requires appropriate record keeping
and security provisions. The software must handle concurrent
accesses to the same login Id correctly.
special training.
experience.
Operating Environment
The hardware, software and technology used should have following specifications:
Valid Login ID
Software Requirements Specification for <Project> Page 6
•If the login ID and the password is wrong then the message prompt “Password or Login is Wrong”.
• If policy is against then you have to claim the rule according to law.
Validate Password
User Documentation
https://www.policybazaar.com/contact-us/
Specific Requirements
Functional Requirements
The functional requirements are organized in two sections First requirements of the Internet
and second requirements of the Electronic device to use Policybazaar.com
General
Functional requirement 1
Functional requirement 2
Functional requirement 3
• You will be redirected to the specific bank site for the safe payment
For the selected policy.
• A valid Card number of the bank and password is required for
The payment.
Authorization
The authorization starts after a customer has entered his Login ID and Password in the Policybazaar.com
site.
Functional requirement 4
Interface requirements
Functional requirement 5
Business Requirements
Clicking the Approve button moves the request to the Approval Workflow.
All personnel using the system will be trained according to internal SOP .
Functional requirement 6
Software Requirements Specification for <Project> Page 9
Compliance Requirements
Functional requirement 7
Security Requirements
Members of the Data Entry group can enter requests but cannot approve or delete requests.
Members of the Managers group can enter or approve a request but cannot delete requests.
Members of the Administrators group cannot enter or approve requests but can delete requests.
Functional requirement 8
If you close the tab then even when you open the policybazaar.com in your system the
Account will be logged in for the convenience of the clients.
Functional requirement 9
There should be a valid ID proof of the client that claims that he/she is the specified
Person of the given specific location.
As if Policybazaar.com wants to send a mail to the client then this mail will be addressed
As per the given information.
Functional requirement 10
It is totally handy as the policy bazaar apps are also launched in various operating systems compatible
devices such as Android, Microsoft, Blackberry, iOS etc.
Software Requirements Specification for <Project> Page 10
You can use our site to compare save and buy from anywhere in consideration of your login ID.
Functional requirement 11
The captcha helps in verifying if the users that actually the human is using the site or the
Robots are used to access the site to gather the information etc.
Hardware Interfaces
Software Interfaces
The software interfaces are specific to the target PolicyBazaar.com systems.
Safety Requirements
• Must be safe in security aspects.
• The Basic information should be kept safe in the databases of the policybazaar.com
• The login account must be always logged out as he/she close the website.
Security Requirements
• The maximum number of attempts to enter Passwords will be two and thereafter the password reset link
Facilities
Robust
5.4.1 Availability
The Internet has to be available whenever you want to access the Policybazaar.com.
5.4.2 Security
The ATM network should provide maximal security. In order to make that much more
5.4.3 Maintainability
Only maintainers are allowed to connect new ATMs to the network.
6.Other Requirements
Data Base
The POLICY BAZAAR must be able to use several data formats according to the data formats that are
Software Requirements Specification for <Project> Page 13
provided by the data bases. A transaction should have all the properties of a data base transaction
(Atomicity, Consistency, Isolation, Durability).
Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple projects or the
entire organization, and just include terms specific to a single project in each SRS.>