Software Requirements Specification for Insurance Management System Page 1

UNIVERSITY OF ENGINEERING & MANAGEMENT, KOLKATA

University Area, Plot No. III - B/5, New Town, Action Area - III, Kolkata, West Bengal 700156

Software Engineering Laboratory

Topic: Insurance Management System

Submitted By:

Amitrajit Bose – 13 12016009001529

Sourav Kumar – 14 12016009001726
Kirti Ojha – 15 12016009001065

Under Supervision of Prof. Anay Ghosh and Prof. Sreyashi Bhattacharya

Software Requirements Specification for Insurance Management System Page 2

ACKNOWLEDGEMENTS

This project would not have been possible without considerable

guidance and support. So, we would like to acknowledge those
who have enabled us to complete this project. Firstly we would
like to thank our project supervisors, Prof. Anay Ghosh and Prof.
Sreyashi Bhattacharya, for providing the guideline with continues
advice and feedback throughout the duration of finishing this
project. We are also thankful to our H.O.D, Prof. Sukalyan
Goswami, for constantly inspiring and motivating us.

………………

Date: 08.04.2019
Amitrajit Bose (13)
Sourav Kumar (14)
Kirti Ojha (15)
Software Requirements Specification for Insurance Management System Page 3

CERTIFICATE

This is to certify that the project entitled “Insurance

Management System” has been successfully developed by
“Amitrajit Bose, Sourav Kumar & Kirti Ojha”. They have used
Dev C++ to develop the project. Their work is satisfactory.
I wish them all the best for their bright future.

DATE: 08.04.2019
…………………..
(Project In-charge)
Prof. Anay Ghosh
Prof. Sreyashi Bhattacharya
Software Requirements Specification for Insurance Management System Page 4

Table of Contents
Table of Contents ...................................................................................................................... 4
1. Introduction ........................................................................................................................ 5
1.1 Purpose ...................................................................................................................................... 5
1.2 Document Conventions ............................................................................................................... 5
1.3 Intended Audience and Reading Suggestions .............................................................................. 5
1.4 Product Scope............................................................................................................................. 5
1.5 References .................................................................................................................................. 5
2. Overall Description ............................................................................................................. 6
2.1 Product Perspective .................................................................................................................... 6
2.2 Product Functions ....................................................................................................................... 6
2.3 User Classes and Characteristics ................................................................................................. 7
2.4 Operating Environment ............................................................................................................... 7
2.5 Design and Implementation Constraints ...................................................................................... 7
2.6 User Documentation ................................................................................................................... 7
2.7 Assumptions and Dependencies .................................................................................................. 7
3. External Interface Requirements ....................................................................................... 7
3.1 User Interfaces............................................................................................................................ 7
3.2 Hardware Interfaces .................................................................................................................... 7
3.3 Software Interfaces ..................................................................................................................... 8
3.4 Communications Interfaces ......................................................................................................... 8
4. System Features .................................................................................................................. 8
5. Other Nonfunctional Requirements ................................................................................... 8
5.1 Performance Requirements ......................................................................................................... 8
5.2 Safety Requirements ................................................................................................................... 8
5.3 Security Requirements ................................................................................................................ 9
5.4 Software Quality Attributes ........................................................................................................ 9
5.5 Business Rules............................................................................................................................ 9
6. Design Documents ............................................................................................................... 9
7. Output………………………………………………………………………………….……..15
Software Requirements Specification for Insurance Management System Page 5

1. Introduction
1.1 Purpose

Online Insurance management system is a web application which is developed for tracking the
details of the insurance policy, customer details and company details. This web site is an online
insurance Analysis and information management system that provides easy access of
information regarding the people and resources of insurance. User can view their own personal
details when logged in into the Policy Holder module. This project is useful for any kind of
insurance company to manage the insurance details, to sanctioned the insurance for customer,
process the insurance policy details and all kind of insurance process through online. The
Insurance management system is a complete solution for organizations, which need to manage
insurance for their vehicles, equipment, buildings, and other resources.

1.2 Document Conventions

The FONT used in this document is: Times New Roman. Important points are written in bold.

1.3 Intended Audience and Reading Suggestions

This document is to be read and analyzed by our college, UEM CSE Dept. Professors for academic
purposes. This document mainly consists of the output of our console-based software and the
following diagrams:
1. ERD
2. DFD
3. DECISION TREE & DECISION TABLE
4. STRUCTURE CHART
5. SEQUENCE DIAGRAM
6. CLASS DIAGRAM & OBJECT DIAGRAM

1.4 Product Scope

This insurance management console has facilities like search tools for insurance awareness articles,
guidelines, illustrations through images for visitors. This insurance management system can
efficiently manage the company, records, provides instant access and one that improves the
productivity. In this console process the user enters into the website it will show details about
insurance and its types, also it will show the details about different duration schemes to the
corresponding insurance type or insurance policy. The main objective of the developed system is to
allow admin users to register insured persons with their name, date of birth, residence address,
medical history and also policy details.

1.5 References
This documentation strictly follows the IEEE Software Requirements Specification Template.
Software Requirements Specification for Insurance Management System Page 6

2 Overall Description
2.1 Product Perspective

This Insurance Management System is a self-contained system used to perform multiple functions
related to the financial protection and reimbursement of damages from the insurer or the insurance
company. The basic principle of insurance is that an entity will choose to spend small periodic amounts
of money against a possibility of a huge unexpected loss. Basically, all the policyholder pools their risks
together. Any loss that they suffer will be paid out of their premiums which they pay.

2.2 Product Functions

1] Provides Reliability

