 |
Perform Repository Pre-Loading Analysis |
|
Execute Repository Load Process |
|
Create Infrastructure Management Procedures |
This task involves representing existing physical data structures in a repository, encyclopedia or dictionary format. The objective is not to replace similar import and/or export activities defined in Transformation, but to import physical representations into a medium analysts can use to understand a system more effectively.
This task does not conflict with the use of the LTM in other Comsys-TIM tasks. In fact this task updates data definition changes that were made during data definition standardization tasks. This task also supports the "institutionalization" of a support infrastructure that includes repository, tools and other standards.
This task is recommended after data definition rationalization and/or literal externalization because it serves to document results while establishing a process to facilitate control over future modifications. Specific objectives include:
· Represent data definitions from current physical systems in repository, dictionary or encyclopedia formats
· Update LTM model, if in use, to reflect data structure changes that may have occurred as a result of prior data definition standardization tasks
· Represent physical data definition usage patterns and relationships in an easy to access/easy to reference format and, possibly, on a workstation platform
· Institutionalize repository procedures, tool usage, work environments and related processes
The entrance criteria for the data definition migration task are listed below.
· Requirement to load a repository or encyclopedia
· Completion of the environmental analysis task
· Completion of data definition rationalization
Note: Rationalization is not required, but improves end result since repositories cannot rationalize data themselves. Loading redundant, cryptic data definitions into a repository is ineffective since these tools, at best, trace usage by name only.
· Completion of literal externalization - recommended, but not required
· Completion of field and record size expansion - as dictated by scenario
Optional: Populated LTM as defined in tasks leading up to this task in Comsys-TIM.
· Populated repository based on LTM model - see technology section of this task
Optional based on extend of effort required in last step of this task:
· Completion of IS Infrastructure Assessment
The personnel and skill requirements necessary to meet the data definition migration task objectives are identified below.
· Repository Administrator
- Expertise in working with target repository
· Application Manager
- Responsibility for institutionalizing management procedures in area of repository support and general tool/method use
· Current Systems Expert
- Knowledge of existing system data usage as implemented
- Knowledge of existing system data as designed and used
· Data Administrator/DBA
- As required to monitor repository/encyclopedia load
· Data Definition Analyst
- Knowledge of how to assess cross system data definitions including producing and interpreting tool
The system components and related inputs required to initiate and complete the data definition migration task are listed below.
· If LTM is being used, previously populated repository using LTM model
· Physical source and Copy members containing rationalized data definitions
· JCL, screen definitions, DDL and related objects as supported by target repository
· Completed IS Infrastructure Assessment Form 007
Technologies supporting the data definition migration task include open system repository, cataloging and word processing tools. These tools are used to represent information as required by this task.
Open systems repository
Tools supporting this task are the repositories themselves. Each tool has its own, unique import facility and underlying storage capability. Occasionally, third party tools support repository loading. Omitted from the list are the I-CASE encyclopedias or the workbench tools that actually store a system. The tools in this section are specifically geared at representing current physical systems and functioning either as dynamic or passive repositories. This task utilizes whatever user model is in place for a given repository as well as the LTM model (see below) for data structure representation.
Legacy transition meta-model (LTM) related requirements include the ability to reflect system components as objects within the repository model and populate that model from a legacy environment. A recommended baseline meta-model (LTM) to support this analysis is shown in the Appendix section of Comsys-TIM. A secondary, and optional, requirement involves accepting an automated load format based on tools that parse and analyze legacy environments. If LTM is used in this task, automated population should have occurred during Inventory/Analysis.
Cataloging tool
This is required to establish several libraries with which to manage the staging of the source. Any library management tool should be able to accomplish this.
Word processor
This is required to record analysis narrative and, in the absence of a spread sheet tool, metric results.
The data definition migration task is comprised of the following task steps:
Perform Repository Pre-Loading Analysis Execute Repository Load Process Create Infrastructure Management Procedures