Comsys-TIM Tool Classification Glossary

Re-engineering Tool Classifications

The analysis import facility populates one or more analysis level representations in an Information Engineering development approach. This is typically one or more models defined within the analysis workstation of an I-CASE modeling tool.

A business rule capture tool should have the ability to identify and slice out logic paths based on specified selection criteria. This tool ideally should, either statically or dynamically, analyze logic paths across source program boundaries. It should also facilitate bypassing or highlighting implementation dependent logic, store extracted rules, further extract against previously extracted rules, display rules in a variation of formats and transform extracted rules into a reusable format.

This tool should be able to represent business operations defined in the source application in diagrammatic form and to facilitate specification of triggers, preconditions and post conditions within a rule editor. This tool should also allow the user to test rules through immediate execution of the model.

A cataloging tool provides the user with the ability to establish libraries and data sets on the system catalog with specific characteristics including location, read/write capability, file duration, etc.

A change integration tool detects, consolidates and reconciles multiple versions of applications. The change integration tool should provide robust impact analysis capabilities for identifying versions that contain differences, name patterns for merging different versions of members with different names and an intelligent merge editor that focuses on maintaining an audit trail of all modifications and conflicts.

A code remodularization facility performs code slicing to carve out segmented functions of a program and to turn them into new called sub-programs. The slicing tool must be able to perform automated slicing based on multiple criteria.

The comparator is used to compare source or data files byte by byte to determine all differences. Comparator functionality should include the use of keys or indexes to allow synchronization of files, and may also include the ability to mask portions of a record by specifying some position or named fields to ignore when performing the comparison.

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.

The configuration management facility provides the versioning capabilities necessary to store multiple versions of an element. This allows for creation of working version libraries. Other requirements include controlling access to libraries by defining user access rights and standard change control procedures and providing a wide variety of ways to view change information - current, historical or changes only.

A data definition analyzer rapidly and automatically analyzes logical data descriptions to provide the user with information about their structure, similarities, level of redundancy and quality. 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. Additional requirements include the ability to link physical files and screen definitions to source code definitions.

Data flow diagramming (DFD) tools are used to document internal system flows (program/file level) as well as links to interface systems. The DFD tool is used to document current system information flows. This may be done manually or with a drawing tool, but DFD tools allow models to be modified easily.

The data migration tool automates the process of converting data values in a physical data store. Functionality includes the ability to analyze, manipulate and convert data to user specification. The tool should be able to utilize either a data dictionary, a repository or a set of user-defined specifications, or some combination of the three, to provide a source definition and a target definition for the data to be converted.

A data name rationalization tool automatically builds composite records from the set of record layouts analyzed, allowing for data name standardization and enhancement, and automatically propagates 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.

The data reverse engineering tool focuses on the capture, import and manipulation of data definitions (and in some cases physical data) with the intent of deriving a logical model. This is typically in the form of an entity relationship model for this task. Features include the ability to capture existing data definitions of all types and the ability to represent records as entities and elements as attributes in a tool encyclopedia. Optional but highly desirable features include the ability to apply artificial intelligence to captured data representations to create an ER model, the ability to merge multiple models and the ability to assist in producing a normalized data model from an ER model.

The year 2000 will require either expansion of existing date fields on files, data bases, and within programs to accommodate a century designation or a procedural workaround in the source code. Expansion of date fields automatically converts record groups/fields to support the new century. The main role this tool plays is to identify, convert, and document date changes in programs and record groups throughout system.

The date impact analyzer tool identifies how dates are used by programs and provides a complete cross-reference of those components affected by a change - including source code, copybooks, files, JCL, CICS tables, etc. Requirements include identifying date usage in programs (i.e. MOVEs, COMPAREs), element tracing throughout an application and missing or obsolete components.

The design import facility allows representation of current system flows in dialog flow format by automatically importing multiple physical objects into the design workstation. It accomplishes this by tracing and capturing program logic and importing it into annotation format, which it then loads into the design workstation. Additional features include a function to load entire COBOL programs into the design workstation.

The enterprise segmentation tool identifies "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 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. Key requirements include the ability to provide complete data tracing and the grouping of components through related data stores.

The environmental analyzer accepts as input system wide application libraries and analyzes them to provide information on system flows, relationships and dependencies. Key requirements include the ability to rapidly parse and cross reference system objects (i.e. JCL, Source, Load, etc.) across multiple application areas for production hardware and software platforms.

The event modeling tool should be able to model events within a business area and support basic event modeling techniques, including the following entities: business operations, events, event subtypes, triggers, stimuli to initiate triggers, partitioned events which trigger multiple operations, control conditions which represent decision points where multiple triggers may initiate operations, and entry and exit points to the model. This tool should also integrate with modeling facilities used to specify system objects and business rules.

I-CASE analysis workstations provide a mechanism for specifying current and target process action diagrams. While automated input facility is not available in all formats for this type of model, captured rules may be respecified into bottom up/top down process action diagrams with this technology.

The interactive date change facility should be able to trace dates across a system through data usage and execution linkage. Analysis may be depicted either graphically or highlighted in interactive source code views. The user may then apply the date modifications as necessary.

The interactive program analysis tool includes an ability to graph a program and show decision paths based on that graph in interactive mode. Decision paths can be depicted using decision trees, control flow graphs or similar facilities. This tool allows the analyst to change nodes or decision points on the graph and immediately see the implications to the affected business rules and control flow.

The interactive system analysis tool should be able to trace logic across a system through data usage and execution linkage. Analysis may be depicted either graphically or highlighted in interactive source code views.

