Sids Project

8/7/2019 Sids Project

1/21

SHILLONG ENGINEERING ANDMANAGEMENT COLLEGE

JORABAT-793101

G. S. Road, Ri-Bhoi District (Meghalaya)Affiliated to

North-Eastern Hill University

SHILLONG

A Project Synopsis

On

Insurance Maintenance SystemFor

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.


2/21

Shillong Engineering and Management College.

Jorabat.

Title of the Project:

INSURANCE MAINTAIN SYSTEM ofING LIFEINSURANCE 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.


3/21

Tools to be used:

Software and hardware specification of machineused:

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 monitorMouse Normal

Keyboard Normal


4/21

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 developmentproject. In case the requirements are not clear ,e.g for a system thepurpose of this phase is to identify and document the exact requirementsfor the system. As never done before, many interactions are requiredbetween the user and the developer.

Identification of the need:

This is the first step for a system analyst, before developing software for anorganization. After discussing with the management of the organization, Ihave over come to the following conclusion regarding the need of theproject as;

1. Due to manual registration the system should maintain several registerto 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 canbe decrease with the help of the proposed system.


5/21

Information Requirement:

There are four strategies available for determining informationrequirement. 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 theinformation about the plan that a customer want to know from anAdvisor when an advisor meet the customer. For example there arethree types of plan like Unit Linked plan, one time investment planand Endowment plan.

Customer:The second one is CUSTOMER A customer can invest, acustomer can give premium against his plan after giving premiumthe customer get the policy.

Receipt:The third one is RECEIPT. In receipt module there are tworeceipts first one is First year premium receipt and second one isTop up or Renewal Receipt. A customer will get First year premiumreceipt after giving his first premium to the insurance company andwhen he will get the top up or Renewal Receipt when he will pay hissecond premium to the company.


6/21

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 plan details

Context Diagram

Or0-level DFD

Structure Chart:

Insurance

MaintanSystemCustomer Advisor


7/21

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.

Structure Chart

Data Flow Diagram:

INSURANCE MAINTAIN SYSTEM

PLAN CUSTOMER RECEIPT

Unit linked

Plan

Fixed deposit

PlanEndowment

Plan

Investment Premium Policy

First year

premium Receipt

Renewal

premium Rec


8/21

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

systems 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 aflowchart, 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 Get EnquiryCustomer Advisor

Plan Details

Process

1.0


9/21

Get plan details Give Response

Retrieved plan details Plan Details

Ask for investment plan details

Give Investment Details

Get Investment detailsRetrieved invest details

Invest Details

Update investment details

Customer submit document Document to advisor

Get Document

Document DetailsGive Document

Plan details

Give Premium Amount Update Premium Details

Update Premium Details

Premium

Details

Retrieved Premium Details

Getting the money Receipt Getting premium details

Premium collection Report

Enquiry for policy

Give policy to customer Advisor give policy Details

Policy issue details

Policy DetailsUpdate Policy Issue details

1st Level DFD

Entity Relationship Diagram:

Premium Pay

process

4.0

Money

Receipt

Process

5.0

Customer

document submit

process

3.0

Investment

Details

Process

2.0

Issuance of

Policy process

6.0


10/21

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 describea 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


11/21

______________________ Links attribute to entity sets and

entity sets to relationship sets.

Represent weak entity

1 M

CId

Customer

CNmCphno

Cadrs

Give

Typofdoc

Doc

o

CId


12/21

1

1

M

1 1 1

1

M

1

1

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.

Plnnm----------

-

Document

Colle

ct

Investment

Amntofinvs

tSassrd

Trmwsprem

Get

P

ay

Premium

Prempaydt

ePremamn

t

CNm

Policy

H

as

Plan

PlcyNo

CNm

Plcyissudt

e

Instlofprem

MtrtyDteSassrd

Modofpre

m

PlnnmTpofpl

n

Maxinvs

ttrm

Mininvsttrm

Bofpln Fde

Pa

y

Plnnm

----------

Plnn

m

-----------

Cid

--------

Cid

-----

-

Invsti

d

Plnnm

Document


13/21

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.

Diamonds, which show decisions that must be made.

Start

Is

Pla

n

Is

appl

y for

Plan Plan

Customer Customer

Is payPremiu

m Premium

Is

get

poli

cy

Policy


14/21

Yes No

No Yes

No Yes

No Yes

State Flow DiagramDatabase 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.

Stop


15/21

1. Name of the Table: Customer.

Field Name Data Type Length Key

CId Varchar 10 Primary key

CNm Varchar 30Cphno Bigint

Cadrs Varchar 50

2. Name of the Table: Document.


Docsrno Varchar 15 Primary key

Typofdoc varchar 20

Fdet Varchar 60

3. Name of the Table: Plan.


plnnm Varchar 20 Primary key

Tpofpln Varchar 10

Bofpln Varchar 140

Mininvsttrm Integer

Maxinvsttrm Integer

4. Name of the Table: Investment.


Invstid varchar 20 Primary key

plnnm Varchar 20 Foreign key

Sassrd Integer

Amntofinvst float

Trmwsprem float


16/21

5. Name of the Table: Premium.


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.


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 adata 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:


17/21

Field Name Source Data

Type

Description Key

CId Customer/policy/pemium Varchar Id of the

customer

Primary key/

foreign keyCNm 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

the document

Primary key

Typofdoc Document varchar Document

types of thecustomer

Fdet Document Varchar Family details

of the

customer

plnnm Plan/Investment/Premium Varchar Name of the

plan

Primary

key/Foreignkey

Tpofpln Plan Varchar Type of theplan

Bofpln Plan Varchar Benefit of the

plan

Mininvsttrm Plan int Minimum

term of

investment

Invstid Investment varchar Id of the

Investment

Primary key

Sassrd Investment int Sum Assured

of the plan

Amntofinvst Investment float Amount of Investment

Trmwsprem Investment float Term wise

premium ofthe plan


18/21

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

number

Primary key

Plcyissudte Policy Date Policy issuedate

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.


19/21

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 existingmanual system for days until the concerned becomes fully confident of the

new system.

Testing Procedure:

The system should always be tested thoroughly befo

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:


20/21

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 systems procedures operate to system specificationsand that the integrity of the vital data is maintained, performance of an acceptance

test is actually the users show. User motivation and knowledge are critical for the

successful performance of the system. Then a comprehensive test report is prepared

that indicates the systems tolerance, performance range, error rate and accuracy.


21/21

Conclusion:

An Insurance Maintain system is an important need for every people inthese days. Keeping track of the whole insurance maintain system is

certainly not an easy task if not as impossible one. Using the InsuranceMaintain system software is going to make the task of the user easier asthere is provision for both storing and retrieving information to and fromthe tables, which will provide the desired flexibility in report generation.But looking at the stiff competition going on the global IT sector today, nosoftware can be called a perfect one. One can never say with an air ofauthority that his/her software will never get outdated. So softwaresshould be designed in such a manner that there is scope for its upgradation without changing its basic infrastructure. Although the bestefforts would be put in to cover every aspect of the Insurance MaintainSystem, still due to the limited experience in software designing, someloop holes may creep into the software. But for time being, the proposedsystem is adequate to handle the Insurance Maintain System in a properway.

Date post:	08-Apr-2018
Category:	Documents
Upload:	shibendu-sharma
View:	218 times
Download:	0 times

Sids Project

Documents