Vous êtes sur la page 1sur 5


Table of content
1.1 Problem definition
1.2 Purpose
1.3 Project scope
1.4 Reference
1.5 Jverview
Overall description
2.1 Product perspective
2.2 Product features
2.3 User classes and characteristics and modules
2.5 User documentation
2.6 Constraints
2.7 Assumptions and dependencies
2.8 Apportioning of requirements
External and interface requirements
3.1 $stem interfaces
3.2 Hardware interfaces
3.3 Communication interface
3.4 $ite Adaptation Requirements
4. Requirement analysis
4.1 $pecific requirement
4.2 Jther non-functional requirements
4.3 Jthers requirements

The project is all about gathering the information of the Customers and clients
who wants to be or alread a polic holder. $oftware has to be developed for
automating the manual client information management sstem. The process begins
with a client agreement that she/he is read to take the polic and then the
operator will add the details of the polic holder to the sstem so that we can
check the details of the client later on. While the client pas an premium there
is a update in the database of the particular client which will tell us the
current status of the client.
1.1 Problem Definition:
Toda all the work at the time of taking an polic is done manuall b ink and
paper, which is ver slow and consuming much efforts and time.
It is required to Design of a Computerized Automated issuance polic and plain
Management $stem, to speed up and make it eas to use b the agents.
1.2 Purpose:
The purpose of this $R$ document is to specif software requirements of the
issuance polic and plain Management $stem for the agents are:-
To make the required information available at once to the user.
To generate reports in the required format meeting the various
To fulfil the user requirements and make the sstem more user
Report generation with minimum data entr.
'arious automatic validation checks to avoid errors.
1.3 Project Scope:
It Manages policies and plains details.
Activities like Updating, Creations done in the sstem b the $stem Jperator
will be maintained in the form of tables for auditing and maintaining the
integrit of the sstem.

1.4 Document conventions:
The convention used in this document is as follows:
The font used in times new roman , heading are in font size 14 and
bold, subheading are in font size 12 and bold, and text is in font size 12.
The abbreviations used are as follows:-
a) S.R.S.:- $oftware requirement specification
b) UI: Graphical User Interface

1.5 References:
The document in this file is adopted from the IEEE Guide to $oftware
Requirements $pecifications (Std 830-1993).
.. Aggarwal and Yogesh Singh
Pressman of software engineering
1.6 Overview:
$R$ will include two sections.
Overall Description will describe major components of the sstem, interconnection
and external interfaces.
Specific Requirements will describe the functions of actors, their role in the
sstem and constraints.

The rest of this document will give further details on the overall product
description, including the hardware, software, and communications interfaces,
product functions, user characteristics, and an assumptions that will be made.
2.1 Product Perspective:
FRONT END:Microsoft 'isual $tudio 2008:-
This front end provides the graphical interface to the user and contain the
build-in components read to use. This language provides ver interactive look
and feel design.
We have choosen this particular tool as a backend as it is capable to store
multiple data and it is ver eas to access and it also provides the graphical
user interface for maintaing the tables.

2.2 Product Features:
$ome of the features are identified for the software. The are listed below:
View policy holder Information's: The agent must able login and see all
details about an client and about the polic and plains of the issuance
companies without an constraints.
Enquiry support: Enable the operator to ask and clear doubts about the
polices and plains.
Report eneration: The sstem supports generation of reports based on
different criteria.
User satisfaction: The sstem is much that is stands up to the user
expectations like eas and faster retrieval of information.
Safety and Robustness: The sstem will be accessible b onl the authorized
users. As information being the most crucial for the organization, there are
safet measures for the securit of information.
ighly accurate: Information being prepared electronicall can be said as
accurate which the first is and the foremost condition for taking a crucial
decision b the management.
Less time consuming: Work carried out b the agent at various stages will be
less time consuming.
Ease in maintaining information: As new information are being added to and
released from their respective ever ear, it will be highl user friendl
to track and maintain the presentation of all the doctors as well as
2.3User Characteristics:
Educational level: at least graduate should be comfort with English
Technical expertise: should be comfortable using general purpose
applications on a computer.
Awareness of the issuance polices and plains and there rules.
2.4 Constraints:
i) $ince the DBM$ being used in M$ Access 2007, which is not ver powerful DBM$
it will not be able to store a ver huge number of records.
Front end
(Microsoft 'isual
$tudio 2008)
Backend database
(M$ ACCE$$ 2007)
ii) Due to limited features of DBM$ being used performance turning features will
not be applied to the queries and thus sstem ma become slow with the increase
in the number of records being stored.
2.5User Documentation:
Polic form is available for the clients to assess them for the eas use.
A specific document should be prepared for the maintenance of the sstem and
should sa the sstem in easiest wa.
2.6Assumptions and Dependencies:
Facilities are alread created and information's available for use.
Roles and responsibilities are alread established.
Administrator is alread created.

