Masters of Technology in Software Engineering

radiographerfictionΔιαχείριση Δεδομένων

31 Οκτ 2013 (πριν από 3 χρόνια και 11 μήνες)

78 εμφανίσεις


Masters of Technology in

Software Engineering




SG
4006



Enterprise Integration




CONTINUOUS
ASSESSMENT



Insurance System Revamp


L
ecturer:

Ouh Eng Lieh


Team
:

T5S

Name

Matriculation No.

LIM YONG BOON

A0065796L

LU ZHI XIAN

HT082186Y

NIE XIAO YI

HT082244Y

TAN ACHILLES ELI IGNACIO

HT082180E

WOO MENG CHEW

A0065935W



December 4, 2010

Ente
rp
r
ise Integration

Case Study: Insurance System Revamp

Page
1

of
17

Table of
C
ontents

s
1.

Introduction

................................
................................
................................
..............

3

2.

Business Analysis

................................
................................
................................
.......

4

2.1.

List of domains

................................
................................
...............................

4

2.2.

List of entities

................................
................................
................................

4

2.3.

List of tasks

................................
................................
................................
....

5

2.4.

List of interactions between entities

................................
................................

5

3.

Analysis & Modelling

................................
................................
................................
.

7

3.1.

Modelling the Business Process
................................
................................
.......

7

3.1.1.

Use Cases
................................
................................
............................

7

3.1.2.

Activity Diagrams

................................
................................
................

9

3.1.3.

Sequence Diagrams

................................
................................
.............

9

3.2.

Data Modelling
................................
................................
.............................

10

3.2.1.

Class Diagrams

................................
................................
..................

10

3.2.2.

Data Transformation Table

................................
................................

11

4.

Integration Architecture
................................
................................
...........................

12

4.1.

Overall Architecture

................................
................................
.....................

12

4.2.

Communication Models

................................
................................
................

12

4.3.

Integration Interfaces

................................
................................
...................

12

5.

Qualities of the Integration Architecture

................................
................................
...

13

5.1.

Scalability

................................
................................
................................
....

13

5.2.

Reusability

................................
................................
................................
...

13

5.3.

Performance

................................
................................
................................

13

5.4.

Maintainability

................................
................................
.............................

13

Ente
rp
r
ise Integration

Case Study: Insurance System Revamp

Page
2

of
17

5.5.

Availability

................................
................................
................................
...

14

5.6.

Security

................................
................................
................................
.......

14

6
Prototype

................................
................................
................................
....................

15

7
References

................................
................................
................................
..................

16


Ente
rp
r
ise Integration

Case Study: Insurance System Revamp

Page
3

of
17

1.


In
troduction

LionHeart Insurance Company (LHI)
envisions becoming

the leading insurance service
provider in Asia. To realize s
uch vision, the company plans on migrating

its legacy policy
system,
LegacyInsure
, into an open
-
standard

based system calle
d,
NewInsure
. The new
system aims to replace the legacy system in integrating various existing subsystems used by
the company while enhancing their productivity and competitiveness in the industry.


This report shall first evaluate the current business

pro
cess, environment
, challenges, and
the requirements of the NewInsure. Based on this assessment, an Integration Architecture
shall be presented to illu
strate the subsystems involved
and their communication

with

NewInsure
. An Integration Da
ta Model shall be
also proposed with

complete interface
definitions. The report shall then justify these recommendations by highlighting Qualities of
the Integration Architecture to address the challenges mentioned. Prototypes of some of the
interface described to the furth
er prove that the solution is viable and effective.

Ente
rp
r
ise Integration

Case Study: Insurance System Revamp

Page
4

of
17


2.

Business
Analysi
s

LionHeart Insurance Company

has four main departments to manage its business
operations. Each department has various subsystems that communicate with
LegacyInsure
.

2.1.

List of domains

2.1.1.

New
Business

2.1.2.

Self Servic
e

2.1.3.

Customer Service

2.1.4.

Accounting & Claims

2.2.

List of entities


New
Business

Self Service

Customer
Service

Accounting & Claims


NBSubmit

IVR

AgencyPortal

ConnectMe

QueryMgmt

OracleFin

Claims

Users

Agent

Agent,
Pol i cyHol der

Agent

Agent,
Pol i c
yHol der

CSO

System

Agent

Technology

C++

C

J2EE

J2EE

C

Oracl e

-

Environment

-

Uni x

-

-

Wi ndows

-

-

User Interface

Web
-
based

Peri phoni cs

Box

W
eb
-
based

Web
-
based

Web
-
based

-

-

Communication

Protocols

MQ

MQ

FTP

MQ

MQ

FTP

FTP

None

Middleware
Application
s
with
LegacyInsure

Screen
Scraping

Dialogue
Manager
(proprietary)

FTP Server

Screen
Scraping

Screen
Scraping

FTP Server

FTP Server

None



Ente
rp
r
ise Integration

Case Study: Insurance System Revamp

Page
5

of
17

2.3.

List of tasks

There are several tasks required from the system. However, all these can be
grouped into following mai
n tasks

