EFFICIENT CLAIM SYSTEM

A major project report submitted in partial fulfillment of the for the award of the degree of

Bachelor of TechnologyIn

Computer Science and EngineeringBy

Ch. Goutham kumar (08641A0577)

B. Ravi kumar (09645A0504)

B. Rajesh (08641A0561)

M. Sruthi (08641A0527)

Under the guidance of

Asst. Prof. N. SATYAVATHI

Department of

Computer Science and Engineering

VAAGDEVI COLLEGE OF ENGINEERING

(Accredited by National Board of Accreditation , affiliated to JNTU, Hyderabad)

Bollikunta, Warangal - 506 005.

1

Table of Contents

1. Introduction

1.1. Methodology …………………………………………..………………………….4

1.2. Purpose ……………………………………………..………………………...6

1.3. Scope ……………………………………………..………………………..7

1.4. Definitions, Acronyms and abbreviations………………..………………………7

1.5. Tools used ……………………………………………….……………………..9

1.6. Preferences …………………………………………………..……………………11

1.7. Technologies to be used ……………………………………..……………………12

1.8. Overview ……………………………………………………..……………………13

2. Overall Descriptions

2.1. Product Perspective………………………………………………………………14

2.2. Software Interface………………………………………………………..……….15

2.3. Hardware Interface………………………………………………………..………16

2.4. Communication Interface…………………………………………………..……..17

2.5. Constraints ……………………………………………………………………..…17

2.6. ER Diagram …………………………………………………….………………...18

2.7. Use Case model survey …………………………………………………………...19

2.8. Class diagrams …………………………………………………….……………...21

2.8.1. Sequence Diagrams ……………………………………………………22

2.8.2. Activity Diagrams …………………………………………….…………25

2.9. Database Design …………………………………………………….……………..29

3. Specific Requirements

3.1 Use Case Reports …………………………………………………………………30

2

1. Introduction

1.1 MethodologyRational Unified Process

Efficient Claim SystemThe Rational Unified Process brings together elements from all of the generic process models,

supports iteration and illustrates good practice in specification and design. The RUP is normally

described from three perspectives:

A dynamic perspective, that shows the phases of the model over time.

A static perspective, that shows the process activities that are enacted.

A practice perspective, that suggests good practices to be used during the process.

Fig 1.1: Phases of Rational Unified Process

3

The different phases in RUP are

InceptionThe goal of the inception phase is to establish a business case for the system. Identifying

all external entities that will interact with the system and defining this interaction. This

information is used to assess the contribution of system to business.

ElaborationThe goals of the elaboration phase are to develop an understanding of the problem

domain, establish an architectural framework, develop project plan and identify key project risks.

ConstructionThis phase is concerned with system design, programming and testing. Parts of the

system are developed in parallel and integrated during this phase.

TransitionThis is the final phase of RUP and is concerned with moving the system from the

development community to the user community and making it work in real environment.

1.2 Purpose

Efficient Claim System- Claim servicing one the core insurance functions. A claimant expects

the settlement of the claim very promptly and fairly. This makes the claim processing directly

related to the profitability and reputation of the Insurance companies.

1.3 ScopeThere are four basic users - Admin, Claim Service Representative (CSR), FNOL Supervisor, and

Inspection/Survey Officer. All users have their own profiles. Admin can create users.

Customer/Claimer can search claim status basing on unique tracking number.

1.4 Definitions, Acronyms and AbbreviationsETS Efficient Claim System (Insurance domain) Claim servicing one the core insurance

functions. A claimant expects the settlement of the claim very promptly and fairly. This makes

the claim processing directly related to the profitability and reputation of the Insurance

4

companies.

Claimer/InsurerA Claimant who already has a Policy Number registered to a Insurance Company will lodge a

call to CSR to claim the Loss.

Claim Service Representative (CSR)A CSR sits in the call-centre and attends calls from the insured, claimants and agents. He

obtains information regarding the loss and registers the FNOL (First Notice of Loss) in the

system. A Claimant can be Policy Holder or relatives of the Policy Holder or Agents of the Policy

Holder. CSR can only change the status of FNOL that is in “open” state.

FNOL Supervisor

FNOL-First Notice of LossFNOL will have all the information that is required to register the Loss and will be

