CONTENTS
Page No.
1: INTRODUCTION TO PROJECT
1.1 PROJECT OVERVIEW 2
1.2 SCOPE OF THE PROJECT 3
1.3 EXISTING SYSTEM 4 1.4 PROPOSED SYSTEM 5 2: DEVELOPMENT ENVIRONMENT 2.1 SOFTWARE REQURIEMENTS 6 2.2 HARDWARE REQURIEMENTS 7 2.3 ABOUT SOFTWARE 8
3: SYSTEM ANALYSIS AND STUDY
3.1 PROBLEM DEFINATION 14
3.2 FEASIBILITY STUDY 15
3.3 SYSTEM REQUIREMENT SPECIFICATION 18 4: SYSTEM DESIGN
4.1 ABOUT SYSTEM DESIGN 20
4.2 DATA FLOW DIAGRAM 22
4.3 ENTITY-RELATIONSHIP 25
4.4 DATA BASE DESIGN 29
5: SYSTEM IMPLEMENTATION 5.1 SOFTWARE TESTING 33 5.2 CODING 36 5.3 SAMPLE SCREENS 54 6: CONCLUSION 65
6.1SCOPE OF ENHANCEMENT 66 7: BIBLOGRAPHY 67
PROJECT OVERVIEW
The insurance company needs to keep track of details of its target companies, agents, policyholders, their premium
payments and the various products that are available with it. Hence it is under tremendous pressure maintaining their day-to-day activities, which is currently being done manually. Entire records have to be updated timely, even a slight
mistake could complicate things. It is very difficult to handle bulk data since human memory is weaker than electronic counter part. It is time consuming to summarize these details to produce the reports. The Insurance management system is a complete solution for organizations, which need to manage insurance for resources avaliable. Organizes and tracks
insurance vendors and the policies provided under different coverage.
Hence there is need for an automated system, which can efficiently manage the company, records, provides instant access and one that improves the productivity. As a result of this automated system, the activities of the company are
performed with in the stipulated time and the reliable and efficient service is ensured to its users.
SCOPE OF THE PROJECT
The transactions related to Life Insurance policies,
premiums, policy maturity, Agents management, Premium calculation , Agent locate, Branch locator,Premium
Calculation etc.,. transactions are done in an easy and effective manner as most part of it is computerized and the manual labour of entering transactions in ledger is not
necessary
All these are to be automated and an application is required to relate all of them relatively and logically so that the current system can be replaced and accepted without major changes and problems.
The application should provide quick access to the records maintained and must reveal the important reviews about the business so that the growth can be easily compared and should provide with the various reports showing the related details so that the important decisions could be taken easily.
Security of the stored information is achieved here. Only privileged users can gain access to the stored information. Computers perform most of the tasks and any information is made available at the users’ fingertips. Storage of all the customer information and the transactions has been
computerized.
EXISTING SYSTEM
Existing Application does not help the Insurance Agents
to Manage Policy Transactions easily.
Existing Application does not helps the Agents to Monitor and perform transaction easily.
In the Customer view, it does not provides the Customers
with their personal account through which they can perform the Transactions.
Manual maintenance of records
Very complex and manual calculation of policy premium
time consuming to summarize these details to produce
the reports
Difficult to handle and manage bulk data.
Difficult to Organizes and tracks insurance and the policies provided under different coverage
If customer requests for any clarification the person in charge has to search through the written records and fetch the details regarding that particular customer, which is time consuming and cumbersome.
Security of the information maintained is comparatively
less.
Maintenance of the ledgers occupy large space
PROPOSED SYSTEM
a) Helps the Agents to maintain the details of all the Policy Holders electronically.
b) This project helps the Customers to be aware of the dues and also the previous payment details made for
Updating Policy ,Policy Maturity, Policy lapse, Policy renewal etc .
c) The application will provide quick access to the records for customer to maintain and reveal the important
reviews about the policies.
d) It provides for effective maintenance of records regarding customers, regarding customers, transactions etc. Initially it may cost more but proves to be cost effective in the long run.
e) Helps to Provide with the various reports showing the related details so that the important decisions could be taken easily.
f) Application should provide quick access to the records maintained and must reveal the important review
g) High Security to sensitive and important data h) Automated Premium calculator
SOFTWARE REQURIEMENTS
Category : Web Based
Platform : Windows XP2 or higher
Web Server : Apache Tomcat 5.5
Presentation : HTML 4.0, CSS
Client Side Validation : JavaScript
Server Side Validation : Java Servlets, JSP
Database Connectivity : JDBC
RDBMS : MySql 5.1
• HTML : It is a basic tool to make and edit Web page.
• JSP : Java Server Pages™ technology is the Java™
technology in the J2EE platform for building applications containing dynamic Web content such as HTML, DHTML, XHTML and XML. The Java Server Pages technology
enables the authoring of Web pages that create dynamic content easily but with maximum power and flexibility.
• Apache Tomcat 5.5 : Apache is a Web Server .
• MySQL is a relational database managements system
(RDBMS) that runs as a server providing multi-user access to a number of databases.
HARDWARE REQURIEMENTS
Processor : Pentium 4 or Higher
Mouse : PS2/USB Mouse
Monitor : VGA Monitor
RAM : 512 MB
Hard disk : 40 GB
Clock Speed : 600 MHz
ABOUT SOFTWARE Why Java is selected?
Java was designed to meet all the real world requirements with its key features, which are explained in the following paragraphs:
Simple and powerful.
Java was designed to be easy for the professional programmers to learn and use efficiently. Java makes itself simple by not having surprising features. Since it exposes the internal working of the machine, the programmers can perform his desired action without fear. Unlike other programming systems that provide dozens of complicated ways to perform a simple task, Java provides a small number of clear ways to achieve a given task. Secure
Today everyone is worried about safety and security. Using Java Compatible Browser, anyone can safety download applets without fear of viral infections or malicious intent. Java achieves this protection by confining a Java program to Java execution environment and by making it inaccessible to other parts of the computer.
Portable.
In Java, the same mechanism that gives security helps in portability. Many types of computers and operating systems are used throughout the world and are connected to the Internet. For downloading programs through different platforms connected o the Internet, some portable, executable ode is needed. Java’s answer to these problems is its well-designed architecture.
Object-oriented.
Java was not designed to be source code compatible with any other language. Java team gave a clean, usable, realistic approach to objects. The object model in Java is simple and easy to extend, while simple types, such as integers, are kept
as high-performance non-objects. ust
Multithreaded.
Java was designed to meet the real-world requirements of creating interactive, networked programs. To achieve this, Java supports multithreaded programming, which allows user to write programs that perform many function simultaneously.
The Java run-time system enables the user to construct smoothly running interactive systems. Java’s easy-to-use approach to multithreading allows the user to think about the specific behavior of his own program, not the multitasking subsystem. The Java designers worked hard in attaining their goal “ write once; run anywhere, anytime, forever” and as a result the Java Virtual Machine was developed.
A main issue for the designers was that of code longevity and portability. One of the main problems is the execution speed of the program. Since Java is architecture-neutral it generates byte code that resembles machine code, and are not specific to any processor
SERVLETS:
A servlet is a web component, managed by a container that generates dynamic content. Servlets are small, platform independent Java classes compiled to an architecture neutral byte code that can be loaded dynamically into and run by a web server. Servlets interact with web clients via a request response paradigm implemented by the servlet container. This request-response model is based on the behavior of the Hypertext Transfer Protocol (HTTP).
The servlet container, in conjunction with a web server or application server, provides the network services over which requests and responses are set, decodes MIME based requests, and formats MIME based responses. A servlet
container also contains and manages servlets through their lifecycle. A servlet container can either be built into a host web server or installed as an add-on component to a Web Server via that server’s native extension API. Servlet Containers can also be built into or possibly installed into web-enabled Application Servers. All servlet containers must support HTTP as a protocol for requests and responses, but may also support other request / response based protocols such as HTTPS (HTTP over SSL). The minimum required version of the HTTP specification that a container must implement is HTTP/1.0. It is strongly suggested that containers implement the HTTP/1.1 specification as well.
A Servlet Container may place security restrictions on the environment that a servlet can executed In a Java 2 Platform Standard Edition 1.2 (J2SE) or Java 2 Platform Enterprise Edition 1.3 (J2EE) environment, these restrictions should be placed using the permission architecture defined by Java 2 Platform. For example, high end application servers may limit certain action, such as the creation of a Thread object, to insure that other components of the container are not negatively impacted.
Java Server Pages™ technology is the Java™ technology in the J2EE platform for building applications containing dynamic Web content such as HTML, DHTML, XHTML and XML. The Java Server Pages technology enables the authoring of Web pages that create dynamic content easily but with maximum power and flexibility. The Java Server Pages technology provides a textual description for the creation of a response from a request.
The JSP file extension is .jsp rather than .htm or .html. The JSP engine parses the .jsp and creates a Java servlet source file. It then compiles the source file into a class file, this is done the first time and this why the JSP is probably slower the first time it is accessed. Any time after this the special compiled servlet is executed and is therefore returns faster.
BENEFITS OF JSP:
Write Once, Run Anywhere™ properties
The Java Server Pages technology is platform
independent, both in its dynamic Web pages, Web servers, and its underlying server components. You can author JSP pages on any platform, run them on any Web server or Web enabled application server, and access them from any Web browser.
Separation of dynamic and static content
The Java Server Pages technology enables the separation of static content from dynamic content that is inserted into the static template.
Support for scripting and actions
The Java Server Pages technology supports scripting elements as well as actions. Actions permit the encapsulation of useful functionality in a convenient form that can also be manipulated by tools; scripts provide a mechanism to glue together this functionality in a per-page manner.
Web access layer for N-tier enterprise application architecture(s)
The Java Server Pages technology is an integral part of the Java 2 Platform Enterprise Edition (J2EE), which brings Java technology to enterprise computing.
PROBLEM DEFINATION
The first step in an initial investigation is to define the problem that led the user request. The problem must be state clearly, understood and agreed upon by the user and the analyst. It must state the objectives the user is trying to achieve and the result the user wants to see.
The System entitled “INSURANCE MANAGEMENT SYSTEM”, to be developed is intended to be a Web based application to help users the easy and efficient way of maintaining the records and the details of their reports and to provide a Satisfied service to the quality controller.
The developed system should allow admin users to register agents persons with their name, date of birth, residence address, and also policy details of various costumers enrolled for policies avaliable. After registering all the insured persons, website should provide management facilities like delete unwanted data such as of agents, Insured persons, Policy details, insurers’ list and also should provide awareness to the visitors about various insurance through articles .
FEASIBILITY STUDY
Preliminary investigation examines project feasibility; the likelihood the system will be useful to the organization. Feasibility report is the important outcome of the preliminary investigation. There are three aspects of feasibility study.
Operational feasibility:
There is lot of support from management; in fact they request it. Because of the persons in the organization has been facing problems with the existing system there is no resistance to the change. And also the current methods are not acceptable to the users that are why they are welcoming to the new system. From the beginning of this new system we made users to involve in some way reducing the resistance. The new system will not cause any problems in any way and also will show efficient performance in all respects. By considering all these things the proposed new system is operationally feasible.
Technical feasibility:
There is no technology and equipment to implement the new system but it can be acquired. It is not a burden rather than that of existing system. The proposed equipment can safely handle the data required to use the new system. The proposed new system can easily be expanded to satisfy the new requirements in future. There is lot of security, accuracy and reliability in the new system rather than existing system. By considering the above reasons the proposed new system is technically feasible.
Economic feasibility:
The cost to implement this new system includes cost of full systems investigation, cost of hardware and software and the cost of user training. The cost that may spend if the new system was not developed is greater than the cost of the new system. The cost to implement the proposed system is one time investment later they need not spent any more. The organization must get benefit if they invest on the proposed
system development. By considering the above reasons the proposed new system is economically feasible.
As this proposed system has passed all the three aspects of feasibility study we can declare it as a feasible project.
SYSTEM ANALYSIS
System analysis provides major planning elements in preparation of data processing system.
Analysis is detailed study of various operations performed by a system and their relationships within and outside of the system and determining whether or not a candidate system should conceder other related systems. During analysis, data are collected on the available files, decision points and transactions handled by the present system. Once an analysis is completed, the next step is to decide how the problem might be solved.
System is a orderly grouping of independent components linked together according to a plan to achieve a specific object. A system records and process data then provides information from it. System analysis concerned with investigation, analyzing, designing and evaluating the system.
The process of developing a computer based information system is a step-by-step approach it begins with logical design and gradually moves to physical design specific documentation associated with each step in the process, and the output document of one step serves as input to the next step. The step in system development is explained with their respective criteria. Once an analysis is completed, the next step is to decide is problem might be solved.
SYSTEM REQUIREMENT SPECIFICATION Modules Description
Administration Module
a) Create Agent : Allows Administrator to create New agent by giving his agent’s username and Password b) Create New Plan : Allows Administrator to Add new
Plan
User/ Costumer Module
a) Get New Policy : Allows User to buy a plan
b) Plan Information : Allows user to retrieve various plans information
c) Owned policies : This allows to see the history to user of his owned plans
d) Update user information : Allows to update and edit user infomation
e) Pay premium : This allows policy holder to pay premium insurance amount
f) Reset User password: This Allows to Reset User password
Agent Module
a) View /update profile : This allows Agents to view, edit and modify his project
b) Add new policy to costumer: This allows Agents
to buy a policy for customer when on demanded. c) Customer due payment : This allows agents to
check customers due payments
d) Reset agent password : This allows agent to reset his password
New User Registration Module
This module allows a new customer to register to this website freely
a) Plan information : This allows both Agent and Customer to know the plans information and it’s descriptions.
b) Premium Calculator : This allows both customer and agents to calculate Premium for various plans
c) Locate Branch : This allows both customer and agents to locate various branches of insurance company
d) Locate Agent : This allows customer to locate
agents by giving area pin
SYSTEM DESIGN
The most creative and challenging phase of the system life cycle is system design. The term design describes a final system and the process by which it is developed. It refers to the technical specification that will be applied in implementing the candidate system.
The main step in design is to determine how the output to be produced and in what format.
System Design is multistep process that focuses on the data structure software architecture procedural detail and interface between the
models. The design process also translates the requirements into the representation of the software that can be accessed
for quality before coding begins.
Computer software design is relatively easily in its evaluation. Therefore, software methodology lacks the dependent flexibility and quantitative nature that is normally associated with classical engineering design disciplines.
System design goes through three phases of development:-1. Logical Design
2. Physical Design 3. Structural Design
1. Logical Design:
Logical design describes the inputs outputs databases and procedural all in a format that meets user requirements.
When analyst prepares the logical system design, they specify the user needs at a level of details that virtually determines the information flow into and out of the system and the required data resources.
2. Physical System Design:
Physical design produces the working system by defining the design specifications that tell the programmers exactly what the candidate system must do. In turn, the programmer writes the necessary programs or modifies the software package that accepts input from the user, performs the necessary calculations through the existing file or data-base , produces
the report on a hard copy or displays it on the screen, and maintains an updated data base at all the times.
3. Structural Design:
Structured design is a data-flow-based methodology. The approach begins with a system specification that identifies input and outputs and describes the functional aspects of the system. The system specifications then are used as a basis for the graphic representation- data flow diagram (DFD). From the DFD, the next step is the definition of modules and their relationships to one another in a form called a structure chart, using a data dictionary and other structured tools.
DATAFLOW DIAGRAMS
Data Flow Diagram :
The Data Flow Diagrams are commonly used during problem Analysis. A DFD is very useful in understanding the system effectively. The DFD shows the flow of data through a system.
Notations in the DFD :
Symbol Description
The circle or bubble represents a process. A process is named and each process is represented by a named circle.
The source or sink is represented as a rectangular box. The source or sink is the net originator or the consumer of the data that flows
in the system.
The arrow represents the flow of data through the system. The labeled arrows enter or leave the bubbles.
The database is represented with the open box symbol
*
The need for multiple data flows i.e AND relationship by a process is represented by * between data flows.
+ The OR relationship between data flows is
represented by + between data flows.
Context Flow Diagram
DFD Level-1 :
ENTITY-RELATIONSHIP
An Entity – Relationship (ER) diagram is a specialized graphic that illustrates the inter relationship between entities in a database. ER diagrams often used symbols to represent three different types of information. They are :
Name Notation Description
Entity
An entity is single object about which data can be stored it is the
“subject“ of a table. Entities and their relationships are modelled
through the use of entity relationship diagrams.
Relationship
A relationship is a named collection or association between entities or
used to relate to two or more entities with some common attributes or meaningful interaction
between the objects.
Attributes
An attribute is a single data item related to a database object. The database schema associates one or more attributes with each database
entity.
Insured Person’s details diagram
INSURED PERSON – PERSONAL DETAILS RELATION Insured Person Personal details Ha s 1 1 Occupation History Ha s n 1
AGENT PERSON – PERSONAL DETAILS RELATION
AGENT PERSON – RELATION
Insured Person Identity Personal details Ha s 1 1 Name Gender Date of Birth/Age Insured Person Identity Personal details Ha s 1 1 Name Gender Date of Birth/Age Insured Person Residence History Ha s n 1 Identity Residence Date Village District State Block Pin
1. Converting relationships
Relationships are based on cardinalities and degree of
the relation m:n m n Binary 1:1 1 1 ER-DIAGRAM POLICY HOLDER POLICY INSUR ED BY POLICY HOLDER AGENT CHOO SES
DATA BASE DESIGN
Database:
A Database is collection of related data, which can be of any size and complexity. By using the concept of Database, we can easily store and retrieve the data. The major purpose of a database is to provide the information, which utilizes it with the information’s that the system needs according to its own requirements. Database Design:
Database design is done before building it to meet needs of end-users within a given information-system that the database is intended to support. The database design defines the needed data and data structures that such a database comprises.
The database is physically implemented using
MySQL.
MySQL is a relational database managements system (RDBMS) that runs as a server providing multi-user access to a number of databases.
The database for Insurance System is organized into 7 tables:
agent_info
Field Type Null Default
agent_id varchar(35) Yes
password varchar(35) Yes NULL
first_name varchar(20) Yes NULL
middle_name varchar(2
0) Yes NULL
last_name varchar(20) Yes NULL
gender varchar(6) Yes NULL
1 0) Address_line_
2 varchar(20) Yes NULL
city varchar(35) Yes NULL
state varchar(3
5) Yes NULL
country varchar(20) Yes NULL
pincode varchar(6) Yes NULL
phone varchar(10) Yes NULL
mobile varchar(12) Yes NULL
email varchar(40) Yes NULL
date_of_birth date Yes NULL
branch_id int(11) Yes
branch_info
Field Type Null Default
id int(11) Yes NULL
name varchar(50) Yes
Address varchar(80) Yes
city varchar(35) Yes
state varchar(3
5) Yes
country varchar(35) Yes
pin varchar(6) Yes
manager_na
life_insurence_info
Field Type Null
policy_id int(11) Yes
insured_perso n
varchar(50
) Yes
date_of_birth date Yes
address varchar(150) Yes
Plan_info
Field Type Null
plan_id int(11) Yes
plan_nam
e varchar(100) Yes
descriptio
n varchar(2000) Yes
policy_taken
Field Type Null
policy_id int(11) Yes
user_id varchar(35) Yes
plan_id int(11) Yes
start_date date Yes
duration int(2) Yes
payment_durati
on varchar(15) Yes
premium_history
Field Type Null
premium_id bigint(20) Yes
policy_id int(11) Yes
premium_amou
nt bigint(20) Yes
date date Yes
status varchar(20) Yes
mode_payment varchar(20) Yes
agent_id varchar(35) Yes
user_info
Field Type Null
user_id varchar(35) Yes
password varchar(35) Yes
first_name varchar(2
0) Yes
middle_name varchar(20) Yes
last_name varchar(20) Yes
gender varchar(6) Yes
Address_line_
1 varchar(20) Yes
Address_line_
2 varchar(20) Yes
city varchar(35) Yes
5)
country varchar(20) Yes
pincode varchar(6) Yes
phone varchar(1
0) Yes
mobile varchar(12) Yes
email varchar(40) Yes
date_of_birth date Yes
occupation varchar(20) Yes
annual_incom int(11) Yes
SOFTWARE TESTING
This software product consist modules, Cultivation, Inventions, Marketing and reports. All 3 modules have finite number of functions, for all modules unit testing was carried out. Some errors were detected in the function, which were solved efficiently. System testing was followed by this specific set of data that was selected for the testing, with each test, test reports were generated indicating the behavior of each unit.
TEST CASE DETAILS
Unit testing was carried on all units of “Computerization of manufacturing pharmaceutical products “, below given are some test case details.
Test case Result When character is Please enter
number
Entered in a number Field
When any data is Please fill all records Left blank
When no record is there No record left to delete
UNIT TESTING
Unit testing is nothing but testing each module with both valid and invalid data. Appropriate message will be displayed for invalid test case and result is produced for the valid ones. Later individual functions were used put together and made to behave properly gaining exact results.
Unit testing is the most important testing when considered with other forms of testing.
After completing all sorts of test cases on all the forms they all are integrated to form the result. This integrated testing was done with the sample data .The need for performing a integrated testing is to find the overall performance of the system.
BLACK BOX TESTING
Black box testing is done in order to some of the following types of errors
Missing functions or an incorrect function.
Interface error.
Error in the external database access.
Performance error
Initialization error and
Termination error.
WHITE BOX TESTING
White box testing is another type of testing technique used to find errors in a application, using this white box testing
the following test cases were successfully tested to this project
Checking weather all independent paths within the module have been exercised at least once or not
All conditions are executing or not
Exercise internal data structure to ensure their validity
All possible validity checks are given or not.
CODING
Home Page
<html>
<head><title>Insurence::Home Page</title></head> <body>
<table width="100%" border="0"> <tr width="100%">
<td colspan="3"><img src="../../images/banner.jpg" width=100% height=200></td>
</tr> <tr>
<td width="20%" height="578" rowspan="2" valign="top"> <table width="95%" border="0" bgcolor="#dddddd" >
<tr align="center">
<td><a href="index.jsp">Home</a></td> </tr>
<tr align="center">
<td><a href="index.jsp?page=plan_info.jsp" >Plan Information</a> </td>
<tr align="center"> <td><a href="index.jsp?
page=premium_calculator.jsp">Premium Calculator</a></td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center">
<td><a href="index.jsp?page=search_branch.jsp">Locate Branch</a></td>
</tr>
<tr align="center">
<td><a href="index.jsp?page=search_agent.jsp">Locate Agent</a></td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center"> <td> </td> </tr>
</table> </td>
<td width="60%" rowspan="2" valign="top"> <table>
<tr> <td>
<h1 align="center">Insurance</h1><br/>
This Online Insurance makes a great starting point for your future and Present .The facilities provided by the online Insurance system will supervise and secure future of the
policy holder.It not only secures the life but also provides loan facility .It is one of opportunities to secure your family and children's future.</pre> </td> <td><img src="../../images/Insure.jpg" /></td> </tr> </table> </td> <td width="20%" valign="top">
<table width="100%" border="0" bgcolor="#dddddd" align="center">
<tr align="center">
<td>Admin <a href="../admin/index.jsp">Login Here</a></td>
</tr>
<td>Agents <a href="../agent/index.jsp">Login Here</a></td>
</tr>
<tr align="center">
<td>Registered User <a href="index.jsp? page=user_login.jsp">Login Here</a></td> </tr>
<tr align="center">
<td>New User !!! <a href="index.jsp?
page=user_registration.jsp">Sign Up here</a></td> </tr> </table> </td> </tr> </table> </body> </html>
Admin Login Page
<html> <head> <title> </title> </head> <body> <a href="../../index.jsp">Home</a> | <a href="javascript: window.history.back();">Back</a> <h1 align="center">Admin Login Form</h1>
<form action="Action/login.jsp" method="post" name="admin_login">
<table width="80%" border="0" align="center"> <tr bgcolor="#dddddd">
<td><input name="admin_id" type="text" size="35" maxlength="35" /> </td>
</tr>
<tr bgcolor="#dddddd"> <td>Password</td>
<td><input name="pass" type="password" size="35" maxlength="35" /> </td>
</tr> <tr>
<td><input name="" type="submit" value="Login" /></td> <td><input name="" type="reset" value="Reset"/></td> </tr> </table> </form> </body> </html> Agent login <html>
<head><title>Agent Home Page</title></head> <body>
<img src="../../images/banner.jpg" width="100%" height="200"/> <a href="../../index.jsp">Home</a> | <a href="javascript: window.history.back();">Back</a>
<!--<a href="javascript: window.history.back()">Back</a>--> <h1 align="center">Agent Home Page</h1>
<div style="color:red;" align="center">
<form action="Action/login.jsp" method="post" name="agent_login"> <table width="60%" border="0" align="center">
<tr bgcolor="#dddddd"> <td>Agent ID:</td>
<td><input name="agent_id" type="text" size="35" maxlength="35" /> </td>
</tr>
<tr bgcolor="#dddddd"> <td>Password</td>
<td><input name="pass" type="password" size="35" maxlength="35" /> </td>
</tr> <tr>
<td><input name="" type="submit" value="Login" /></td> <td><input name="" type="reset" value="Reset"/></td> </tr>
</table> </form> </body> </html>
User Login Page
<html>
<head><title>Insurence::Home Page</title></head> <body>
<table width="100%" border="0"> <tr width="100%">
<td colspan="3"><img src="../../images/banner.jpg" width=100% height=200></td>
</tr> <tr>
<td width="20%" height="578" rowspan="2" valign="top"> <table width="95%" border="0" bgcolor="#dddddd" >
<tr align="center">
<td><a href="index.jsp">Home</a></td> </tr>
<tr align="center">
<td><a href="index.jsp?page=plan_info.jsp" >Plan Information</a> </td>
</tr>
<tr align="center"> <td><a href="index.jsp?
page=premium_calculator.jsp">Premium Calculator</a></td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center">
<td><a href="index.jsp?page=search_branch.jsp">Locate Branch</a></td>
</tr>
<tr align="center">
<td><a href="index.jsp?page=search_agent.jsp">Locate Agent</a></td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center"> <td> </td> </tr>
<tr align="center"> <td> </td> </tr> <tr align="center"> <td> </td> </tr> </table> </td>
<td width="60%" rowspan="2" valign="top">
<script language="javascript" type="text/javascript" > function checkAll()
{
check_null("user_id","User Name"); check_null("password","Password"); if(str=="Please Check the following \n") { return true; } else { alert(str);
str="Please Check the following \n"; return false;
} }
</script>
<script language="javascript" type="text/javascript" src="../../js/validation1.js" >
</script>
<div><a href="javascript:
window.history.back();">Back</a></div>
<div align="center"><h1>User Login</h1></div> <div style="color:red;" align="center">
</div>
onSubmit="return checkAll()">
<table width="80%" border="0" align="center"> <tr bgcolor="#dddddd">
<td>User Name:</td>
<td><input name="user_id" type="text" size="35" maxlength="35" id="user_id"/></td>
</tr>
<tr bgcolor="#dddddd"> <td>Password:</td>
<td><input id="password" name="password"
type="password" size="35" maxlength="35" /></td> </tr>
<tr>
<td><input name="login" type="submit" value="Login" /></td>
<td><input name="reset" type="reset" value="Reset" /></td> </tr> <tr> <td></td> <td></td> </tr> </table> </form> </td> <td width="20%" valign="top">
<table width="100%" border="0" bgcolor="#dddddd" align="center">
<tr align="center">
<td>Admin <a href="../admin/index.jsp">Login Here</a></td>
</tr>
<tr align="center">
Here</a></td> </tr>
<tr align="center">
<td>Registered User <a href="index.jsp? page=user_login.jsp">Login Here</a></td> </tr>
<tr align="center">
<td>New User !!! <a href="index.jsp?
page=user_registration.jsp">Sign Up here</a></td> </tr> </table> </td> </tr> </table> </body> </html>
User Registration Form
<html>
<head><title>Insurence::Home Page</title></head> <body>
<table width="100%" border="0"> <tr width="100%">
<td colspan="3"><img src="../../images/banner.jpg" width=100% height=200></td>
</tr> <tr>
<td width="20%" height="578" rowspan="2" valign="top"> <table width="95%" border="0" bgcolor="#dddddd" >
<tr align="center">
<td><a href="index.jsp">Home</a></td> </tr>
<td><a href="index.jsp?page=plan_info.jsp" >Plan Information</a> </td>
</tr>
<tr align="center"> <td><a href="index.jsp?
page=premium_calculator.jsp">Premium Calculator</a></td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center">
<td><a href="index.jsp?page=search_branch.jsp">Locate Branch</a></td>
</tr>
<tr align="center">
<td><a href="index.jsp?page=search_agent.jsp">Locate Agent</a></td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center"> <td> </td> </tr> <tr align="center">
<td> </td> </tr>
</table> </td>
<td width="60%" rowspan="2" valign="top">
<script language="javascript" type="text/javascript" > function checkAll() { check_null("user_id","User ID"); check_null("password","Password"); check_null("confirm_password","Confirm Password"); compare("password","confirm_password","Password","The two passwords don't match");
check_null("first_name","First Name"); check_null("last_name","Lirst Name"); check_null("Address_line_1","Address Line 1"); check_null("Address_line_2","Address Line 2"); check_null("city","City"); check_null("state","State"); check_null("country","Country"); check_numaric("pincode","Pin code"); check_numaric("phone","Phone Number"); check_numaric("mobile","Mobile Number"); check_RegExp("email","EMail Id",/^([a-zA-Z0-9])+([\.a-zA-Z0-9_-])*@([a-zA-Z0-9])+(\.[a-zA-Z0-9_-]+)+$/); check_null("occupation","Occupation"); check_numaric("annual_incom","Annual Income"); if(str=="Please Check the following \n")
{ return true; } else { alert(str);
str="Please Check the following \n"; return false;
} }
</script>
<script language="javascript" type="text/javascript" src="../../js/validation1.js">
</script>
<a style="left:20%; position:absolute" href="javascript: window.history.back();">Back</a>
<div align="center"><h1>User Registration Form</h1></div>
<div style="color:red;" align="center">
</div>
<form action="Action/user_registration.jsp" method="post" onSubmit="return checkAll()">
<table width="80%" align="center" border="0"> <tr bgcolor="#dddddd">
<td>User ID: (Max. length: 35)</td>
<td><input name="user_id" id="user_id" type="text" size="35" maxlength="35"></td>
</tr>
<tr bgcolor="#dddddd">
<td>Password:(Max. length: 35)</td>
<td><input name="password" id="password"
type="password" size="35" maxlength="35"></td> </tr>
<tr bgcolor="#dddddd"> <td>Confirm Password:</td>
<td><input name="confirm_password"
id="confirm_password" type="password" size="35" maxlength="35"></td>
</tr>
<tr bgcolor="#FFFFFF"> <td>First Name:</td>
<td><input name="first_name" id="first_name" type="text" size="35" maxlength="20"></td>
</tr>
<tr bgcolor="#FFFFFF"> <td>Middle Name:</td>
<td><input name="middle_name" id="middle_name" type="text" size="35" maxlength="20"></td>
</tr>
<tr bgcolor="#FFFFFF"> <td>Last Name:</td>
<td><input name="last_name" id="last_name" type="text" size="35" maxlength="20"></td>
</tr>
<tr bgcolor="#FFFFFF"> <td>Gender</td>
<td><input name="gender" type="radio" value="Male" id="male" checked="checked"><label for="male"> Male</label> <input name="gender" type="radio" value="Female" id="female"><label for="female">Female</label></td> </tr> <tr bgcolor="#ffffff" > <td>Date of Birth</td> <td> <select name="date"> <option value='1'>1</option> <option value='2'>2</option> <option value='3'>3</option> <option value='4'>4</option> <option value='5'>5</option> <option value='6'>6</option> <option value='7'>7</option> <option value='8'>8</option> <option value='9'>9</option> <option value='10'>10</option> <option value='11'>11</option> <option value='12'>12</option> <option value='13'>13</option> <option value='14'>14</option>
<option value='15'>15</option> <option value='16'>16</option> <option value='17'>17</option> <option value='18'>18</option> <option value='1912'>1912</option> <option value='1911'>1911</option> <option value='1910'>1910</option> <option value='1909'>1909</option> <option value='1908'>1908</option> <option value='1907'>1907</option> <option value='1906'>1906</option> <option value='1905'>1905</option> <option value='1904'>1904</option> <option value='1903'>1903</option> <option value='1902'>1902</option> <option value='1901'>1901</option> <option value='1900'>1900</option> </select> </td> </tr> <tr bgcolor="#dddddd"> <td>Address Line 1:</td>
<td><input name="Address_line_1" id="Address_line_1" type="text" size="35" maxlength="20"></td>
</tr>
<tr bgcolor="#dddddd"> <td>Address Line 2:</td>
<td><input name="Address_line_2" id="Address_line_2" type="text" size="35" maxlength="20"></td>
</tr>
<tr bgcolor="#dddddd"> <td>City:</td>
<td><input name="city" id="city" type="text" size="35" maxlength="35"> </td>
<tr bgcolor="#dddddd"> <td>State:</td>
<td><input name="state" id="state" type="text" size="35" maxlength="35"></td>
</tr>
<tr bgcolor="#dddddd"> <td>Country:</td>
<td><input name="country" id="country" type="text" size="20" maxlength="20"></td>
</tr>
<tr bgcolor="#dddddd">
<td>Pin-code / Zip-code:</td>
<td><input name="pincode" id="pincode" type="text" size="6" maxlength="6"></td>
</tr>
<tr bgcolor="#dddddd">
<td>Phone:(with STD code)</td>
<td><input name="phone" id="phone" type="text" size="10" maxlength="10"></td>
</tr>
<tr bgcolor="#dddddd"> <td>Mobile Number:</td>
<td><input name="mobile" id="mobile" type="text" size="12" maxlength="12"></td>
</tr>
<tr bgcolor="#dddddd"> <td>E-Mail:</td>
<td><input name="email" id="email" type="text" size="40" maxlength="40"></td>
<tr>
<td>Occupation:</td>
<td><input name="occupation" id="occupation" type="text" size="20" maxlength="20"></td> </tr> <tr> <td>Annual Income:</td> </tr> <tr align="center">
<td>New User !!! <a href="index.jsp?
page=user_registration.jsp">Sign Up here</a></td> </tr> </table> </td> </tr> </table> </body> </html> SCREEN SHOTS Home Page
Customer Policy Information
CONCLUSION
A computerized insurance management system has been developed and the system was tested with sample data.
The system results in regular timely preparations of required outputs. In comparison with manual system the benefits under a computer system are considerable in the saving of man power working hours and Effort.
Provision for addition , updation and deletion of customers is there in the system .It is observed that proper filing system has been adopted for future reference . The entire project runs on windows environments.
The system can be used to make better management described at appropriate time. The user gets amount and timely information system.
SCOPE OF ENHANCEMENT
The system may be further updated or modified at will owing to its simple structure. We can further add a
transaction entity which will look after the payments made by the customer towards their policy.
Depending on future requirements more changes can be made owing to the organization’s need.
After finishing the requirements for phase-1 of the development the remaining estimated modules will be developed. The following enhancements may be added to the existing modules.
Add new Administrators
Enhancement of search options after completion of the
pahse-2
These features are estimated depends upon the requirements of the client in phase-2. So, these modifications require completion of the pahse-2 development of the project.
Bibliography
Using Java2 Platform Joseph Weber
Java Servlets Programming BPB Publications
SQL Complete Reference Oracle Press
Principles of database systems Jeffery D Ullman
Database Management Systems C J Date
Web References . http://www.w3schools.com. http://www.codeproject.com. http://www.uml.org. http://www.planetsource.com