Page tree
Skip to end of metadata
Go to start of metadata

Validate the analysis results

After the analysis is complete, you can check and validate it. AIP Console provides various ways to validate the results.

Overview of Analysis

Details > Overview section provides you an overview of the application after it is processed by AIP Console. 

Overview of Analysis shows:

  • The number of versions of source code that are delivered and processed
  • The technologies that are detected from the source code automatically apart from the ones that you declared in the Inventory page
  • The number of Lines of Code and Function Points that are counted, if you have activated the software architecture.

Analysis Reports

Details > OVERVIEW > Reports provides you the Excel reports produced by specific extensions that were installed.

For example, the "Unanalyzed Code" report shows you the percentage of files that are delivered but not processed. If you want to get the details of these files, you can download the report.

You can add new extensions that provides you useful information on the analysis cycle.


The Details > LOGS tab shows the log files produced for all the executed steps.

A green check on the task item indicates the successful completion, and a red cross icon against the step indicates one of its steps failed. In addition, if an issue occurs during the execution of a step or  any files are missing, then you can see an exclamation mark as shown above.

If you want to review the logs, then click the View Log icon of that step.
For some logs, a summary shows you the list of errors/warnings and missing source files (with the number of times the files have been referenced), if any.
If required, you may download lists and logs.

Version Management

Versions page lets you to check the delivery contents.

  1. Click the view icon corresponding to the onboarded version.

The Version Management screen above shows the file types that are detected during the source code discovery. It also shows a few statistics like how many files have been added, removed, or modified. As it is the first delivery, everything is considered as "unchanged". You can compare the different files that have been discovered with the expected technologies to check if there are any missing files and/or extra files. Based on these numbers you can reject or accept the version.
You can download the table into an xml file to share the information with others.


The Extensions page, shows you all the extensions that are installed either by the source code discovery or through forced installation.

You can download new extension from Cast Extend, by using the AVAILABLE tab.


The Config page allows you to validate and refine the configuration.

  • The ANALYSIS tab shows different technologies that are discovered in the source code version. If you drill-down a specific technology, you will see settings that are common to all associated Analysis Units are automatically created. You can also go into each Analysis Unit to see specific settings and adjust them, if required.

  • The Modules tab allows you to define how modules must be created after the source code analysis is done.

  • The TOOLS tab allows you to load Dynamic Link Filtering Rules files to clean-up the application with unexpected dynamic links. If a Dynamic Link Filtering Rules file has been forced for all applications, you will see it here.

  • The Architecture tab is dedicated for software architecture check. Here, you can upload architecture models and compare them with the applications.

You can also review and edit the uploaded ones. To do that, click the View menu item in the ellipsis icon:

The model editor appears:

For more information refer AIP Console - Architecture
When you find the model you need, you can attach it to the application.

You can attach one model to multiple applications and multiple models to one application.

Once attached, an architecture model will be used each time a snapshot is computed. A quality rule will be generated and applied against the application. It will show the results in the Dashboards.

You can test the model immediately by using the Check menu item but the result will not be saved).

  • The ENHANCEMENT MEASURE tab is used to select the way enhancement size will be measured in each version.

The default is to use the methodology defined by the OMG.

The SECURITY DATAFLOW tab is for activating the User Input Security analysis. The dataflow analysis is only available for JEE and DotNet technologies.

There are many rules on security for various languages and frameworks that do not require the dataflow analysis.


The Transactions page shows you the number of transactions that were identified and the proportion of them that are not valid.

A transaction is an end-to-end call graph, starting from an entry point (very often it corresponds to a UI element) until data storages and/or API calls. An invalid transaction does not reach any end point. Normally, you should have a low percentage of invalid transactions.

Function Points

If you have an active license for Function Point counting in AIP, you will see the functional weight of your application in the Function Points page. You will also find here information on the amount of changes that have been delivered by the version you have just scanned.

The FP count should not be zero for Transactional Functions and for Data Functions. In addition to that the number of AEP for the functional part of the first version (AEFP) must be equal to the total number of FP.

Accessing Dashboards

After the completion of successful analysis, you can see the results in Dashboard.

You can access the dashboards directly from AIP Console as shown below.

A new web browser tab opens to display the Health Dashboard home page or the Engineering Dashboard application selection page:

You can also access the Engineering Dashboard directly from your application. To do that, use the More actions menu and select Open Engineering dashboard

You will be automatically connected to your application.


AIP Console reduces the number of technical and manual steps for the user, such as: 

  • The schema settings and source code delivery management are automated.
  • Administrator can configure the set up the strategy for Extensions and can define global settings that will be applicable for all the applications.
  • Many steps like registering an application, packaging a version, and computing a snapshot have been automated and are executed with minimum user interaction.

You can follow-up the work progression and get a quick overview on the application status when the analysis is in progress.

  • No labels