specific to LOB (Line of business). The FNOL Supervisor has the capacity to view, modify,

delete and verify the FNOLs. He can assign FNOL to Inspection/Survey team to inspect the

Accident claim or Theft claim or back to CSRs for further clarification.

Inspection Survey OfficerInspection/Survey user will go to the address as mentioned in the FNOL and will gather

all the details and verify if the Claim is valid or not. If not then the FNOL will be rejected.

WASCE

WebSphere Application Server Community Edition. It is an application server that

runs and supports J2EE and web service applications.

DB2

Database_2. A database management system that provides a flexible and efficient database

platform to maintain records of pictures, survey reports.

5

JSP

Java Server Pages. It is used to create dynamic web content.

J2EE

Java 2 Enterprise Edition. A programming platform which is a part of java platform for

developing and running distributed java.

UML

Unified Modeling Language is a standard language for writing software blueprints. The

UML may be used to visualize, specify, construct and document

XML

Extensible Markup Language is a text based format that let developers describe, deliver

and exchange structured data between a range of applications to client for display and

manipulation.

HTTP

Hypertext Transfer Protocol. It’s a service protocol.

RAD

Rational Application Developer is a development tool that helps to design web pages and

also helps to design the diagrams like ER, Database schema diagrams and to generate DDL.

6

1.5 Tools Used

Application architecture – JAVA, J2EE

JAVAJava is an object-oriented programming language developed by Sun Microsystems a

company best known for its high end UNIX workstations. Java language was designed to be

small, simple, and portable across platforms, operating systems, both at the source and at the

binary level, which means that Java programs (applet and application) can run on any machine

that has the Java virtual machine (JVM) installed.

J2EEJava Platform, Enterprise Edition or Java EE is a widely used platform for server

programming in the Java programming language. The Java platform (Enterprise Edition) differs

from the Java Standard Edition Platform (Java SE) in that it adds libraries which provide

functionality to deploy fault-tolerant, distributed, multi-tier Java software, based largely on

modular components running on an application server.

Web server – WASCEWebSphere Application Server Community Edition (from now on WASCE) is a free,

certified Java EE 5 server for building and managing Java applications. It is IBM's supported

distribution of Apache Geronimo that uses Tomcat for servlet container and Axis 2 for web

services. Over 15 WASCE developers are committers in the Apache Geronimo project.

Development tool –RADIBM Rational Application Developer for WebSphere Software (RAD) is an integrated

development environment (IDE), made by IBM's Rational Software division, for visually

designing, constructing, testing, and deploying Web services, portals, and Java (J2EE)

applications.

7

Database platform – DB2DB2 Database is the database management system that delivers a flexible and cost

effective database platform to build robust on demand business applications and supports the

J2EE and web services standards.

Design tool – Rational Software ModelerIBM Rational Software Modeler, (RSM) made by IBM's Rational Software division, is

a Unified Modeling Language UML 2.0-based visual modeling and design tool. Rational

Software Modeler is built on the Eclipse open-source software framework and includes

capabilities focused on visual modeling and model-driven development (MDD) with the UML

for creating resilient, thought-out applications and web services.

1.6 References

Object Oriented Modeling and Design with UML-Michael Blaha, James Rambaugh.

Software Engineering, Seventh Edition, Ian Sommerville.

IBM Red Books.

IBM TGMC Sample Synopsis.

IBM – www.ibm.in/developerworks .

Efficient Claim System Java - www.sun.com

Wikipedia - www.wikipedia.com

Database Management Systems – Navathe.

Complete Reference - J2EE – Keogh.

1.7 Technologies to be used

DB2: Relational Database Management System.

RAD: Rational Application Developer.

WASCE: Websphere Application Server Community Edition.

8

Rational Software Modeler.

1.8 Overview

Proposed System:

▪ Registered policy holders/relatives can make claims.

▪ Registration for Users.

▪ Insurance is claimed by policy holder/relative of registerd holder etc.,assured

insurance claim amount is to be handed over to claimer

Our Plan:

Registration for Users.

Claimer/Insurer can be able to track or search for the claim status through his /her unique

tracking number.

Claims can be done more easily with assistance and interaction with CSR(Claim Service

Representative)..,this makes insurer feel better and user friendly assistance.

2. Over All Description