The interface/bridge generator supports the conversion of date field definitions within programs. If redevelopment goals include expanding or converting some physical data stores without expanding related data stores belonging to different systems, and if data is shared between expanded and unexpanded systems, activation and deactivation of data interface routines is required. This technique allows for files to be selectively converted over time and eliminates the need to simultaneously convert all of the programs that use a single file.

The language change/upgrade tool automatically revises source code to comply with either the requirements of a new release or an entirely different language. This change in source language ideally causes no corresponding change in functionality, although some small changes sometimes do occur based upon the functions and limitations of different languages.

The object modeling tool focuses on modeling the system objects within a business area of the organization. This tool should support basic object modeling requirements according to the Martin/Odell Object Oriented Analysis (OOA) object diagramming method. It should minimally include the following diagramming concepts: Object types, object type partitions, associations, subtypes and components. Additional features may include the ability to immediately prototype results of object model modifications or to extend modeling notations based on other requirements.

A repository provides the capability to link system objects using a formal model. Requirements include the ability to reflect system components as objects within the repository model and to populate that model from a legacy environment. A secondary, and optional, requirement involves accepting an automated load format based on tools that parse and analyze legacy environments. For large systems or cross functional expansion efforts, this repository model can be maintained as a sophisticated mechanism for managing project efforts.

The physical data analyzer is capable of automatically scanning selected data and producing a sampling of defective data. There are three common methods for determining defective data: comparison of the data to user-defined rules, comparison of the data to system definitions (either hard-coded in the source or defined in the dictionary) and analysis of the data alone to discover inherent rules and dependencies. Optional features include the ability to select a data sample and to produce data quality management reports.

The physical data design tool helps to automate the data design process by facilitating creation of the indexes on primary keys, validation of foreign keys and finalization of the physical relational model. Key features include the ability to accept logical data model and physical data volume requirements as input to development of relational data base tables. In addition, the tool may assist in normalization of the model.

The presentation extract/design tool supports the analysis of user presentation layer views of a system by providing automated screen or report mockups for system reporting or on-line teleprocessing facilities. A second feature that is important, though not essential, is automated screen map to GUI conversion. Some tools can read screen maps, including BMS and MFS, and produce an initial GUI design of the screen.

A project management tool provides the capability to define a project in terms of a series of chronological steps from inception to completion, including step based estimates, roles, deliverables and dependencies, and to automatically track and update the project plan as steps are completed.

A program editor allows source text to be accessed and altered. Beyond the ability to type new or overlaying text, functionality includes a standard set of line commands, such as Insert, Delete, Move and Copy, scrolling commands and global commands, such as Change All.

Restructuring tools parse and analyze source code, determine all possible logic paths and recreate a functionally identical version of the program in structured form. The degree of flexibility in output formats and styles varies from tool to tool, but all allow the user some leeway in determining the format of the resultant code.

Risk assessment tools help assess and plan for Year 2000 problems from a business perspective. It allows users to assess risks and experiment with alternative mitigation and testing plans. It enables prioritization of limited Year 2000 resources (people, time and money). The software provides a means of linking an organization's technology resources to its business functions. This ability to map interdependencies, along with the software's simulation capabilities, provides an organization with a practical framework for prioritizing Y2K mitigation and testing efforts based on an understanding of the business risks involved.

Spreadsheet tools offer a convenient format for recording much of the information gathered throughout the Comsys-TIM. Referenced TIM Forms have been pre-loaded into certain spread sheet tools to facilitate data entry and analysis in a tabular format.

The static analysis tool is able to graph programs and analyze their quality based on those graphs to produce several standard types of source language metric summary level analysis, including analysis of code complexity, structure and defects.

Strategic planning tools aid in gathering function dependency, data flow diagram, subject area and interaction models to represent high level views of the existing business and data architecture.

Testing tools are primarily used for one or more facets of the testing process. Functionality includes dynamic coverage analysis, test data selection and on-line transaction capture/playback. Dynamic coverage analysis reports percentage of logic statements covered by the utilized data or the actual count of the statements covered. Test data selection covers tools which aid in building a comprehensive test bed. On-line transaction capture/playback collects a series of on-line calls so as to provide data for the application to be run later in a batch mode.

The transaction simulation facility captures, packages, transmits and receives host based transactions to and from client/server environment using transaction simulation software. The facility interfaces with GUI front-end tools to package, compress and transmit host data to and from workstation environments.

The virtual date utility provides the capability to intercept the current system date (and time in some cases) to ensure the accuracy of Year 2000 or other date/time modifications. Requirements include executing applications using future system dates. This will enable you to test applications before the turn of the century and avoid potential problems.

A word processor provides the capability to enter and format text in a flexible and easily updated form, using a standard set of features such as pull-down menus for formatting and stylistic options, cursor highlighting of text for selected operations, optional template-driven document creation, and sophisticated and varied printing options.

The year 2000 will require either expansion of existing date fields on files, data bases, and other data stores to accommodate a century designation, or a procedural workaround in the source code. Procedural workarounds involve the creation or selection of date handling routines. These routines can perform the conversion of 2-digit year fields to 4-digit year fields without physically changing the existing date fields in the data stores. Access to these routines must be built into the source code of each program using date fields for which the year 2000 might cause problems.

Various routines have been created to handle almost any date handling situation, including those requiring no date conversion whatsoever. These routines may also be used for date standardization in any system, even those involved in a date field expansion project. As the number of available date routines within each vendor package is quite large, they will not be individually mentioned. Refer to the vendors for more explicit information.

These date routines can also be created or consolidated from existing subroutines or source code within any organization, if the resources and time to do so are available.