SHILLONG ENGINEERING AND
MANAGEMENT COLLEGE
JORABAT-793101
G. S. Road, Ri-Bhoi District (Meghalaya)
Affiliated to
North-Eastern Hill University
SHILLONG
A Project Synopsis
On
“Insurance Maintenance System”
For
“ING Life Insurance Company Ltd., Guwahati”
Submitted By:-
Shibendu Sharma.
Roll No.: CS-48/07.
Regd. No.: 9138 Year- 2007/08.
Branch: Computer Science and Engineering.
Course: Bachelor of Technology.
Submitted To:-
Ms. Shilpi Rajkhowa.
Computer Science and Engineering Department.
Shillong Engineering and Management College.
Jorabat.
Title of the Project:
“INSURANCE MAINTAIN SYSTEM” of “ING LIFE
INSURANCE” Guwahati.
Introduction:
ING Guwahati branch had started in the month of march 2006 with a man
power of six sales managers and one branch manager. Within a month it
furth.er got extended to 12 sales manager and one branch head. Presently
ING guwahati has 2 branch headed by Mr. Partha Sarathi Dey as senior
Branch manager and Mrs. Juri Baruah as agency manager with a team of 20
sales manager, 3 customer service executives and one training manager.
Objectives of the Project:
• Store data with minimal redundancy.
• To fasten up the data processing speed.
• Search record in a minimal time.
• Maintain integrity of the data.
Tools to be used:
Software and hardware specification of machine
used:
Software:
Operating System Windows 7.
Front End VB.Net
Back End My SQL Server.
Hardware:
Processor Intel Core-i3.
Hard Disk 320 GB.
RAM 3 GB.
Monitor 14” LED monitor
Mouse Normal
Keyboard Normal
Printer Inkjet printer.
Minimum Software and hardware to run the project:
Software:
Operating System Any windows based operating system.
Front End VB.Net
Back End My SQL Server.
Hardware:
Processor Pentium IV or above.
Hard Disk 80 GB or above.
RAM 512 MB or above.
Monitor 15 inch normal monitor
Mouse Normal
Keyboard Normal
Objectives of the Proposed System:
1. Retrieve required information quickly and efficiently.
2. Provide latest and updated information.
3. Provide appropriate managerial reports at all levels according to the
needs.
4. Store data with minimum redundancy.
Advantages of the Proposed System:
1. Searching will be faster.
2. Data consistency will be eliminated.
3. Latest information can be obtained if the files are update properly.
Requirement Analysis:
Requirement analysis is usually the first phase of software development
project. In case the requirements are not clear ,e.g for a system the
purpose of this phase is to identify and document the exact requirements
for the system. As never done before, many interactions are required
between the user and the developer.
Identification of the need:
This is the first step for a system analyst, before developing software for an
organization. After discussing with the management of the organization, I
have over come to the following conclusion regarding the need of the
project as;
1. Due to manual registration the system should maintain several register
to keep track of the registration process. It is very time-consuming.
2. To retrieve any information of a reporter such as address, identity, etc
needs a fair amount of time. The retrieval time of this information can
be decrease with the help of the proposed system.
Information Requirement:
There are four strategies available for determining information
requirement. They are as follows:
• Asking(interview)
• Deriving from the existing information system.
• Review of written documents.
• Synthesizing from the characteristics.
Module Description:
In INSURANCE MAINTAIN SYSTEM there are three types of module.
They are Plan, Customer and Receipt.
• Plan: The first module is PLAN. In plan module have all the
information about the plan that a customer want to know from an
Advisor when an advisor meet the customer. For example there are
three types of plan like Unit Linked plan, one time investment plan
and Endowment plan.
• Customer: The second one is CUSTOMER A customer can invest, a
customer can give premium against his plan after giving premium
the customer get the policy.
• Receipt: The third one is RECEIPT. In receipt module there are two
receipts first one is First year premium receipt and second one is
Top up or Renewal Receipt. A customer will get First year premium
receipt after giving his first premium to the insurance company and
when he will get the top up or Renewal Receipt when he will pay his
second premium to the company.
Context Diagram:
Context diagrams are related to Data Flow Diagram, and show the interactions
between a system and other actors with which the system is designed to interface.
Context diagrams can be helpful in understanding the context which the system will
be part of.
Enquiry for plan Get enquiry details
Insurance
Maintan
Customer System Advisor
Get plan details Response against the request
Context Diagram
Or
0-level DFD
Structure Chart:
A structure chart is a top-down modular design tool, constructed of squares
representing the different modules in the system, and lines that connect
them. The lines represent the connection and or ownership between activities
and sub activities as they are used in organization charts.
INSURANCE MAINTAIN SYSTEM
PLAN CUSTOMER RECEIPT
Unit linked Fixed deposit Endowment First year Renewal
Plan Plan Plan premium Receipt premium Receipt
Investment Premium Policy
Structure Chart
Data Flow Diagram:
A data-flow diagram (DFD) is a graphical representation of the "flow" of data
through an information system. DFDs are an important technique for modeling a
system’s high-level detail by showing how input data is transformed to output
results through a sequence of functional transformations. A DFD provides no
information about the timing or ordering of processes, or about whether processes
will operate in sequence or in parallel. It is therefore quite different from a
flowchart, which shows the flow of control through an algorithm.
DFDs consist of four components. They are Entities, Processes, Data stores, and
Data flows.
The symbols are as follows:
Symbol Meaning
Represent entity set.
Represent the data stores
Represent process
Represent the data flow
Enquiry for plan Plan Details Get Enquiry
Customer Process Advisor
1.0
Get plan details Give Response
Retrieved plan details Plan Details
Ask for investment Investment plan details
Details Give Investment Details
Process
Get Investment details 2.0
Retrieved invest details
Invest Details
Update investment details
Customer submit document Customer Document to advisor
document submit
process Get Document
3.0 Document Details
Give Document
Plan details
Give Premium Amount Premium Pay Update Premium Details
process
4.0
Update Premium Details
Premium
Details
Retrieved Premium Details
Money
Getting the money Receipt Receipt Getting premium details
Process
5.0
Premium collection Report
Enquiry for policy Issuance of enquiry to the advisor for policy
Policy process
Give policy to customer 6.0 Advisor give policy Details
Policy issue details
Policy Details
Update Policy Issue details
1st Level DFD
Entity Relationship Diagram:
Entity- Relationship (E-R) diagram represents real world situation using
concepts, which are commonly used by people. In E-R diagram the logical structure
of the data is captured by indicating the grouping of data into entities. The entity is
the most basic concept in the E-R diagram that represents important objectives in
the real application. An entity is a collection of similar entities. An attribute describe
a property associated with entities.
An Entity can appear in:
• One to One relationships.
• One to Many relationships.
• Many to One relationships.
• Many to Many relationships.
The symbols of E-R diagram are as follows:
Symbol Meaning
Entity set
Relationship set
Attributes
Key Attributes
Cardinality
______________________ Links attribute to entity sets and
entity sets to relationship sets.
Represent weak entity
Typofdoc
Cphno Cadrs
CId CNm CId
Docsrn
o
1 Give M
Customer
Pln 1
m n
1 Plnnm Document
Tpofpl Document
G
et n
M
Colle
ct
Bofpln Fdet
Plan
1 1 1 Mininvsttrm
P
ay
Maxinvs
ttrm
Investment Invsti
d
Prempaydt
e
Trmwsprem Premamn
t
Plnnm
---------- Cid
- Amntofinvs Sassrd -------
t -
Premium
1 Plnnm
-----------
Instlofprem H M -
Plnn as
Pa
m PlcyNo Modofpre
y
------- m CNm
---- 1
Policy 1
CNm
Cid
Plcyissudt ------- Sassrd MtrtyDte
e -
ER_Diagram
State Flow Diagram:
State Flow Diagram is also known as Flow Chart Diagram. A Data Flow
diagram can be used to Define and analyze processes, Build a step-by-step picture of
the process for analysis, discussion, or communication, and Define, standardize or
find areas for improvement in a process.
Data Flow Diagram are made up of three main types of symbol:
• Circles, which signify the start or end of a process;
• Rectangles, which show instructions or actions.
Start
• Diamonds, which show decisions that must be made.
Is
Pla
n
Plan Plan
Is
appl Customer Customer
y for
Is pay
Premiu Premium
m
Is
get
poli Policy
cy
Yes No
No Yes
No Yes
No Yes
Stop
State Flow Diagram
Database Structure:
Database structure is the process of producing a detailed data model of a
database. This logical data model contains all the needed logical and physical design
choices and physical storage parameters needed to generate a design in a Data
definition language which can then be used to create a database.
1. Name of the Table: Customer.
Field Name Data Type Length Key
CId Varchar 10 Primary key
CNm Varchar 30
Cphno Bigint
Cadrs Varchar 50
2. Name of the Table: Document.
Field Name Data Type Length Key
Docsrno Varchar 15 Primary key
Typofdoc varchar 20
Fdet Varchar 60
3. Name of the Table: Plan.
Field Name Data Type Length Key
plnnm Varchar 20 Primary key
Tpofpln Varchar 10
Bofpln Varchar 140
Mininvsttrm Integer
Maxinvsttrm Integer
4. Name of the Table: Investment.
Field Name Data Type Length Key
Invstid varchar 20 Primary key
plnnm Varchar 20 Foreign key
Sassrd Integer
Amntofinvst float
Trmwsprem float
5. Name of the Table: Premium.
Field Name Data Type Length Key
plnnm varchar 20 Foreign key
Prempaydte Date
Premamnt float
CNm Varchar 30
Modofprem Varchar 20
CId Varchar 20 Foreign key
6. Name of the Table: Policy.
Field Name Data Type Length Key
PlcyNo Integer 10 Primary key
Plcyissudte Date
CNm Varchar 30
Instlofprem float
MtrtyDte Date
Sassrd float
plnnm Varchar 20 Foreign key
Cid Varchar 20 Foreign key
Data Dictionary:
A data dictionary is a collection of descriptions of the data objects or items in a
data model for the benefit of programmers and others who need to refer to them.
A data dictionary has many advantages. The most obvious is documentation; it
is a valuable reference in any organization. Another advantage is improving analyst
user communication by establishing consistent definition of various elements, teams
and procedures. Also data dictionary is an important step in building database.
Data Dictionary of “Insurance Maintain System”:
Field Name Source Data Description Key
Type
CId Customer/policy/pemium Varchar Id of the Primary key/
customer foreign key
CNm Customer Varchar Name of the
customer
Cphno Customer Bigint Phone number
of the
customer
Cadrs Customer Varchar Address of the
customer
Docsrno Document Varchar Serial no of Primary key
the document
Typofdoc Document varchar Document
types of the
customer
Fdet Document Varchar Family details
of the
customer
plnnm Plan/Investment/Premium Varchar Name of the Primary
plan key/Foreign
key
Tpofpln Plan Varchar Type of the
plan
Bofpln Plan Varchar Benefit of the
plan
Mininvsttrm Plan int Minimum
term of
investment
Invstid Investment varchar Id of the Primary key
Investment
Sassrd Investment int Sum Assured
of the plan
Amntofinvst Investment float Amount of
Investment
Trmwsprem Investment float Term wise
premium of
the plan
Prempadte Premium Date Premium Pay
Date
Premamnt Premium float Amount of the
plan
Modofprem Premium Varchar Mode of the
premium pay
PlcyNo Policy Int Policy Primary key
number
Plcyissudte Policy Date Policy issue
date
Instlofprem Policy float Installment of
the premium
MtrtyDte Policy Date Date of
Maturity
System Implementation:
A crucial phase in the system development life cycle is the successful
implementation of the system design. Implementation simply means the
system design into operation. This involves installing of hardware, terminal
and also training the operation staff.
There are three main types of implementation:
• Implementation of a computer system to replace the manual system.
• Implementation of a new computer system to replace an existing one.
• Implementation of a modified application to replace an existing one.
After a through testing of the different aspects of the system, the system is
ready for implementation. The system is to run in a parallel with existing
manual system for days until the concerned becomes fully confident of the
new system.
Testing Procedure:
The system should always be tested thoroughly before
implementation of it as regard to the individual programs, the system as
a whole, user acceptance etc. This is because implementing a new
system is a major job that requires a lot of man-hour and other
resources. So an error not detected before implementation may cost a
lot. Effectively testing early in the process translates directly into long
term cost saving from a reduced number of errors. The purpose of the
system testing is to consider all the likely variations to which it will be
subjected and then push the system to its limits. It is a tedious but
necessary step in system development.
The different types of testing techniques that are used during the development of the
system under consideration are as follows:
Module Testing:
Module testing must be carried out during the programming stage itself. Here
individual program testing must be carried out during the coding stage itself and
the required changes are to be made on the module to ensure the smooth and
satisfactory execution of the module in the form of an individual program and the
generation of the output in the required form.
String Testing:
Programs are invariably related to one another and interact in a total system. Each
program is tested to see whether it conforms to related programs in the system.
Each portion of the system is tested against the entire module with both test and live
data before the entire system is ready to tested.
Unit Testing:
Unit testing is changes made in an existing or a new program. It is necessary for the
verification of the code that would be produce during the code phase. It is mainly to
test the internal logic of the module.
Integration Testing:
In integration testing, many unit tested modules are combined into sub systems,
which would be then tested. The objective if this testing is to see if the modules can
be integrated properly. That is, the prime emphasis is on testing the interfaces
between the modules.
System Testing:
The purpose of system testing is to identify and correct errors in the system. As
important as this phase is, it is one that is frequently compromised. Typically the
project is behind schedule or the user is easier to go directly to conversion. In system
testing performance and acceptance standards are developed. Substandard
performance or service interruptions that result in system failure are checked
during the test.
Output Testing:
No system could be useful if it does not produce required format. It includes asking
the user about the required format of the output that would be displayed on the
screen or in a printed form.
User Acceptance Testing:
An acceptance test has the objective selling the user on the validity and reliability of
the system. It verifies that the system’s procedures operate to system specifications
and that the integrity of the vital data is maintained, performance of an acceptance
test is actually the user’s show. User motivation and knowledge are critical for the
successful performance of the system. Then a comprehensive test report is prepared
that indicates the system’s tolerance, performance range, error rate and accuracy.
Conclusion:
An Insurance Maintain system is an important need for every people in
these days. Keeping track of the whole insurance maintain system is
certainly not an easy task if not as impossible one. Using the Insurance
Maintain system software is going to make the task of the user easier as
there is provision for both storing and retrieving information to and from
the tables, which will provide the desired flexibility in report generation.
But looking at the stiff competition going on the global IT sector today, no
software can be called a perfect one. One can never say with an air of
authority that his/her software will never get outdated. So software’s
should be designed in such a manner that there is scope for its up
gradation without changing its basic infrastructure. Although the best
efforts would be put in to cover every aspect of the Insurance Maintain
System, still due to the limited experience in software designing, some
loop holes may creep into the software. But for time being, the proposed
system is adequate to handle the Insurance Maintain System in a proper
way.
