Data Link Overview

Data links can make a big difference in the amount of work your systems do for your customers. The typical data link consists of two pieces of software, and a standardized data packet that is passed between the systems. The software components consist of:

The Server component, which runs on the system that has primary ownership of the data, and

The Client component, which runs on the system that requests the data from the Server. The Client is usually designed to request a read-only copy of the data on an as-needed basis

The requested data is packaged by the Server component into a documented, standard form, and is sent upon request to the Client component. The Client unpacks the data packet, and uses the requested data as appropriate.

Both the server and the client software components may be seamlessly integrated into existing applications, or they may be dedicated, stand-alone applications.

Typical project plan

The typical project consists of three major phases: design, development/ test, and implementation.

Stage 1: Design

The design stage is devoted to obtaining, organizing, and documenting the following information:

The source of the data. What table, file, field, and field position is each transferred data element coming from

The transformations, edits, and tests that must be done as the data is being packaged by the Server component. This includes formulas or algorithms for converting data from one form or value to another, edit checks to make sure data values fall within the allowable range as required for the new system, and any tests that are required to meet data integrity, uniqueness, and referential integrity constraints imposed by the target system

The transfer packet format. This is the record format or XML schema that will be used to store the data in the transfer packet.

The destination of the data. What location within the target system's data store will the each element be stored into once the transformations are completed successfully.

The Cutover Test Plan. What final acceptance tests will the customer and Redbridge perform to assure us that the tranfer of the data is done accurately and completely?

Design Stage Collaboration

The customer supplies all available documentation about the source, transformations and destination of the data. This information is usually readily available, but in rare cases it must be laboriously reconstructed, often by trial and error. Once this information has been obtained, Redbridge consolidates all this material into a mapping document that spells out where each data element is coming from, where it's going, and any applicable transformations, edits, and tests that must be performed on the data as its packaged for transfer to the requesting Client components.

The customer then reviews the mapping document, signs off on it, and that kicks off the development and testing work.

Stage 2: Development and Test

Redbridge uses the mapping information from the Desigh phase as blueprints to write the Server and Client software components, and the transfer packet data structures. As the coding is completed for each section of the data to be transferred, it is unit tested. Once all unit development and testing is done, a full system-test is performed. This testing and development is typically done as an iterative, incremental process until finally the entire system has been thoroughly tested. Then we're ready for cutover.

Stage 3: Implementation

Once the data link software is built and tested, it's time to install it on the production systems, and move the project into maintenance mode.