2.3.1.

Proposal Submission

2.3.2.

Proposal
Inquiries

2.3.3.

User Validation

2.3.4.

Agent Inquiry

2.3.5.

Change PIN

2.3.6.

Payment Process

2.3.7.

Update Proposal


2.4.

List o
f interactions

between entities

2.4.1.

T
he
A
gent will submit the proposal through the NBSubmit system and the
details of the insurance p
lan will be sent to NewInsure system.

2.4.2.

T
he agent can enquire the detail of the insurance via NBSubmit system and the
request is forwarded to NewInsure system to retrieve the record
.

2.4.3.

T
he IVR system will send the login user information to NewInsure system for

authentication.

2.4.4.

T
he IVR allows the agent and policyholder to enquire the policy detail. The
NewInsure system will receive the inquiry request from IVR and send the result
back to IVR.

2.4.5.

T
he IVR system allows to change PIN.

2.4.6.

T
he agent will use AgencyPortal sy
stem to handle queries. The NewInsure
system will receive the inquiry request from AgencyPortal system and send the
result back to AgencyPortal system.

Ente
rp
r
ise Integration

Case Study: Insurance System Revamp

Page
6

of
17

2.4.7.

T
he policyholder can enquire the detail of policy insurance through ConnectMe
system. The NewInsure sys
tem will receive the
query

request from
ConnectMe
system and send the result back to
ConnectMe
system.

2.4.8.

T
he ConnectMe system allows the policyholder to submit proposal and the
details of the insurance plan will be sent to NewInsure system.

2.4.9.

T
he
C
ustomer
S
erv
ice
O
perator

(CSO)

uses QueryMgt system to handle the
queries. The NewInsure system will receive the inquiry request from QueryMgt
system and send the result back to QueryMgt system.

2.4.10.

T
h
e NewInsure system will send payment

records

to OracleFIN

after
the
pay
ments have been
proce
ssed


Ente
rp
r
ise Integration

Case Study: Insurance System Revamp

Page
7

of
17


3.

Analy
sis

& Model
l
ing

3.1.

Modelling the Business Process

3.1.1.

Use Case
s


Figure
1

Use Cases: Business Context Level 1

Ente
rp
r
ise Integration

Case Study: Insurance System Revamp

Page
8

of
17



Figure
2

UseCase Diagram: Detailed level

Ente
rp
r
ise Integration

Case Study: Insurance System Revamp

Page
9

of
17


3.1.2.

Activity Diagram
s


3.1.3.

Seq
uence Diagrams



Ente
rp
r
ise Integration

Case Study: Insurance System Revamp

Page
10

of
17


3.2.

Data Mode
l
ling

3.2.1.

Class Diagrams




Ente
rp
r
ise Integration

Case Study: Insurance System Revamp

Page
11

of
17

3.2.2.

Data Transformation Table

Ente
rp
r
ise Integration

Case Study: Insurance System Revamp

Page
12

of
17


4.

Integration Architecture

4.1.

Overall Architecture

4.2.

Communication Models

4.3.

Integration Interfaces

Ente
rp
r
ise Integration

Case Study: Insurance System Revamp

Page
13

of
17


5.

Qualities of the Integration Architecture

5.1.

Scalability



Platform
-
Independent
.
The pro
posed design offers a platform
-
independent
interface that allows any system, whether third party application or newly develop
app to be easily integrated regardless on the platform it

is using. As the company
continues to innovate new business processes, t
he newly introduced system can
easily plugin new systems off
-
the shelf or new systems.



Service
-
Oriented.

As new business functions are requested, the NewInsure can add
more services and expose them through the web interfaces. Subsystems can easily
access
these services through the exposed interface without affecting the existing
functions and processes.

5.2.

Reusability



Common Components
.

Some subsystems share



Pluggable Components.

5.3.

Performance



Improved
Speed.

Screen Scraping causes



High
Reliability
.
Screen Scra
ping methods are known to be unreliable. The use of
standard adapters

5.4.

Maintainability



Data Consistency
.

The transformation of all data to XML format shall ease the
readability of the information passed across different subsystems.



Data Efficiency.

The new

design reduces the amount data redundancy as the
defined data classes consolidates the data attributes needed for communication
among the subsystems.

Ente
rp
r
ise Integration

Case Study: Insurance System Revamp

Page
14

of
17

5.5.

Availability


5.6.

Security

Ente
rp
r
ise Integration

Case Study: Insurance System Revamp

Page
15

of
17


6
Prototype

[Provide screenshots of the prototype]

Ente
rp
r
ise Integration

Case Study: Insurance System Revamp

Page
16

of
17


7
References

Service
-
Centri
c Integration Architecture for Enterprise Software Systems (2009)
.

http://www.computing.dcu.ie/~cpahl/papers/JISE09.pdf


Applied Enterprise Integration Architecture. (June 2006)
http://jimcamerononline.com/index.php?option=com_content&task=view&id=21&Itemid=9


IBM InfoSphere Data Architect.

http://www
-
01.ibm.com/software/data/optim/data
-
architect/