The main function of insurance is that eliminates the uncertainty of an unexpected and sudden
financial loss. This is one of the biggest worries of a business. Instead of this uncertainty, it provides
the certainty of regular payment i.e. the premium to be paid.

2] Protection

Insurance does not reduce the risk of loss or damage that a company may suffer. But it provides a
protection against such loss that a company may suffer. So at least the organisation does not suffer
financial losses that debilitate their daily functioning.

3] Pooling of Risk

In insurance, all the policyholders pool their risks together. They all pay their premiums and if one of
them suffers financial losses, then the pay-out comes from this fund. So the risk is shared between all
of them.

4] Legal Requirements

In a lot of cases getting some form of insurance is actually required by the law of the land. Like for
example when goods are in freight, or when you open a public space getting fire insurance may be a
mandatory requirement. So, an insurance company will help us fulfil these requirements.

5] Capital Formation

The pooled premiums of the policyholders help create a capital for the insurance company. This capital
can then be invested in productive purposes that generate income for the company.
Software Requirements Specification for Insurance Management System Page 7

2.3 User Classes and Characteristics

The software has been developed keeping in mind the personalized usage of multiple end users who
will be using the application to keep track of their insurance policies and compute premiums.
The current version of the software does not include a master password or admin account, to
maintain the privacy of every user of the application, everyone has to sign-up before using it.

2.4 Operating Environment

The software can operate on any Linux system which has g++ compiler installed.

2.5 Design and Implementation Constraints

1. Completely console based

2. Implemented the database using file management system and object serialization schemes.

2.6 User Documentation

A project report along with a small presentation will be given about our software project.

2.7 Assumptions and Dependencies

Customer need have minimum computer knowledge to operate system and register. Agent needs
the knowledge of computer as well as insurance policy domain insurance company employees need
knowledge of Insurance domain as well as computer.

3 External Interface Requirements

3.1 User Interfaces

 Front-end software: Console Based Application - C++

 Back-end software: File Management System & Object Serialization

3.2 Hardware Interfaces

 Linux
Software Requirements Specification for Insurance Management System Page 8

3.3 Software Interfaces

Software used Description

Operating Compatible with Linux and UNIX-based Operating Systems.

system Compatibility on Windows OS has not yet been tested.

To save the user insurance records, user login records we have chosen file

Database management system and object serialization schemes.

4. System Features
The software has features and capabilities that were not available on previous midrange systems.
Primary features include the ability to enabling new schemes and offers and create domains. These
features provide greater reliability, availability, and serviceability, which means uptime. These
features and capabilities are as follows:

 Domain--The ability to create logically independent multiple schemes for multiple users,
with each domain saved within separate files.
 Reliability--A function of the care with which the hardware and software design was
executed, the quality of the components selected, and the quality of the maintenance
process.
 Availability--The percentage of time the customer's system is able to do productive work.
 Serviceability--The system ensures that repair time (downtime) is kept to a minimum.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

All insurance scheduling, viewing, and options commands must execute instantaneously, except for
when exit is chosen in the application. The time to execute exit operation must be in the order of
seconds.

5.2Safety Requirements

Passwords should be masked and not visible when a user enters it on the command line tool.
Authentication data must be stored in an encrypted and safe format with proper backup.
Software Requirements Specification for Insurance Management System Page 9

5.3Security Requirements
The folder containing all the files of authentication details should be locked and only admin
accessible.

5.4Software Quality Attributes

AVAILABILITY: The insurance policy should be available on the specified date and specified
time as many customers are doing advance reservations.
CORRECTNESS: The insurance date and premiums should be calculated and correctly.
MAINTAINABILITY: The administrators should maintain correct details and records of all the
customers.
USABILITY: The insurance schemes should satisfy a maximum number of customer’s needs.

5.5Business Rules
A term plan provides death risk cover for a specified period. In case the life assured passes away
during the policy period, the life insurance company pays the death benefit to the nominee. It is a
pure risk cover plan that offers high coverage at low premiums. There’s an option to add riders to
widen up the coverage. The death benefit is payable as lump sum, monthly payouts, or a
combination of both. There’s no payout if the life assured outlives the policy term. However, these
days there are companies offering Term Plans with Return of Premiums (TROPS), where insurance
companies payback all the paid premium amount in case the life assured outlives the term period.
But, such plans are costlier than the vanilla term insurance plan.

6 Design Documents
 ER Diagram
Software Requirements Specification for Insurance Management System Page 10

 Data Flow Diagram

DFD LEVEL 0

DFD LEVEL 1

DFD LEVEL 2
Software Requirements Specification for Insurance Management System Page 11

 Decision Table

 conditions
Valid selection NO YES YES YES YES YES YES
New user -- YES NO NO NO NO NO
Existing user -- NO YES YES YES YES YES
New policy -- -- NO YES YES YES YES
Policy_count > 0 -- -- -- YES NO NO NO
Life -- -- -- -- YES NO NO
Home -- -- -- -- NO YES NO
health -- -- -- -- NO NO YES

actions
Display error X
message
Ask for user’s X
name, email
&password.
Store membership X
record
Display X
Registration
Successful
Display policy X X X X
details

Display “one policy X

per user” error
message
Create new policy X X X
Software Requirements Specification for Insurance Management System Page 12

 Structure Chart
Software Requirements Specification for Insurance Management System Page 13

 Sequence Diagram
Software Requirements Specification for Insurance Management System Page 14

 Class Diagram

 Object Diagram
Software Requirements Specification for Insurance Management System Page 15

7. Output
Software Requirements Specification for Insurance Management System Page 16
Software Requirements Specification for Insurance Management System Page 17