EFFICIENT CLAIM SYSTEM

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

Bachelor of Technology In Computer Science and Engineering

By 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.

Table of Contents 1. Introduction

1.1. Methodology ...4 1.2. Purpose 1.3. Scope .....6 ....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 Perspective14 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

1. Introduction 1.1 Methodology

Rational Unified Process

Efficient Claim System

The 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

The different phases in RUP are

Inception
The 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.

Elaboration
The 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.

Construction
This phase is concerned with system design, programming and testing. Parts of the system are developed in parallel and integrated during this phase.

Transition
This 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 Scope
There 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 Abbreviations

ETS 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 companies. 4

Claimer/Insurer
A 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 Loss

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

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.

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. Its 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.

1.5

Tools Used

Application architecture JAVA, J2EE JAVA

Java 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.

J2EE
Java 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 WASCE

WebSphere 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 RAD

IBM 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.

Database platform DB2

DB2 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 Modeler

IBM 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
y y y y y

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

y y y y Java - www.sun.com Wikipedia - www.wikipedia.com Database Management Systems Navathe. Complete Reference - J2EE Keogh.

1.7
y y y

Technologies to be used
DB2: Relational Database Management System. RAD: Rational Application Developer. WASCE: Websphere Application Server Community Edition.

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: y y Registration for Users. Claimer/Insurer can be able to track or search for the claim status through his /her unique tracking number. y 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

2.2

Software Interface

Client 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 Internet Explorer - 6 Intel Pentium III or AMD -800 MHz ServerSide Processor RAD Intel Pentium III or AMD -800 MHz DB2 - 9.5 Intel Pentium III or AMD -800 MHz 256 MB 500 MB (Excluding Data Size) RAM 1 GB Disk Space 3.5 GB RAM 128 MB DisK Space 100 MB

10

Recommendation Requirements:

Client Side Processor Internet Explorer - 6 Intel Pentium III or AMD -800 MHzAll Intel or AMD - 1 GHZ Server Side Processor RAD IAll Intel or AMD - 2 GHZ DB2 - 9.5 IAll Intel or AMD - 2 GHZ 512 MB 500 MB (Excluding Data Size) RAM 2 GB Disk Space 3.5 GB RAM 256 MB DisK Space 100 MB

2.4
y y

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

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

login DeleteFNOL ModifyFNOL StatusChange

Receive Call Supervisor GenarateFNOL ViewReport

AssignFNOLToSurvey CSR ViewFNOL

RegisterClaim

Inspection User

SubmitFNOLReport

logout

Customer
Customer. 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 Policy Holder. CSR can only change the status of FNOL that is in open state. 13

FNOL Supervisor
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 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

User userId password login() logOut()

FNOLSupervisor ClaimRepresentator id : int name : string mobileNo : long registerClaim() registerFNOl() viewClaimDetails() viewFNOL() viewStatus() opname() id : int name : string mobile : long getFNOL() updateFNOL() deleteFNOL() updateFNOLstatus() assignFNOL() getFNOLReport()

Survyer id : int name : string mobile : long viewAssignedFNOL() generateReport() submitReport() ApproveFNOL() modifyReport()

CSRBusinessClass registerClaim() registerFNOL() viewFNOL() getLOB() viewStatus()

supervisorBAL getFNOL() updateFNOL() deleteFNOL() updateFNOLstatus() assignFNOL() getFNOLReport()

SurvyerBusiness viewAssignedFNOL() generateReport() approveFNOL() modifyReport() submitReport()

CliamDAL claimID : int polocyNumber : string claimedate : date polocyCompany : string fnolID : int registerClaim() getLobType() viewStatusregisterFNOL() viewStaus() logInBAL login() getRole()

FNOLDataAccess fnolId : int fnolName : string fnolLobType : int fnolAssignedId : int fnolCreatedDate : date fnolReportID : id registerFnol() getFnol() getAssignrdFnol() updateFnol() deleteFnol() assignFnol() getReport() approveFnol() getLobOfFnol() submitReport() viewReport() modifyReport()

LoginDal logIn() getRole()

15

2.8.1 Sequence Diagrams

FNOL Registration in Sequence Diagram

Claimant Claim Service Representative Calls registerClaim() getsLossInfo() registerFNOL() Claims FNOL

FNOL Assign in Sequence Diagram

CSR

FNOL Supervisor getFNOL()

FNOL

Inspection/Surv eyer

verifyFNOL() getAdditionalFNOLInfo() UpdatesFNOL() assignFNOL()

16

Inspector/Surveyor Sequence
Inspection/Surveyer getFNOLInfo() FNOL

FNOL Supervisor

verifyData() CollectsAdditionaInfo()

updatesFNOL()

17

Activity diagram
Staff head of the dept bursar staff

System Login

No

val id? Yes

Add New Cl aim

Edi t Cl ai m

Submi t Cl ai m

No com plete?

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

18

User Registration Activity

Initially 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

ReceiveCall

RegisterClaim CSR logIn

GenarateFNOL

Use Case SignIn Create FNOL Use Case SignIn Create FNOL

Description The CRS has to sign in order to. The CRS Register Claims and FNOL Description The CRS has to sign in order to. The CRS Register Claims and FNOL

22

3.1.2 FNOL Supervisor use-case report

ViewFNOL ModifyFNOL

DeleteFNOL Supervisor Login StatusChange

ViewReport AssignFNOLToSurevey

Use Case Log in View FNOL Update FNOL View Reports Assign FNOL to Surveyer Status Change

Description FNOL supervisor can log-in to the system in order to He can view all generated FNOLs He can update FNOL Details He can view all reports He can assign FNOL to a agency or suurvyer He can change the status of FNOL

23

3.1.3Inspection Officer Use case Report

Use Case Log-in View all Assigned FNOl Generate Report Submit Report

Description He can log-in to the system in order to He can view details of all assigned FNOl

He can generate all reports He can submit report to supervisor

24