UTILITY 2000
|
Specifications
|
Tool Types |
|
|
|
|
|
- Application Re-engineering
|
|
|
|
Tool Selection Criteria |
|
|
C, C++, Visual Basic 3,4,5, Java, PowerBuilder, Access and Excel, ADA* and Fortran*
|
- Environment Compatibility
|
|
|
Uses built-in date-related functions specific to the programming language.
|
|
Accuracy is enhanced by fuzzy logic. Utility 2000 provides a list of variables found in the
source code, enabling the user to search for variables such as "Pay
period".
|
|
The user may add or remove custom search patterns.
|
|
Full support provided with the software.
|
|
|
|
Mostly point and click actions with typing for some code editing.
|
|
Negotiable based on LOC or extent of use for site/enterprise license.
|
Tool Impact Analysis Criteria |
|
- Finds date-related fields
|
|
|
|
|
|
|
|
|
|
- Traces impacts across source, data,
documentation
|
|
- Supports common languages across
environments
|
|
- Provides customizable search patterns for flexibility
|
|
- Offers easy GUI for user friendliness
|
|
- Integrates well with code renovation
|
|
Tool Code Renovation Criteria |
|
- Minimizes required keystrokes
|
|
- Groups related lines of code
|
|
- Allows automatic global changes
|
|
- Permits manual local changes
|
|
- Supports all business rules
|
|
- Generates file converters and bridges
|
|
- Supports common languages across
environments
|
|
|
|
- Integrates well with impact analysis
|
|
|
|
Other features included in UTILITY 2000:
Audits all work done
with user name, time and date.
Records all changes in a database, enabling retracing of steps in the case of a test failure.
Full reporting features, with totals of applications scanned, work completed and changes made.
* Available in February
1998.
|