2.7 Apportioning of requirements:
Not required.
3.1 System Interfaces
1. Microsoft 'isual $tudio 2008
2. Windows 7
3. M$ access

3.2 ardware Interfaces
1. 40 GB Hard Disk
2. 256 MB Ram
3. Monitor
4. Keboard
5. Processor PI'
3.3 Communication Interface
In our sstem the communication interface is the database through which we
get the details of the particular client and their polices.
3.4 Site Adaptation Requirements
No site adaptation is necessar in this project. Because the insurance
policies and plains management sstem is portable. The entire sstem is
transported to wherever it is needed. No external dependencies are in place
and operation of the sstem will never change due to location.
4.1 Specific Requirement
The document will also include the specific requirements needed. These will
include the functions, performance, design, and software attributes. This
document is organized in a logical manner and is eas to follow. Readers
should refer to the table of contents, appendices, or index if looking for
something in specific. Jtherwise, reading this document from start to finish
will start with a vague description and get more specific and detailed as
changing sections and reading further.
4.2 Other Non-functional Requirements
Performance Requirements
$ome Performance requirements identified is listed below:
The database shall be able to accommodate a minimum of 1,000 records of
The software shall support use of multiple users at a time.
Security Requirements
$ome of the factors that are identified to protect the software from
accidental or malicious access, use, modification, destruction, or
disclosure are described below. $pecific requirements in this area could
include the need to:
Keep specific log or histor data sets
Assign certain functions to different modules.
Restrict communications between some areas of the program
Check data integrit for critical variables
ater version of the software will incorporate encrption techniques in
the user/license authentication process.
Portability Requirements
$ome of the attributes of software that relate to the ease of porting the
software to other host machines and/or operating sstems. This ma include:
Microsoft 'isual $tudio 2008 is used to develop the product. $o it is
easiest to port the software in an environment
The user will be able to reset all options and all stored user variables
to default settings.

$ome of the attributes identified for the reliabilit is listed below:
All data storage for user variables will be committed to the database at
the time of entr.
Data corruption is prevented b appling the possible backup procedures
and techniques.

Usability requirements
$ome of the usabilit requirements identified for this sstem are listed
A logical interface is essential to an eas to use sstem, speeding up
common tasks.
Error prevention is integral to the sstem and is provided in a number of
formats from sanit checks to limiting free-text input.

All the data will be rebuilt during ever start-up. There is no recover
of user data if it is lost. Default values of sstem data will be
assigned when necessar.

Software System Attributes
There are a number of attributes of software that can serve as
requirements. It is important that required attributes b specified so
that their achievement can be objectivel verified. The following items
provide a partial list of examples.
The input sstem will allow for inputting numbers, operands, special
smbols and letters of the alphabet.

Immediate Feedback: The $stem must tr to answer all the queries of the
clients and it should provide immediate feedback after getting an request.
The sstem must provide the illusion to the agent that, the are contact the
real peoples for process the polic.

Reduce the Cost of policy Process: The main aim of the $stem is to reduce
the cost needed for Polic Process, so it automaticall reduces the manual
power needed to perform the entire task and improve the qualit of the work.
Increase the Quality of the Process: The $stem facilitates the work of the
agents and the same time it must reduce the work load of the companies with
expected qualit.