Periscope uses the term ‘upgrade’ to describe migration of an existing application to a newer version as well as transforming a legacy system to a cutting-edge web-based system that Periscope develops partnering with you:
System Upgrade (upgrade/transform your legacy application to modern web technologies) and Application Upgrade (upgrade Periscope application to a newer release)

Periscope Upgrade Approach


The Upgrade process can be broadly divided into the following phases:

1. Planning & Preparation Phase

1.1. In addition to developing an upgrade strategy and a detailed project plan, the planning of the upgrade will broadly involve the following:

Conduct Business Fit Gap Analysis:
This analysis with the detailed analysis of the external interfaces and integration points, will reveal all the gaps in the new release, determine where the delivered functionality can be leveraged with no/minimal customizations and highlight any customer related unique business processes that have been developed in new release/system and are absent in existing system. The functional area should be detailed down to transaction/business process, component level and interface level:

Plan Technical Requirements:
Thorough review of the existing technical environment and also taking into consideration the Hardware/Software requirements for the new release, will determine the technical requirements for the Upgrade.

Plan Project Team Requirements:
Identify resources required from both Periscope and the Client
1.2. The preparation will involve:

    - Install New Release/System
    - Prepare Copy of Production Database

2. Upgrade Phase

2.1. Run and Review Compare between existing and new system/release
2.2. Apply Application Changes
2.3. Complete Production Copy
2.4. Test the Upgrade

3. Implementation Phase

3.1. Move to Production

    Business Fit Gap Steps:

      Functionality to be retained and brought forward as is using the Upgrade process
      Functionality to be dropped from existing system/release and adopt the new functionality from new system/release
      Functionality from existing system/release to be retained on an as-is basis and but re-implemented in new system/release
      Functionality from existing system/release to be retained re-implemented and enhanced as a result of new system/release implementation
      Functionality leveraged from new system/release modules and/or from enhancement of delivered functions