2.1 Product Perspective

9

2.2 Software InterfaceClient on Internet

Web Browser, Operating System (any)

Client on Intranet

Web Browser, Operating System (any)

Web Server

WASCE, Operating System (any)

Data Base Server

DB2, Operating System (any)

Development End

RAD (J2EE, Java, Java Bean, Servlets, HTML, XML, AJAX), DB2, OS (Windows),

WebSphere(Web Server).

2.3 Hardware Interface

Minimum Requirements:

ClientSide

Processor RAM DisK Space

Internet Explorer - 6 Intel Pentium III or

AMD -800 MHz

128 MB 100 MB

ServerSide

Processor RAM Disk Space

RAD Intel Pentium III or

AMD -800 MHz

1 GB 3.5 GB

DB2 - 9.5 Intel Pentium III or

AMD -800 MHz

256 MB 500 MB

(Excluding Data

Size)

10

Recommendation Requirements:

Client Side

Processor RAM DisK Space

Internet Explorer - 6 Intel Pentium III or

AMD -800 MHzAll

Intel or AMD - 1 GHZ

256 MB 100 MB

Server Side

Processor RAM Disk Space

RAD IAll Intel or AMD - 2

GHZ

2 GB 3.5 GB

DB2 - 9.5 IAll Intel or AMD - 2

GHZ

512 MB 500 MB

(Excluding Data

Size)

2.4 Communication Interface Client (customer) on Internet will be using HTTP/HTTPS protocol.

Client (system user) on Internet will be using HTTP/HTTPS protocol.

2.5 Constraints GUI is only in English and region language.

Login and password is used for the identification of users.

Limited to HTTP/HTTPS.

This system is working for single server.

11

2.6 Architecture Design

APPLICATION LAYER BUSSINESS LAYER DATABASE LAYER

12

2.7 Use Case Model Survey

Receive Call

RegisterClaim

login

ModifyFNOLDeleteFNOL

StatusChange

ViewReport

AssignFNOLToSurvey

ViewFNOL

GenarateFNOL

SubmitFNOLReport

CSR

Inspection User

Supervisor

logout

CustomerCustomer. He can register themselves and search policies ,if interested can also buy policies.

Claim Service Representative (CSR)A CSR sits in the call-centre and attends calls from the insured, claimants and agents. He

obtains information regarding the loss and registers the FNOL (First Notice of Loss) in the

system. A Claimant can be Policy Holder or relatives of the Policy Holder or Agents of the

13

Policy Holder. CSR can only change the status of FNOL that is in “open” state.

FNOL SupervisorFNOL will have all the information that is required to register the Loss and will be

specific to LOB (Line of business)The FNOL Supervisor has the capacity to view, modify, delete

and verify the FNOLs. He can assign FNOL to Inspection/Survey team to inspect the Accident

claim or Theft claim or back to CSRs for further clarification.

Inspection Survey Officer Inspection/Survey user will go to the address as mentioned in the FNOL and will gather

all the details and verify if the Claim is valid or not. If not then the FNOL will be rejected.

14

2.8 Class Diagram

15

UseruserIdpassword

login()logO ut()

LoginDal

logIn()getRole()

logInB A L

login()getRole()

C liam DA Lc laim ID : intpolocyNum ber : s t ringc laim edate : datepolocyCom pany : s t ringfnolID : int

regis terC laim ()getLobType()viewS tatusregisterFNO L()viewS taus()

FNO LDataA ccessfnol Id : intfnolNam e : s t ringfnolLobType : intfnolA ss ignedId : intfnolCreatedDate : datefnolReportID : id

regis terFnol()getFnol()getA ssignrdFnol()updateFnol()deleteFnol()ass ignFnol()getR eport ()approveFnol()getLobO fFnol()subm itReport ()viewR eport()m odifyReport ()

CS RB us inessClass

regis terC laim ()regis terFNOL()viewFNO L()getLOB ()viewS tatus()

Claim Representatorid : intnam e : s t ringm obi leNo : long

regis terC laim ()regis terFN Ol()view Claim Details()view FNO L()view S tatus()opnam e()

supervisorB A L

getFNO L()updateFNOL()deleteFN OL()updateFNOLstatus()ass ignFNOL()getFNO LReport()

