Professional Documents
Culture Documents
Lic
Lic
SOFTWARE REQUIREMENTS
SPECIFICATION
FOR
Submitted
Roll No:-
RK23LAA0
Registration No:12307167
SectioK23LA
Table of Contents
1. Introduction
1.1 Purpose
1.2 Intended Audience And Reading Suggestions
1.3 Project Scope
1.4 Overview
1.5 Definitions
1.6 References
2. General Description
2.1 Product Perspective
2.2 Product Functions
2.3 User Characteristics
2.4 Abbreviations
3. Specific Requirements
3.1 Functional Requirements
3.2 Non Functional Requirements
3.3
External Interface Requirements
3.3.1Hardware Requirements
3.3.2Software Requirements
3.4 Performance Requirements
3.5 Other Requirements
3.5.1 Database
3.5.2 User interface
3.5.3 Communication interface
3.5.4 Performance requirement
4. System design
4.1 Use Case Diagram
1.1 Purpose
This project is the University level project and is implementing under the
guidance of University professors.
1.4 Overview
1.5 Definitions
1.6 Reference
Life Insurance Corporation (www.lic.com)
www.learnerswindow.com
2. Overall Description
2.1 Product Perspective
The Life Insurance management system(LIC) is a web based application
and maintains a centralized repository of all related information.
Customer
The customer interacts with Life Insurance managmnet System via
the Internet. It must be very easy for them to access and use the
that Management System. They should be able to do operations like
registering, viewing of policy, premium calculation, rating of policy.
Maintainer
It should be easy to maintain the whole system. The maintainer
should be the only person that is allowed to or give privileges to add
new information.
2.4 Abbreviations
Throughout this document the following abbreviations are used
LIS: Life Insurance System
SRS: Software Requirement Specification
GUI: Graphical User Interface
LIC: Life Insurance Corporation
PC: Premium calculation
V:view the policy
BPO: Buy Policy Online
PP: Premium Payment
3. Specific Requirements
General
Functional requirement
Description
Initialize parameters V,PC,BPO,H
Input
V,PC,BPO in entered.
Processing
Processing the result based on the parameters entered.
Output
Displaying the result based on the parameters.
Functional requirement 2
Description
If No result is available for the entered parameters the system
displays an error message.
Input
PP,PC in entered.
Output
Display an error message.
Authentication
The Authentication starts when the Customer enters his logic id and
password.
Description
The System has to check if the entered information is a valid
Input
Customer enters the login id and password.
Processing
Check if it is a valid.
Output
Display error message .
-userid/bad password if the login id is wrong.
3. Specific Requirements
General
Functional requirement
Description
Initialize parameters TYR,S,D,H
Input
TYR,S,D,H in entered.
Processing
Processing the result based on the parameters entered.
Output
Displaying the result based on the parameters.
Functional requirement 2
Description
If No result is available for the entered parameters the system
displays an error message.
Input
TYR,S,D in entered.
Output
Display an error message.
Authentication
The Authentication starts when the Customer enters his logic id and
password.
Description
The System has to check if the entered information is a valid
Input
Customer enters the login id and password.
Processing
Check if it is a valid.
Output
Display error message .
-userid/bad password if the login id is wrong.
3. Specific Requirements
General
Functional requirement
Description
Initialize parameters PC,V,BPO
Input
TYR, PC,V,BPO in entered.
Processing
Processing the result based on the parameters entered.
Output
Displaying the result based on the parameters.
Functional requirement 2
Description
If No result is available for the entered parameters the system
displays an error message.
Input
V,PC in entered.
Output
Display an error message.
Authentication
The Authentication starts when the Customer enters his logic id and
password.
Description
The System has to check if the entered information is a valid
Input
Customer enters the login id and password.
Processing
Check if it is a valid.
Output
Display error message .
-user id/bad password if the login id is wrong.
Functional requirement 3
Description
Perform Payment operation.
Input
Initial Payment sequence successful.
Processing
Online Payment .
Output
Wait for Payment Completion.
Functional requirement 4
Description
Perform Payment Cancellation operation.
Input
Cancellation successful.
Processing
Payment Return.
Output
Wait for Payment Return Confirmation.
Security: The business logic is hidden from the users and is much
safer and thus avoids unauthorized or illegal access or database
corruption. Security of the user’s information is also safe as there is a
login facility.
Server Side:
Client Side:
Server Side:
Operating System Window Server 2008 or any
compatible operating system.
Runtime Environment .Net Framework 4.0
Web Server IIS 7.0
Front End Microsoft Asp.Net 2010 with
c#
SQL server 2008
Back End
Server Side:
Performance requirement 1
Description
Error message should be displayed at least 20 sec .
Performance Requirement 2
Description
Online Payment should be secured and if any kind interfere in
communication is occurred it must not lead to payment failure.
Performance Requirement 3
Description
Only after Payment confirmation premium should be confirmed.
The Life insurance management system must be able to use several data
formats according to the data formats that are provided by the data bases
of different policy, loans transaction should have all the properties of a
database transaction (Atomicity,Consistency,Isolation,Durability)