Data name rationalization's goal is to reduce the number of physical record groups and data names in a system in an attempt to achieve a one to one correlation between physical definitions and logical element groupings. Specific objectives include:
· Preparing succinct primary record groups as input to data redesign efforts
· Improving the ability to apply application maintenance and enhancement requests
· Collapsing multiple physical records into a single record definition
· Developing standard Copy members that can be reused across a system
· Standardizing names within reusable record definitions and at the program level
Note: Task Steps that identify and eliminate aliases, synonyms and homonyms at the system level for shared record groups, and at the program level for localized elements, depend on cross system analysis and propagation capabilities described in the tools section of this task.
The entrance criteria for the data name rationalization task are listed below.
· Completion of the data definition analysis of the technical assessment component of the Inventory/Analysis stage
· Completion of the environmental analysis task
· Determination of the record group(s) or file(s) of interest to be rationalized
· Completion of the application staging task for system components as listed input requirements below
The personnel and skill requirements necessary to meet the data name rationalization task are identified below.
· Process Positioning Expert
- Expertise in applying cross system name rationalization tools and techniques
· Current Systems Expert
- Knowledge of existing system source operational requirements and application functionality
· Data Definition Analyst
- Knowledge of application data structure and content
· Data Administrator/DBA
- Knowledge of data usage procedures and standards for the application area and the organization
· Systems Programmer
- Security access to physical system objects
The system components and related inputs required to initiate and complete the data name rationalization task are listed below.
· System components including program, Copy, JCL and screen layout source loaded into Original/Input working libraries
· Identification of the records and files of interest to be rationalized
Note: This could be all record groups across the systems of interest.
· Data definition standardization control log Form 023
· Positioning work plan Form 020
· Record grouping reports created in the data definition analysis task
· Primary I/O record definitions identified during data definition analysis
· Inventory lists and cross reference reports created in the environmental analysis
· Data definition analysis results recorded on Form 003C
Technologies supporting the data name rationalization task include data definition analyzer, data name rationalization, open systems repository, cataloging, program editor, compiler/preprocessors and comparator tools. These tools are used to represent information as required by this task.
Data definition analyzer
The main role this tool plays within this task is to rapidly and automatically analyze logical data descriptions to provide the user with information about their level of redundancy so as to facilitate the task of renaming and standardizing data elements across the system.
Tool attributes include physical definition cross reference ability, size and data structure comparison capability, control transfer summary analysis, in-context usage analysis, redundancy analysis and selective name usage analysis. Data gathered should be available in cross reference reports and, ideally, in a repository. Additional requirements include linking physical files and screen definitions to source code definitions.
Data name rationalization tool
The main role this tool plays within this task is to automatically build composite records, allowing for data name standardization and enhancement, and to automatically propagate these composite records throughout the system. Additionally, a data name rationalization tool should be able to replace program level data references with their new names.
Open systems repository
A repository provides an important, yet optional, capability to link data definitions to other definitions and to physical objects using a formal model. Use of repository in this task requires that a baseline meta-data was established during data definition analysis. For large systems or cross functional expansion efforts, this repository model can be maintained as a sophisticated mechanism for managing project efforts.
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 meta-model that supports this analysis is shown in the Appendix section of the Comsys-TIM product. A secondary, and optional, requirement involves accepting an automated load format based on tools that parse and analyze legacy environments.
Cataloging tool
This is required to establish several libraries with which to manage the rationalization of the data elements in the source. Any library management tool should be able to accomplish this.
Program editor
This is required to physically rationalize the records, composites, and related statements in the source. Use a program editor appropriate to the environment.
Compiler/preprocessors
A source language compiler/preprocessor is required to parse source code and convert it into machine executable instructions. This compilation process identifies many types of errors, and requires their correction before it will complete successfully.
Comparator
This tool is used to validate changes made to source code by comparing the input programs line by line and producing listings of any differences it finds.
The data name rationalization task is comprised of the following task steps:
