Data Centralization Over Network Application For Insurance Services

ABSTRACT

This work is on data centralization over networks which aimed at the centralization of data in different platforms. The data, which are based in different platforms, can be centralized in a unique server. The main peculiarity of the data centralization over networks is that the clients can use different platforms and databases. Data centralization over networks can be used to synchronize data in different databases such as SQL. ORACLE, MYSQL, ACCESS, etc. It can be used as a backup tool. Data-CON aims to develop client and server tools to centralize over various networks. Data centralization over networks can be used to centralize dates in both Internet and intranet, and it can be used to synchronize data between different network points. Data centralization over networks supports the communication between the clients in different platforms. It is also having some chat application. It allows both online and off-line communication. Data centralization over networks can be used as a backup tool for taking file backup from network, Internet and local machine. Exiles, which are created in monitored folders, are copied over the network to the central folder, which can be used as backup folder or central storage.

 

 

TABLE OF CONTENTS

Title page

Certification

Dedication

Acknowledgement

Abstract

Table of Content

CHAPTER ONE: GENERAL INTRODUCTION

1.1      Introduction

1.2      Statement of the Problem

1.3      Aim and Objectives

1.4      Significance of the Study

1.5      Scope and Limitation

1.6      Organization of the Report

1.7      Definition of Term

LITERATURE CHAPTER TWO: LITERATURE REVIEW

2.1      The Evolution from Local to the Central Tape Backup

2.2      The Emergence of Disk-Based Backup

2.3      How Wide -Area Data Service Accelerate Wan Backup

2.3.1  Data Streamling Eliminate Redundant Byte from Transfers

2.3.2  Transport Streamling Eliminate Transport Protocol Inefficiencies

2.3.3  Application Streamline Optimizes Application Wan Performance

2.3.4  Management Streamline Enables Transparent Deployment and Centralized Management

CHAPTER THREE: METHODOLOGY AND ANALYSIS OF THE EXISTING SYSTEM

3.1      Research Method

3.2      Description of Current System

3.3      Problems of the Existing System

3.4      Description of Proposed System

3.5      Advantages of the Proposed System

3.6      Design and Implementation Methodologies

CHAPTER FOUR: DESIGN AND IMPLEMENTATION OF THE SYSTEM

4.1      Design of the System

4.1.1  Output Design

4.1.2  Input Design

4.1.3  File Design/Database Design

4.1.4  Procedure Design

4.2      System Implementation

4.2.1 Choice of Programming Language

4.2.2  Hardware Support

4.2.3  Software Support

4.2.4 Implementation Techniques used in Detail

4.3      System Documentation

4.3.1  Program Documentation

4.3.2  Operating the System

4.3.3  Maintaining the System

CHAPTER FIVE: SUMMARY, CONCLUSION AND RECOMMENDATION

5.1      Summary

5.2      Experience Gained

5.3      Problem Encountered

5.4      Conclusion

5.5      Recommendation

REFERENCES

Appendix

  1. System Flowchart
  2. Program Flowchart
  3. Source Program Listing
  4. Computer Output

 

CHAPTER ONE

                                                           GENERAL INTRODUCTION

1.1      INTRODUCTION

According to Kampfner (2019), a centralized database is a database that is located, stored, and maintained in a single location. This location is most often a central computer or database system. This study was carried out due to the need to be close to customers, manufacturing facilities and specialized labour have required organizations to extend the traditional concept of “headquarters” to offices and factories hundreds or even thousands of miles away (Kampfner, 2019). However, along with the opportunities that come with workforce globalization; come the realities of dealing with data that sprawls across the organization. Whether the data is at the Munich branch or at HQ in New York, it is equally susceptible to loss, requiring that data recovery and security plans apply to all parts of the organization, regardless of location (Venkatraman, 2011).

To protect company data and ensure its availability to users, IT organizations have been conflicted between two back up approaches. The first approach, local tape backup, requires that tape libraries be present wherever there are servers in racks (David, 2010).

Local area network (LAN) access to the servers gives administrators fast data backup and recovery. The newer approach, centralized backup, puts high-density tape libraries in one location to which data from servers around the world is backed up (Shannon et al., 2012).

While centralized backup requires less hardware, reduces administration time, and solves the security problem associated with loose tape media, it can introduce greater bandwidth consumption and longer backup/restore windows. Because of these issues, centralized backup has been a leap some managers have not been willing to make. With the right wide-area data services (WDS) technology, a more scalable and secure data protection model can be implemented without the expense of an expanded wide area network (WAN). WDS is a superset of several network acceleration categories, including data reduction and compression as well as protocol and application optimization (Shannon et al., 2012). WDS can eliminate the bandwidth and time constraints that stall many centralized backup deployments and are the primary enabler of many technology consolidation projects.

 

1.2      STATEMENT OF PROBLEM

The existing system that was in place was operating on individual database system (i.e. each system has its own database) which made it vulnerable to corrupt practices and have a lot of setbacks among which:

  1. Getting required data and information needed takes time,
  2. In an organization, it is not easy to get an information about something unless you go to the system it is stored no matter how much urgent it is,

iii.        It is cost ineffective in the sense that, substantial large amount of money will be needed to set up such system, since each system has to be catered for etc.

1.3      AIM AND OBJECTIVES

This study is aimed at producing a system that will serve as repository for all other systems connected to it, whereby they will be able to add, edit and query the database whenever the need arise.

Objectives of this system are:

  1. To maximize data integrity and minimized data redundancy, as the single storing place of all the data also implies that a given set of data only has one primary record. This aids in the maintaining of data as accurate and as consistent as possible and enhances data reliability.
  2. To develop a central server that maintains, manages and controls the activities of all other systems.
  3. To develop a system that will reassure data security, integrity and reliability.

iii.        To develop a system that will be cost effective compared to individual database system.

  1. To enable easy access to any required data and information within a little period of time.

 

1.4      SCOPE AND LIMITATIONS

The scope of this system covers a wide range in term of producing a centralized database for computational data and information; it operates on a local area network whereby data centralization will only be available for systems that are connected to the network. It is currently used for systems that are connected together using local area network.

The limitation of this system is only based on the fact that it requires professionalism or technical skills like basic knowledge of networking, computer awareness etc. It would pose a great headache for a person trying to use the system and unable to use it because of lack of communication between the systems due to incorrect configurations and or technical issue or fault on the hardware component of the system.

1.5      SIGNIFICANCE OF THE STUDY

            This study will provide a better data preservation than other types of databases due to often-included fault-tolerant setup

The system will serve as a generally bigger data security, as the single data storage location implies only a one possible place from which the database can be attacked and sets of data can be stolen or tampered with.

This project helps in creating a central system where all data will be stored and accessed when needed by making use of local area network connection. Example, in an organization where there are several client computers and one server, this system will provide a means of storing all their data and transaction works on the server alone to enable security and ease of access.

 

1.6      ORGANIZATION OF REPORT

Majority of this project will contain all the necessary information needed to carry out the proposed task.

Chapter one contains general introduction, aim and objective, significance of the study, methodology, scope and limitation, organization of the report and definition of technical / operation terms.

Chapter two deals with the literature review, it reviews related topic to the project, discussion of related aspect of the project topic relative to computer technology.

Chapter three deals with analysis of the system which include the data collection method employed, the description of the existing system and its problems and the description of the proposed system and possible advantages it will provide the will solve problems encountered in the existing manual system.

While chapter four deals with the design, implementation and the description of the proposed system. It covers description of the output design, input design, database design and procedure design. The implementation techniques used, the programming language used in developing the new system and system requirements for running the system. And also talks about the program documentation as well user documentation.

Lastly chapter five presents a brief summary of the work done, experience gained and problems encountered in the course of the project, conclusion and recommendation. Other appendices included after the references used are; algorithm, system flowchart, program flowchart, program source listing and generated computer output.

 

1.7      DEFINITIONS OF TERM

NETWORK: This comprises of two or more devices (computer, printer etc connected together using a particular connection protocol with the aim of sharing resources.

LAN: Local Area Network this is a communication network that serves user within a confined geographical area or a restricted locally such as a building or campus.

LAN CABLE: This is the cable usually called CAT5, RJ45 that is modified in order to create connection between 2 systems for ease of data communication and transmission.

SERVER: A computer that provides client stations with access to files and printers as shared resources to a computer network.

BACKUP:  A copy of a file or directory on a separate storage device

Hardware: the mechanical, magnetic, electronic, and electrical components making up a computer system.

WAN: Wide Area Network is a network that covers a broad area (i.e., any telecommunications network that links across metropolitan, regional, national or international boundaries) using leased telecommunication lines.

OPTIMIZATION: The act of rendering optimal.

PROTECTION: A covering that is intends to protect from damage or injury.

WDS:Wireless Distribution System is a system enabling the wireless interconnection of access points in an IEEE 802.11 network. It allows a wireless network to be expanded using multiple access points without the traditional requirement for a wired backbone to link them.

BANDWIDTH: A data transmission rate; the maximum amount of information (bits/second) that can be transmitted along a channel.

APA

Data Centralization Over Network Application For Insurance Services. (n.d.). UniTopics. https://www.unitopics.com/project/material/data-centralization-over-network-application-for-insurance-services/

MLA

“Data Centralization Over Network Application For Insurance Services.” UniTopics, https://www.unitopics.com/project/material/data-centralization-over-network-application-for-insurance-services/. Accessed 22 November 2024.

Chicago

“Data Centralization Over Network Application For Insurance Services.” UniTopics, Accessed November 22, 2024. https://www.unitopics.com/project/material/data-centralization-over-network-application-for-insurance-services/

WORK DETAILS

Here’s a typical structure for Data Centralization Over Network Application For Insurance Services research projects:

  • The title page of Data Centralization Over Network Application For Insurance Services should include the project title, your name, institution, and date.
  • The abstract of Data Centralization Over Network Application For Insurance Services should be a summary of around 150-250 words and should highlight the main objectives, methods, results, and conclusions.
  • The introduction of Data Centralization Over Network Application For Insurance Services should provide the background information, outline the research problem, and state the objectives and significance of the study.
  • Review existing research related to Data Centralization Over Network Application For Insurance Services, identifying gaps the study aims to fill.
  • The methodology section of Data Centralization Over Network Application For Insurance Services should describe the research design, data collection methods, and analytical techniques used.
  • Present the findings of the Data Centralization Over Network Application For Insurance Services research study using tables, charts, and graphs to illustrate key points.
  • Interpret Data Centralization Over Network Application For Insurance Services results, discussing their implications, limitations, and potential areas for future research.
  • Summarize the main findings of the Data Centralization Over Network Application For Insurance Services study and restate its significance.
  • List all the sources you cited in Data Centralization Over Network Application For Insurance Services project, following a specific citation style (e.g., APA, MLA, Chicago).