Impact Analysis

Assess the impact of a change in your code

Estimate what you should modify to accomplish a change.
Don't break your application after a change!

• If I change this variable, what is the effect on my code?
• If I add a parameter to a function, what else is affected?
• If a table or column is changed, which code should I update?

Review CRUD Operations in Your code
(Create, Read, Update, Delete)

Generate a CRUD matrix showing which programs access your data.

For instance, which DW or Procedures Create/Read/Update/Delete which Tables.

• Review dependencies between database and PB applications.
• Analyze the impact of changing your database Schema, for example changing a table definition or adding an index.
• Estimate software complexity and development efforts.
• Find out which table is never updated, deleted from multiple places, etc.
• Make sure every process has at least one input (R) and one output (CUD).

Explore Complex Chains of Calls

Display Call Trees: callers and callees for Functions and events.

Explore all possible execution paths.
Drill down in the code, click on referenced methods or variables to see their definitions.

Call trees help evaluate the effects of modifications to your code.

Improve Code Quality

Cleanup the code. Streamline maintenance efforts. Avoid unexpected behavior.

• Identify unused objects and remove some dead code.
• Find empty methods, duplicated objects, oversized or uncommented scripts.
• Calculate code metrics: lines of code, number of objects, methods, variables…
• Check naming conventions.
• Find objects that do not inherit from an ancestor etc.
• You can check your code against hundreds of rules

Code Comparison

Compare 2 versions of your DB or application:

• View differences in a container hierarchy.
• Drill down to find relevant changes.
• Filter changes for a given object, or object type: Userobject, Table, Procedure...
• Filter changes in a given PBL.
• Save “snapshots” of your code on a regular basis, and compare them anytime.
• And more...