Core IT
. Archival Restore System
. Billing Rewrite System
. Reengineering of Informix 4GL system
. Translation of AutoCAD Drawings
. Sales force Automation Case tool
. B2B Portal for A Publishing Company
Engineering Services
. Design & Detailing in Compressor
. Welding Line Fixture Design
White Papers

Business Model
Service Delivery Model
 FAQ's
 Subscribe
 Corporate Brochure

You are here: home / case studies / Core IT / archival restore system

Archival Restore System
Tools Used
  • Oracle 9i
  • XML
  • PL/SQL
  • ASP, Java Script,     VB Script
  • Java class
  • Our Strong offshore methodology helps in the successful development of 'Archival and Restore' system using Oracle PL/SQL.

    The Client: US based second largest credit bureau
    Business Model: Offshore fixed price

    The Challenge

    This is a development of a Client/Server system for archival and restore of cases older than specified time period. The Client processes different kind of home mortgage reports for online as-well-as batch customers. On an average 50,000 reports are generated per day. This requires the data to be archived off the system to keep the database size to a minimum.

    The ArchRestore redevelopment involved:

    • Using XML for easy interfaces with other systems.
    • Developing code in ASP. VBScript and Java Script using IIS
    • Developing the application in Oracle PL/SQL
    • Java class files for File write
    • Using XML for creating the interface file; one per case
    • Restoration of XML file on demand
    • Creating configurable system for ease of use

    The Solution

    After the initial system study, the entire project was executed at our offshore development center.

    All potential risk items were identified during the system study phase. For instance, the Client already had an existing application, which was not flexible, and the existing data from that application was not reusable with the new application.

    The requirements were gathered after discussing with the end users and the technical staff of the Client. The non-functional requirements were suggested to the customer to make the system useful for interfacing with other in-house applications. The system was made flexible to be useful in case the database schema was altered. Multiple versions of the DTD were possible to be created in the application. The system was made highly parameter driven so that the user could alter the system characteristics on the fly. The test cases were prepared and approved by the Client team. The test data was downloaded from the Client on our FTP site and used for unit and system testing of the application.

    There was no schedule overruns. Our team met the deadline for every milestone on time.

      © 2003-2005 IT Elite Systems. All rights reserved. Terms & Use | Contact | Sitemap