Interim Support Planning

Objectives

Unless a system is being phased out completely, there is typically some level of support that must continue near-term, regardless of long-term issues. Technical characteristics of a system are, in many cases, the most straight forward to address. Cryptic and redundant data definitions, poor program structure, redundant or monolithic modules, and inadequate front-ends can be addressed within a reasonable pay back period. These same activities also support analysis and reuse under various strategic redevelopment scenarios.

The interim plan, which focuses on correcting structural weaknesses while delivering new user capability under the current systems architecture, must be driven by business objectives.

This includes new functionality, data sharing and presentation issues, performance issues and reliability factors. Impact of this plan reaches well beyond minor, short-term improvement, however. It may be dictated by the need to stabilize baseline systems for subsequent rule extraction under Transformation. This should be considered when building the interim plan business case.

Recommendations usually included in the interim plan focus on delivering immediate value to end users while streamlining the number of individuals and skill levels required to maintain the system. The interim plan is a required deliverable of Inventory/Analysis and, where applicable, must be integrated with the long range strategy for that business area.

Specific objectives for this process include:

· Define interim "window" based on application objectives

Note: Interim window could be an extended period of time.

· Identify weaknesses in current physical system that, once corrected, could leverage the maintenance support team

· Recommend Positioning or re-documentation techniques for current systems based on business requirements

· Develop a plan, including a pilot process, to upgrade the technical condition of the existing system

· Project cost benefit analyses for each of the recommended improvements

· If applicable, determine how short-term improvements leverage strategic redevelopment goals.

Entrance Criteria

The entrance criteria for the interim support planning task is listed below.

Note: Following is the typical minimum level of assessment tasks to be performed.

· Establishment of application objectives on inventory/analysis executive planning Form 001

· Completion of all relevant technical assessment tasks based on scenario driving the assessment

· Completion of the user backlog requirements analysis

· Completion of the IS infrastructure assessment

Note: Following are required for more in-depth interim planning and for an Interim Plan being developed in support of a Strategic Redevelopment Plan.

· Completion of physical analysis of the general system architectural assessment

Note: All or part of the architecture assessment tasks may be warranted based on findings during technical assessment. While the interim plan does not dramatically impact most architectural issues, it may affect areas such as user interface, technical obsolescence and data structure inadequacies.

· Completion of all remaining architectural assessment tasks

Note: Following are required when an Interim Plan is being developed in support of a Strategic Redevelopment Plan.

· Completion of subject area/entity type analysis for current system

· Completion of function hierarchy analysis and function dependency analysis for current system

· Completion of business function/entity type analysis

· Completion of feasibility analysis/assessment integration

Roles/Skills

The personnel and skill requirements necessary to meet the interim support planning task objectives are identified below.

· Redevelopment Expert

- Ability to review analysis findings and make interim recommendations based on short and long-term requirements

· Application Area Manager

- Ability to provide input to and approve interim system plans

· Project Manager

- Ability plan, manage and control the project

- Ability establish an interim plan that can be delivered in required time frames

· Current Systems Expert

- Knowledge of existing system functional breakdown

- Review of plan and comments as to where the most benefit may be gained near term

· User Requirements Analyst

- Input, review and sign-off on interim plan

Input Requirements

The system components and related inputs required to initiate and complete the interim support planning task are listed below.

· If any enterprise planning tasks were performed as input to Inventory/Analysis assessment, any forms completed during that analysis

· Metrics recorded on completed assessment forms:

- 001 - Inventory/Analysis executive planning form

- 003A - environmental analysis form

- 003B - process flow analysis form (with attachments)

- 003C - data definition analysis form

- 005 - functional assessment form (functional quality ratings only)

- 007 - IS infrastructure assessment form

Note: Form 004 is highly desirable if significant remodularization is planned as an interim activity or if the interim plan is being reviewed as a precursor to strategic redevelopment planning.

- 004 - functional mapping form (current program/process mapping)

Note: Highly desirable, but not required.

- 006 - architectural assessment form

- 008A - module maintainability ratings form

- 008 - assessment integration form

· Blank copy of Positioning Workplan Form 020

· Categorized, prioritized backlog request list from user backlog requirements analysis

· Assessment integration analysis summary for short-term maintenance requirements

· Assessment integration/feasibility analysis report summarizing interim requirements and, if applicable, strategic issues

Tool/Technology Support

Technologies supporting the interim support planning task include spreadsheet, project management and word processing tools. These tools are used to represent information as required by this task.

Spreadsheet

This tool is used to review prior metric results input into Comsys-TIM forms during prior tasks.

Project management tool

Step one requires work plan finalization using a project management tool. It is also a key tool for actually building the main deliverable from this task - the interim plan.

Word processor

This is required to record analysis results.

Task Steps

The interim support planning task is comprised of the following task steps:

Create Interim Plan Outline
Correlate Analysis Requirements/Findings
Identify Positioning Tasks & Cost Analysis
Develop Pilot or Proof of Concept Plan
Finalize Interim Support Work Plan
Finalize Application Staging Plan
Finalize Language Change Work Effort
Finalize Flaw Analysis & Removal Work Plan
Determine Restructuring Work Effort
Finalize Design Improvement Work Effort
Finalize Field & Record Size Expansion Plan
Assess Data Definition Rationalization Scope
Finalize Data Definition Rationalization Plan
Develop Literal Externalization Work Plan
Finalize Physical Data Upgrade Plan
Finalize Data Definition Migration Plan
Finalize Code Slicing Work Plan
Develop Reconciliation & Re-Aggregation Plan
Establish Validation Criteria & Plan
Identify Support Structure Adjustments
Integrate Interim Plan & Strategic Objectives