Académique Documents
Professionnel Documents
Culture Documents
1. Abstract
2. Introduction
2.1 Organization Profile
2.2 About the project
3. System Analysis
3.1 Existing system
3.2 Problem Definition
3.3 Proposed System
3.4 Requirement Analysis
3.5 Feasibility study
4. System Design
4.1
Project Modules
4.2
Data Dictionary
4.3
4.4
E-R Diagrams
4.5
4.6
4.7
UML Diagrams
Activity diagrams
Hardware And Software Requirements
5. System Testing
6. Software Tools Used
7 Technical Notes
8.
7.1
7.2
7.3
Introduction to Java
Screens
9. Conclusion
10. Bibliography
1. Abstract
Apna life insurance system automates the management of Apna life
insurance activities, which involves Defining Policies, Schemes, Policy
Specifications, Policy Terms and Conditions, Policies registrations by the
customers, Facilitates the Premiums Flexi-Pay modes, Policy Bonus in Flexible
periods.
The Agents are involved in the process of the Customer Policy registration
and the Commissions are based on the targets achieved by the Agents.
Apna life insurance System also maintains the database of the Branch
Managers who deals with the Agents which in turn deals with the Customers.
2. INTRODUCTION
2.1 ABOUT THE ORGANIZATION
Chairman
Manager
Customer
Agent.
The Second chapter explains the exact Definition of the Problem and
evolves out with the Feasibility Study of the product/part.
The Third chapter is System Analysis which deals about the Hardware
and Software Specifications, and Software Requirement Specification, under this
SRS Formal Description and Module Description.
The Fourth chapter describes the System Design, under this two levels of
designs, they are
whole project.
The Sixth chapter deals the Conclusion and Foreseeable Enhancements
of the system.
The Seventh chapter deals about the Bibliography of this Project.
The Eight chapter is the final one which deals about the language
used, tools used, Screen layouts and Reports
Reports
3. SYSTEM ANALYSIS
3.1 Existing system
Before developing this application all activities done manually, then all the
activities take more time and also take more manpower. Commission, interests,
dues calculate manually, based on this manual problem some times calculate the
wrong
All related information passed one branch to another branch through
courier. Some times missed the important documents. So these problems
overcome when we will develop the system. This system is very helpful to
automation of entire Apna life insurance system and also reduces the time and
manpower.
Users of the system:
The users of the system are company chairman, Branch Managers,
Customer, Agents. This system is designed such a way that the users can easily
interact with the system with minimum knowledge.
3.2 PROBLEM DEFINITION AND FEASIBILITY ANALYSIS
Definition of the problem
To create or develop a new system first we have to study the prior
system, Analysis difficult problems faced by the operator of that system. System
Analysis therefore understands such problems and proposes a new system in
which the above problems are rectified.
3.3 Proposed System
Operational Feasibility
In this test, the operational scope of the system is checked. The system
under consideration should have enough operational reach. It is observed that
the proposed system is very user friendly and since the system is built with
enough help, even persons with little knowledge of windows can find the system
very easy.
Technical Feasibility
This test includes a study of function, performance and constraints that
may affect the ability to achieve an acceptable system. This test begins with an
assessment of the technical viability of the proposed system. One of the main
fusers to be accessed is the need of various kinds of resources for the
successful implementation for the proposed system.
Economical Feasibility
An evaluation of development cost weighed against the ultimate income or
benefit derived from the development of the proposed system is made. Care
must be taken that incurred in the development of the proposed of the system
should not exceed from the system. The income can be in terms of money or
goodwill, since the software brings in both, the system is highly viable.
Hardware requirements
Software requirements
Hardware Requirements:
The selection of hardware is very important in the existence and proper
working of any software. In the selection of hardware, the size and the capacity
requirements are also important.
The Web Based Manufacturing System can be efficiently run on Pentium
system with at least 128 MB RAM and Hard disk drive having 20 GB. Floppy disk
drive of 1.44 MB and 14 inch Samsung color monitor suits the information
system operation.(A Printer is required for hard copy output).
RAM Capacity
--------
Hard Disk
--------
Floppy disk
--------
CD-ROM Drive
--------
32 HZ
Software Requirements:
One of the most difficult tasks is that, the selection of the software, once
system requirement is known is determining whether a particular software
package fits the requirements. After initial selection further security is needed to
determine the desirability of particular software compared with other candidates.
This section first summarizes the application requirement question and then
suggests more detailed comparisons.
Operating System
Browser
--
IE
Web/Application Server
--
Tomcat Server
Database
--
Oracle
Database Connectivity
--
JDBC
Java Technologies
--
Windows 98/NT/2000
--
Scripting Technology
--
Java Script
4. SYSTEM DESIGN
4.1 Project Modules
Modules Description:
Branch Establishments
Reports:
2. Manager
Policy Details
Branch Manager details
Agents Details
Customer details
The Managers of the different branches recruits the Agents and also
registration of customers. He is also responsible for
calculate
registration of Policies,
also agent
Customer Registrations
Customer Bonus
Agent Commission
Reports
Policy details
Agent Commission
Customer Details
Policy Details
3. Agents
The main role of Agents is to registration of the
Customers. Agents just like a mediator between Apna life insurance system and
Customers. Based on their performance they will get commission. These
systems provide a facility to Agents like to visible their Commission and also their
customer details.
Manager Details
4. Customer
The Customers are a main source of this system. Based on his
interest and benefits, he takes a policy. Customers also take more than
one policy based on their requirement. Here so many facilities are
provided to the Customers, like their information visible on line, like
premium dates, bonus dates, personal details, policy details.
The responsibilities of the Customers as follows
Design Description
Design is essentially a blue print or it acts as a bridge between the
requirement specification and the final solution for satisfying the requirements.
Based on the work-flow described above we can draw the following
conclusions for the Software System that has to be developed:
The System needs to store the details of all the Premiums that are available
of the company.
The System needs to store the details of all the Customers held in the
Company warehouse.
The System needs to store the details of all the Agents held in the Company.
The System needs to store the details of all the Branch Managers details.
The System should allow the Customers to visible their next premium dates,
bonus, dues and related information.
The System should provide an option to generate a Agents Reports, with the
help of these reports estimate of their performance
For the above to take place the system should store the Premium details of
the Customers. If any future modification required, easily modify the
Customers details.
The System should provide an option that all customers are visible to latest
Policies and their specifications. This facility is very help to Customers to see
the all information through on line.
BONUSRATE
NUMBER(2)
3. Agents
Name
Null?
Type
----------------------------------------- -------- ---------------------------AGENTID
NOT NULL NUMBER(11)
AGENTNAME
VARCHAR2(22)
AGENTFNAME
VARCHAR2(22)
AGENTAGE
NUMBER(3)
AGENTSEX
VARCHAR2(1)
AGENTQUAL
VARCHAR2(22)
AGENTOCCUPATION
VARCHAR2(22)
AGENTADDRESS
VARCHAR2(22)
AGENTREGDATE
DATE
AGENTSECURITYDEPOSIT
NUMBER(10,3)
BRANCHMGRID
NUMBER(7)
4. BranchMgr
Name
Null?
Type
----------------------------------------- -------- --------------------------BRANCHMGRID
NOT NULL
NUMBER(11)
BRANCHMGRNAME
VARCHAR2(22)
BRANCHMGRFNAME
VARCHAR2(22)
BRANCHMGRAGE
NUMBER(3)
BRANCHMGRSEX
VARCHAR2(1)
BRANCHMGRQUAL
VARCHAR2(11)
BRANCHMGRADDRESS
VARCHAR2(33)
BRANCHNAME
VARCHAR2(22)
BRANCHMGRJOINDATE
DATE
5. Customer
Name
Null?
Type
----------------------------------------- -------- ---------------------------CUSTID
NOT NULL
NUMBER(11)
CUSTNAME
VARCHAR2(33)
CUSTFNAME
VARCHAR2(33)
CUSTAGE
NUMBER(3)
CUSTSEX
CUSTQUAL
CUSTADDRESS
CUSTOCCUPATION
CUSTREGDATE
VARCHAR2(1)
VARCHAR2(33)
VARCHAR2(33)
VARCHAR2(33)
DATE
6. CustPolicies
Name
Null?
Type
----------------------------------------- -------- ---------------------------CUSTPOLICYID
NOT NULL
NUMBER(11)
CUSTID
NUMBER(10)
POLICYID
NUMBER(5)
POLICYDATE
DATE
PREMIUMTYPE
VARCHAR2(10)
PREMIUMAMOUNT
NUMBER(15,2)
NOMINEENAME
VARCHAR2(33)
RELATION
VARCHAR2(20)
AGENTID
NUMBER(11)
EXPIRYDATE
DATE
7. CustpolicyAmounts
Name
Null?
Type
----------------------------------------- -------- ---------------------------CUSTPOLICYID
NUMBER(11)
AMOUNT
NUMBER(15,3)
INTERESTAMOUNT
NUMBER(15,2)
NETAMOUNT
NUMBER(15,2)
8. Custpremiumdates
Name
Null?
Type
----------------------------------------- -------- ------------------CUSTPOLICYID
NUMBER(11)
PREVIOUSPREMIUMDATE
DATE
NEXTPREMIUMDATE
DATE
9. Custpremiumtx
Name
Null?
Type
----------------------------------------- -------- ----------------------CUSTPREMIUMTXID
NOT NULL
NUMBER(22)
CUSTPOLICYID
NUMBER(11)
PREMIUMAMOUNT
PREMIUMPAYDATE
NUMBER(15,2)
DATE
10. Policycommission
Name
Null?
Type
----------------------------------------- -------- ---------------------------TARGETAMOUNT
NOT NULL
NUMBER(20,3)
COMMISSIONRATE
NUMBER(5,2)
11. PremiumAmounts
Name
Null?
Type
----------------------------------------- -------- ------------------POLICYID
NUMBER(5)
MONTHLY
NUMBER(15,2)
QUARTERLY
NUMBER(15,2)
HALFYEARLY
NUMBER(15,2)
ANNUALLY
NUMBER(15,2)
12. AgentCommission
Name
Null?
Type
----------------------------------------- -------- ---------------------------AGENTID
NUMBER(11)
AGENTNETAMOUNT
NUMBER(13,3)
13. AgentcommTx
Name
Null?
Type
----------------------------------------- -------- -----------------------AGENTCOMMTXID
NOT NULL
NUMBER(11)
AGENTID
NUMBER(11)
AGENTAMOUNT
NUMBER(13,2)
AGENTCOMM
NUMBER(13,2)
AGENTCOMMDATE
DATE
14. Custbonusdates
Name
Null?
Type
----------------------------------------- -------- ---------------------------CUSTPOLICYID
NUMBER(11)
PREVIOUSBONUSDATE
DATE
NEXTBONUSDATE
DATE
15. Custbonustx
Name
Null?
Type
----------------------------------------- -------- ---------------------------CUSTBONUSTXID
NOT NULL
NUMBER(22)
CUSTPOLICYID
NUMBER(11)
BONUSDATE
DATE
BONUS
NUMBER(12,2)
16. Branch
Name
Null?
Type
----------------------------------------- -------- -----------------------BRANCHID
NOT NULL
NUMBER(5)
BRANCHNAME
VARCHAR2(22)
LOCATION
VARCHAR2(22)
BRANCHDATE
DATE
PHONE
NUMBER(12)
STATE
VARCHAR2(22)
Circle or Bubble
It represents a process that transforms incoming data flow(s) into outgoing data
flow(s).
Open Rectangle
GANE
AND
SARSON NOTATION
DATA FLOW
DATA STRUCTURE
EXTERNAL ENTITY
OR
DATA LINK
PROCESS
DATA BASE
DATA FLOW
DATA STRUCTURE
EXTERNAL ENTITY
OR
DATA LINK
PROCESS
DATA BASE
Context level
Customers
customer
s
Manager
Managers
0. 0
Create Insurance
system
Chairman
Agents
Chairman
Agents
Login Info
Data Base
Chairman
User
Login
Process
Managers
Customer
s
Invalid
Chairaman
Agents
Registration of
Branch, Polices,
Branch Manager
Customers
Agents
Branch Managers
1.0
Create Insure
System
Registration of
Agents, Customers
Cal Interest,Bo
nus
1.0
Creative Insurance
System
1.0
Creative
Insurance
System
View
Chairman
Reports
View
Branch Manager
Reports
view
Reports
View
Reports
Customers
Agents
Registratio
n
Of Branch
Chairman
Login
Create
Insurance
System
Appoint of
Manager
Registration
of Policies
Reports
Registratio
n
Of Agents
Registration
of
Customers
Branch Managers
Login
Create
Insurance
System
Calculate
of Customer
Bonus
Calculate of
customer
Next
Premium
Agents
Commission
Reports
Registratio
n
Of Agents
Customers
Login
Registration
of
Customers
Create
Insurance
System
Calculate
of Customer
Bonus
Calculate of
customer
Next
Premium
Agents
Commission
Reports
4.4ENTITY-RELATIONSHIP DIAGRAMS
PURPOSE
Represent attributes.
Phone
BranchI
d
Branch
MgrNa
me
BMJoin
Date
Stat
e
Branch
Name
Branc
hNam
e
Branch
Location
Branch
MgrFat
herNa
me
Branch
Date
Age
Customer
Addr
BranchMgr
Custome
RegDate
CustId
BMQual
BMSe
x
BMAg
e
CustId
CustPoli
cyId
PolicyId
Sex
CustNa
me
Customer
Customer
FNmae
CustI
d
Policy
Date
CustQ
ual
Customer
Occuptio
n
Agent
Id
CustPolicies
Nomine
eName
Premiu
mType
Premiu
mAmout
nt
PolicyTer
m
Bonu
sPerio
d
PolicyAm
ount
PolicyId
Policy
Name
Policies
Bon
usR
ate
PolicyI
d
Policy
Id
Monthly
u
Quarterl
y
Premium
Amounts
PolicyFac
eAmount
PolicyI
nterest
PolicyDat
e
Halfye
arly
Annualy
Agent
Age
AgentAd
dress
Agents
RegDate
AgentId
Agent
Name
Agents
AgentFN
mae
Age
ntsS
ex
Agents
Id
Agents
CommT
xId
Agent
Id
AgentA
mount
Agents
CommTx
Agents
Comm
Agent
Id
Agents
Securit
y
Deposi
t
BranchM
geId
Agents
Comm
Date
4.5 UMLDIAGRAMS
INTRODUCTION
UML is a notation that resulted from the unification of Object
Modeling Technique and Object Oriented Software Technology .UML has been
designed for broad range of application.
Hence, it provides constructs for a broad range of systems and activities.
An Overview of UML in five notations
1.use case diagrams
Use cases are used during requirements elicitation and analysis To
represent the functionality of the system.Use cases focus on the behaviour of
the system from the external point of view.The actor are
Outside the boundary of the system,whereas the use cases are inside the
boundary of the system.
2.class diagrams
Policies Maintainance
Manager Registration
Chairman
Chairman
Branch Creation
Agents Registration
Customer Registration
Manager
Manager
Customer Premium Payment
Customer Bonus
Agent Commission
Policies Details
Agent
Agent
Manager Details
Policy Amounts
Bonus Dates
Premium Dates
Customer
Policies Details
Customer
drive of 1.44 MB and 14 inch Samsung color monitor suits the information
system operation.(A Printer is required for hard copy output).
RAM Capacity
--------
Hard Disk
--------
Floppy disk
--------
CD-ROM Drive
--------
Software Requirements:
One of the most difficult tasks is that, the selection of the software, once
system requirement is known is determining whether a particular software
package fits the requirements. After initial selection further security is needed to
determine the desirability of particular software compared with other candidates.
This section first summarizes the application requirement question and then
suggests more detailed comparisons.
Operating System
Browser
--
IE
Web/Application Server
--
Tomcat Server
Database
--
Oracle
Database Connectivity
--
JDBC
Java Technologies
--
Windows 98/NT/2000
--
Scripting Technology
5. System Testing
--
Java Script
TESTING
Testing is a process, which reveals errors in the program. It
is the major quality measure employed during software development.
During software development. During testing, the program is executed
with a set of test cases and the output of the program for the test cases is
evaluated to determine if the program is performing as it is expected to
perform.
In order to make sure that the system does not have
errors, the different levels of testing strategies that are applied at differing
phases of software development are:
1.
Unit Testing
Unit Testing is done on individual modules as they are
completed and become executable. It is confined only to the
designer's requirements.
Each module can be tested using the following two
strategies:
i)
input conditions that fully execute all functional requirements for the
program. This testing has been uses to find errors in the following
categories:
a) Incorrect or missing functions
b) Interface errors
c) Errors in data structure or external database access
d) Performance errors
e) Initialization and termination errors.
2.
Integrating Testing
Integration testing ensures that software and subsystems
work together as a whole. It tests the interface of all the modules to
make sure that the modules behave properly when integrated
together.
3.
System Testing
Involves in-house testing of the entire system before delivery
to the user. It's aim is to satisfy the user the system meets all
requirements of the client's specifications.
4.
Acceptance Testing
It is a pre-delivery testing in which entire system is tested at
client's site on real world data to find errors.
validation
The system has been tested and implemented successfully
and thus ensured that all the requirements as listed in the software
requirements specification are completely fulfilled. In case of erroneous
input corresponding error messages are displayed.
7. Technical Notes
Overview of Java
Java is loosely based on C++ syntax, and is menat to be Object-Oriented
Structure of java is midway between an interpreted and a compiled language .
java programs are compiled by the java compiler into Byte Codes which are
secure and portable across different platforms . these byte codes are essentially
instructions encapsulated in single type, to what is known as ajava virtual
machine (JVM) which resides instandard browser.
Jvm verifies these byte codes when downloaded by the browser for integrity.
Jvms available for almost all OS. JVM converts these byte codes into machine
specific instructions at runtime.
FEATURES OF JAVA
PARADIGM OF JAVA
Netscape
Internet Explorer
JAVA SCRIPT
Java script is a general purpose , prototype based , object oriented
scripting language developed jointly by sun and netscape and is meant for the
ADVANTAGE
1. java script can be used for client side application
2. java script provides means to contain multiform windows for
presentation of the web.
9. Conclusion
The web application is developed for to maintain the insurance policies. These
application is used CEO, Managers, Agents and customers. The CEO can be
maintain the branch, policies, manager and all the repots are handled. Manager
can be maintain the agents, customers, premium payments, agent commission
and reports are maintain.
The Agents are involved in the process of the Customer Policy registration
and the Commissions are based on the targets achieved by the Agents.
Apna life insurance System also maintains the database of the Branch
Managers who deals with the Agents which in turn deals with the Customers.
10. BIBLIOGRAPHY
ORACLE
Java 2, The Complete Reference
Ivan Bayross
Patrick Naughton
& Herbert Schildt
Jason Hunter
& William Crawford
Musciano
James Goodwill
Larne Pekowsky