Information redevelopment planning consolidates enterprise-wide analysis results, evaluates suggested options, and delivers an enterprise-wide information architecture transition strategy. Specific objectives of this task include:
· Consolidate analyses gathered during the enterprise-wide redevelopment assessment
· Identify high-level strategies based on findings of enterprise-wide assessment
· Establish transition mapping strategy
· Link enterprise assessment findings to various strategic initiatives
· Review ongoing projects and recommend alternative approaches and scenarios
The entrance criteria for the information redevelopment planning task are listed below.
· List of strategic goals for key application areas created in Enterprise Analysis Planning stage
· Enterprise redevelopment objectives for assessment project created in Enterprise Analysis Planning stage
· Completion of assessment tasks as dictated by scenario or project driving enterprise redevelopment planning effort
Note: This task assumes completion of all tasks within this stage. If tasks or steps were omitted, invoking scenario should selectively guide redevelopment planners through this task.
· Access to management and user personnel, as defined in Roles/Skills section, required to complete this task
The personnel and skill requirements necessary to meet the information redevelopment planning task objectives are identified below.
· Redevelopment Expert
- Subject matter expert with ability to facilitate enterprise-wide redevelopment planning sessions
· Application Area Manager
- Ability to provide feedback on and response to required application area strategic adjustments
· Data Administrator/DBA
- Knowledge of enterprise-wide data structures
· Project Manager
- Ability and authority to create work plans, assign resources and manage work flow of redevelopment project
· IS Management/Executives
- Knowledge of strategic and near term IS goals and ability to establish an enterprise redevelopment strategy
· User Requirements Analyst
- Knowledge of ongoing business requirements and ability to provide input and approval of architecture transition strategy
The inputs used in the Enterprise Analysis Planning task include:
· Baseline list of motivational factors as to why assessment was performed
· List of strategic information goals for the IS organization
· If an Comsys-TIM scenario is being followed, the symptoms, requirements, approach and steps for that scenario
The results from the Enterprise Analysis Planning task include:
· List of enterprise redevelopment assessment objectives
· Enterprise Redevelopment Assessment work plan
· List of business areas and systems assessed (these are included on Form 040, an input required below)
Completed copies of the following forms are needed:
Note: Completion of each form is based on the scenario or project drivingassessment effort.
· Enterprise Summary Form 040
Note: Form 040B actually replaces Form 040 on language level upgrade efforts.
· If this is a language level upgrade project, alternatively obtain Enterprise Summary Form 040B - Language Upgrade Supplement
· Business Area/Data Store Matrix Form 041
Note: Form 041 copies completed for enterprise and, optionally, for individual business areas based on scenario.
· Business Area/Function Matrix Form 042
· Business Area/Project Matrix Form 043
Results from the Technical Architecture Assessment including:
· Narrative summary of current technical architecture findings and, optionally, current to target technical architecture variances
Results from the Data Architecture Assessment including:
· Narrative summary of current data architecture findings and, optionally, current to target data architecture variances
Optional - based on requirement to provide logical view of legacy data utilization
· Existing subject areas and associations defined within a high-level subject area model for legacy environment
Results from the Business Architecture Assessment including:
· Narrative summary of current business architecture findings and, optionally, current to target business architecture variances
· Current business enterprise level architecture information flow summary DFD
The following deliverable is subject to repository availability and to load processing performed during architecture assessment tasks - it is required if the segmentation step is to be applied in this task.
· Updated legacy transition meta-model with business area/system objects & relationships
Technologies supporting this task include date impact analyzer, enterprise segmentation, open systems repository, project management and word processing tools. Secondary tools, referenced in subsequent tasks of this stage, include strategic planning products that may have been used to represent strategic plans, goals and work flows. While not directly required for this task, these planning tools may be a vehicle for representing information required as input to this task.
Date impact analyzer
It is nearly impossible to perform large scale date impact analysis without automated tools. In an IBM MVS or similar mainframe environment, identifying all potential date related records/fields is very time consuming. The main role this tool plays within this task is to rapidly and automatically identify the number of date fields to assist in the development of a budget for Year 2000 projects, particularly when using the Cost Per Date Estimating model.
Enterprise segmentation tool
Most projects should be started with a complete inventory of the Corporate systems. A key purpose of this inventory is to identify "upgrade units", also called "compliance units". These are IS components which will be analyzed, modified, tested and moved back into production as a group. An upgrade unit should contain no external dependencies.
The main role this tool plays within this task is to perform an enterprise-wide analysis (through JCL analysis of Data Set Names in the JOB and PROC libraries) that logically groups components for simultaneous conversion. This provides complete data tracing and allows the grouping of components through related data stores.
Open systems repository
A repository provides, for this task, facilitates documentation of upgrade units within segmentation step. Loading of legacy transition meta-data must have been completed in prior tasks in order to utilize it within this task.
Requirements include the ability to reflect system components as objects within the repository model and populate that model from a legacy environment. A recommended transition legacy transition meta-model supporting this analysis is shown in the Appendix section of the Comsys-TIM product.
Project management tool
Tool support for this task includes project planning capabilities in order to support the creation of a budget for year 2000 projects. This includes the ability to depict work tasks and time/cost estimates.
Project planning tools are highly recommended for this step.
Word processor
Word processing tool supports creation of Enterprise Redevelopment Assessment Report and is required for this task.
The information redevelopment planning task is comprised of the following task steps:
