ALLIANZ INSURANCE

COMPANY

TRAVEL INSURANCE

PROCESSING SYSTEM

DETAILED DESIGN DOCUMENT

TEAM-04
MODULE-01
CREATION OF POLICY
AND AGENT DATABASES
1
 TABLE OF CONTENTS

SNO TITLE PAGE

NO
1 HIGH LEVEL DESIGN DOCUMENT
2 LOW LEVEL DESIGN DOCUMENT
3 TEST STRATEGY

2
 HIGH LEVEL DESIGN DOCUMENT

INTRODUCTION:
THE MAIN PURPOSE OF THIS HIGH LEVEL DOCUMENT IS EXPLAINED IN THE
FOLLOWING POINTS:

 THIS DOCUMENT AIMS AT PROVIDING AN OVERALL DESCRIPTION OF THE ENTIRE

PROJECTAND HOW THE PROJECT IS BEING DIVIDED INTO VARIOUS MODULES.

THIS DOCUMENT CONTAINS THE FOLLOWING DETAILS:

 OVERALL PROJECT OVERVIEW

 PROJECT SCOPE

 FUNCTIONAL AND NON FUNCTIONAL REQUIREMENTS

 PROJECT ARCHITECTURE DESIGN

 FLOW CHART EXPLAINING THE MODULE

3
PROJECT OVERVIEW:

Alliance insurance company is a leading insurance company

In india.It offers various types of policies for its customers.Due to
large amount of data,the insurance company plans to automate its
processes.For this purpose it needs to store all the details in different
databases like

 POLICY DATABASE
 AGENT DATABASE
 CUSTOMER DATABASE
 HISTORY DATABASE

Hence the main aim of this project is to store the insurance policy
Details in the database system.

4
SCOPE OF THE PROJECT:
Generally in discussing about the scope of the project we need to verify
the following criteria:
 The data should be verified and validated and should be processed for
the valid records and report should be generated out of it.
 The respective modules to be created and tested accordingly to achieve
the final result of the business need.

CONSTRAINTS:
 The application should accept the applicant data which are provided
by Allianz
Insurance company.
 This application will accept and process the data sent on
MONTHLY,QUARTERLY AND YEARLY.
ASSUMPTIONS:
 The applicant data should be sent to the Allianz insurance company
only.
 This application will process only the valid customers.

5
DEPENDENCIES AND RISK:
 This application should be active for all calendar days.Any outage
on the external data system and third party verification system
should not impact this application.
This application should not go down even though if there are no
customer data to get processed on any calendar days.

6
PROCESS ARCHITECTURE DIAGRAM:

This diagram gives the various stages that takes place in

The module of creation of databases.This can be explained with the help of the
following activity diagram.

7
ACTIVITY DIAGRAM:
EXISTING POLICY
AND AGENT FILES

VERIFICATION ERROR
AND VALIDATION
FILE

CREATION OF
POLICY AND AGENT
DATABASES

SEPERATION AND
SORTING OF INPUT
FILES
8
NON FUNCTIONAL REQUIREMENTS:
There are various kinds of non functional requirements apart from the
Functional requirements that are required to execute our project some of non functional
criteria are as follows:
 PERFORMANCE REQUIREMENTS
 SAFETY REQUIREMENTS
 SECURITY REQUIREMENTS
 FUNCTIONALITY
 RELIABILITY
 USABILITY
 EFFICIENCY
 MAINTANAIBILITY
Hence all these characteristics have to be perfectly satisfied in order to
complete the successful execution of our project.
 Performance:
Since we handle a large amount of data,its recommended to use tapes rather
than disks.
 Safety and security:
There should always be a backup facility incase of any disruptions hence here we
have the backups of input and output files being stored in GDG.
 Functionality:
All the required functions including interoperability and security are checked.
 Reliability:
Maturity,fault tolerance and recoverability has to be provided.
 Usability:The automated system should be easy to understand,learn and operate .
9
LOW LEVEL DESIGN DOCUMENT
AIM:
The main purpose of this document is to give a detailed design about each and every
step that is processed in the module .Here we have various categories such as:

 TABLE LAYOUT OF POLICY AND AGENT DATABASES

 PROCEDURAL DESIGN
 FUNCTIONS AND ALGORITHMS
 CLASS DIAGRAM SHOWING THE RELATIONSHIPS BETWEEN DIFFERENT ENTITIES
INVOLVED IN CREATION OF POLICY AND AGENT DATABASES.

TABLE LAYOUT OF POLICY AND AGENT DATABASES:

POLICY FILE LAYOUT :
ATTRIBUTES
POLICY ID
POLICY CODE
POLICY NAME
TYPE OF POLICY
TERM
POLICY AMOUNT
10
AGENT FILE LAYOUT :
ATTRIBUTES
AGENT CODE
AGENT NAME
REGISTRATION NUMBER
STREET NAME
CITY
PINCODE
PHONENUMBER
COMMISION
ACCOUNT NUMBER
BANK NAME
BANK BRANCH

These are the details that are to be present in the databases after validating
and verification of certain constraints specified.Only valid details of policies
and agents will be updated into the database.

11
PROCEDURAL DESIGN:

VERIFICATION CREATION OF
AND POLICY AND
RAW DATA VALIDATION AGENT
SENT FROM BASED ON DATABASES
FILE BUSINESS
RULES

STORE THE
REJECTED STORE ALL THE
FILES INTO DETAILS INTO
ERROR FILE THE DASD FILES
WITH AND DATABASE
REASONS

12
FUNCTIONS AND ALGORITHMS:
 Create the insurance policy table and load the details of travel insurance policy file
And load the details of travel insurance policy file after validating the basic validations.

 Validations here refers to checking for format and mandatory values such as numeric
check.

 Once the validations are done the error records are being written into the error file
Along with the rejected reason.

 Error file has the same layout as that of the insurance policy file.

 Create the agent detail table and load the details from agent detail file .

 Here again we follow the same step as that of policy database wherein we perform
certain validations(check for format and mandatory values,numeric check)and write
the error records into the error file with the rejected reasons.

 Extract insurance policy file with type of policy as medical into a file and sort the file
in the order of type of policy,policy id and policy code

13
  These files will be internally referred by the processing divisions.
 Include the newly added policy detail in master policy VSAM KSDS file.

 Extract the required details and generate a separate report file for the above
applicants in the standard report format.

 Using page break logic the maximum number of lines to be displayed in a page are
12.

 Master policy VSAM file contains the details of all policies.

 All the backups of input and output files are being made in a GDG where GDG limit
is 10 versions.

14
CLASS DIAGRAM:
INPUT POLICY ERROR FILE
FILE NAME:STRING
VERIFICATION
NAME:CHAR
AND
ID:INT VALIDATION
NAME:CHAR
ID:INT

INPUT
AGENT FILE
NAME:CHAR POLICY AGENT
DATABASE DATA BASE
ID:INT
NAME:CHAR NAME:CHAR
ID:INT ID:INT

15
TEST STRATEGY:
This document consists of all the test cases that needs to be
satisfied for the project to be executed successfully.
TEST CASES VALIDATED NON VALIDATED

POLICY ID

16