VHUNT Ordering options and Pricing

VHUNT understands program variable dynamics and is THE ideal tool for addressing the software maintenance/documentation problems
VHUNT
will save software maintenance valuable resource (time) by using VHUNT source code AutoCorrect (Code Renovation) feature.
Background:

The most expensive phase of the software life cycle is its maintenance. The issues facing maintainers of a large software systems is the ability to identify all of the appearances of each and every element of the software down to the individual variable (or field) in all of the software modules which may be linked together for execution. Without this capability it becomes impossible to change certain elements of the software without the risking all other relevant subsequent sections of code adjustments. Software maintenance can NOT be performed without a comprehensive understanding of program variables.

As an example, a procedure ( function ) interface and the input/output parameters passing to / and from it must be consistent across all appearances of the procedure call. In certain languages, ( and within certain limits ), the Software Generation System (compiler, etc.) being used may (if so constructed) identify any inconsistencies existing in the calling ( and called ) locations. In most cases and languages this capability does not exist, but the consistency is required for correct execution.

VHUNT is a tool designed to assist a group of (one or more) Software engineers to undertake the maintenance and / or upgrade/update a large and / or complex software systems. It provides the maintainers with the capability to identify software variables in the source code and to access them directly while modifying the source code using his / her favorite editor, or using VHUNT source code AutoCorrect
(Code Renovation) feature.

VHUNT has independent language capabilities via pattern-matching technique to find date suspect items in code or data. The user provides the seed database to start the pattern-matching process. A seed is a data item or format that is know to occur in the code/data. As VHUNT is scanning the code/data it matches items to the seed(s) called a hit(s) or suspect variable. The hits are reported by VHUNT and AutoCorrect can be performed on the suspect variables.

VHUNT is Software Slicing Tool, as well as a Data Name Rationalization Tool, and source code AutoCorrect
(Code Renovation) Tool.
NOTE: (Software Slicing) Allows viewing of all source code affecting a given variable or statement
Variable Hunter (VHUNT) has been proven to be a useful tool for understanding program variables.


Contents:


Summary

Source code modules are processed by VHUNT to locate and highlight those variables that are derived from the seed data-base.This process is extended ( recursively ) to all variables that reference ( or are referenced by ) suspect variables. VHUNT produces reports containing both metrics summarizing the extent of the required analysis effort, ROM cost to amend suspect variables, ( optional ) listings of the suspect code lines, and optionally perform source code AutoCorrect (Code Renovation).

VHUNT is adapted to a variety of programming language grammar:
"ADA, C/C++, JOVIAL, PASCAL, FORTRAN, COBOL" optionally performing two level code slicing
VHUNT supports "ASM, ASCII file"

Back to Top


Key Features

The major feature of VHUNT is the ease of user interface panels, output visualization, and VHUNT's analysis (execution) speed.


OUTPUT:
The output visualization is reported via the " Occurrences of Suspect Variables " panel. Detailed information on the rest of the output fields are available in VHUNT help file. The major features are covered here. The totals are reported ( for grouped files ), i.e. number of Suspect Variables. This number represents the Suspect Variables that were derived from the analysis, and the total cost estimate ( for grouped files ) to amend the derived Suspect Variables.

At " Module Impact Analysis Report " field, select the file that is of interest and double-clicking will list the source code and hi-light the occurrences of the Suspect Variables.

For example; selecting the "J162P30A.CBL" file is listed below.


The selected module will be listed with the Hunted (Suspect) Variables highlighted.

Additional outputs are not presented here, i.e. only modules with Lines containing suspect Hunted Variables, and / or only variables with their associate occurrence count.
Hunted (Suspect) Variables Usage

Listing of Hunted (Suspect) Variables usage. Base and derive. With their associate occurrence (hit) count and Suspect source code.

Hunted (Suspect) variables profile as related to the Source code.

Point the mouse to the vertical bar (suspect variable) and Double-click on left mouse
The selected line numbers of the source code will display.


Optionally performing VHUNT source code AutoCorrect (source code Renovation) .


Back to Top


Benefits:

VHUNT is an excellent tool for:
1. performing documentation/conversion and source code impact analysis, using the source code AutoCorrect feature will save valuable resources.
2. addressing software maintenance problems through understanding program variables ( or fields )

VHUNT is a:
1. Software Slicing Tool
2. Data Name Rationalization Tool
3. Source Code AutoCorrect Tool

VHUNT understands program variable dynamics and is THE ideal tool for addressing software maintenance/documentation problems
VHUNT
will save software maintenance valuable resource (time) by using VHUNT source code AutoCorrect (Code Renovation) feature.

Back to Top


Specifications

Technical Requirements

Minimum Hardware
Pentium Processor 16MB RAM , 50MB hard disk space
Software
VHUNT is available for Windows 95/98 , Windows NT

Back to Top



Copyright © 1997-2001 Computer performance Engineering, Inc. All rights reserved
Information in this document is subject to change without notice.
All information is believed accurate but not guaranteed.
Other products and companies referred to herein are trademarks or registered trademarks of their respective companies or mark holders.
webmaster@y2kok.com