FNO LS upervisorid : intnam e : s t ringm obi le : long

getFNO L()updateFNOL()deleteFNOL()updateFNOLstatus ()ass ignFNOL()getFNO LReport()

S urvyerB us iness

viewA ss ignedFNO L()generateR eport()approveFN OL()m odifyR eport ()subm itR eport ()

S urvyerid : intnam e : s t ringm obile : long

view A ssignedFNO L()generateReport()subm itReport ()A pproveFNO L()m odifyReport ()

2.8.1 Sequence Diagrams FNOL Registration in Sequence Diagram

FNOL Assign in Sequence Diagram

16

Claim antClaim ant Claim S ervice Representat iveClaim S ervice Representat ive

Claim sClaim s FNO LFNO L

Calls

getsLossInfo()

regis terC laim ()

regis terFNO L()

CS RCS R FNO L S upervisor

FNO L S upervisor

FNO LFNO L Inspect ion/S urveyer

Inspect ion/S urveyer

getFNO L()

verifyFN O L()

ass ignFNO L()

getA ddit ionalFNO LInfo()

UpdatesFNO L()

Inspector/Surveyor Sequence

17

FNO L S upervisor

FNO L S upervisor

Inspect ion/S urveyer Inspect ion/S urveyer FNO LFNO L

getFNO LInfo()

verifyData()CollectsA ddit ionaInfo()

updatesFNO L()

Activity diagram Staff head of the dept bursar staff

System Login

No val id?

Yes

Add New Claim

Edi t Cl ai m

Submi t Cl ai m

No

complete?

Yes print and subm it Approve cl ai m Approve cl ai m

18

User Registration ActivityInitially user/customer is made to fill all mandatory fields filled in registration form.

Once the user clicks submit, the user name is verified. If the user name is already present, then

the user is again taken back, so that he can change the user name. If the user name is not present

then it checks for password and remaining mandatory fields. If any of the mandatory field is left

empty or filled incorrect, then the user is informed to enter the correct values. Once all these

verifications are succeeded, then the registration is done.

CSR Claim Registration Activity

A CSR sits in the call-centre and attends calls from the insured, claimants and agents. He

obtains information regarding the loss and registers the FNOL (First Notice of Loss) in the

system. A Claimant can be Policy Holder or relatives of the Policy Holder or Agents of the

Policy Holder. CSR can only change the status of FNOL that is in “open” state. After successful

log in Claim Service Representative note down all the above claims, FNOL online.

FNOL Maintaining Activity

FNOL will have all the information that is required to register the Loss and will be

specific to LOB (Line of business). The FNOL Supervisor has the capacity to view, modify,

delete and verify the FNOLs. He can assign FNOL to Inspection/Survey team to inspect the

Accident claim or Theft claim or back to CSRs for further clarification.

Inspection Survey and Approve/rejecting FNOL Activity Inspection/Survey user will go to the address as mentioned in the FNOL and will gather all

the details and verify if the Claim is valid or not. If not then the FNOL will be rejected

19

2.9 Database Design

2.9.1 ER Diagram

20

2.9.2 Database Diagram

21

3. Specific Requirements

3.1 Use Case Reports

3.1.1 Claim Service Representative use-case report

Use Case Description

SignIn The CRS has to sign in order to.

Create FNOL The CRS Register Claims and FNOL

Use Case Description

SignIn The CRS has to sign in order to.

Create FNOL The CRS Register Claims and FNOL

22

CS R

ReceiveCall

Regis terC laim

logIn

G enarateFNO L

3.1.2 FNOL Supervisor use-case report

Use Case Description

Log in FNOL supervisor can log-in to the system in order to

View FNOL He can view all generated FNOLs

Update FNOL He can update FNOL Details

View Reports He can view all reports

Assign FNOL to Surveyer He can assign FNOL to a agency or suurvyer

Status Change He can change the status of FNOL

23

S upervisor

V iewFNOL

M odifyFNOL

DeleteFNOL

S tatusChange

V iewReport

Login

A ss ignFNOLToS urevey

3.1.3Inspection Officer Use case Report

Use Case Description

Log-in He can log-in to the system in order to

View all Assigned

FNOl

He can view details of all assigned FNOl

Generate Report He can generate all reports

Submit Report He can submit report to supervisor

24