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

On this page:

Target audience:

CAST AI Administrator

Summary: this page lists:

  • impacts of changes made in CAST AIP 8.1.7 on Quality Model results
  • other impacts of changes made in CAST AIP 8.1.7
  • miscellaneous result changes

Introduction

Each CAST AIP release provides new features which improve the value of the platform and justify an upgrade. However, there are a number of changes or improvements which can impact the measurement results/grades:

  • New or improved Quality Rules to perform deeper analysis
  • Updates to the Assessment Model, e.g. changes to rule weights, severity or thresholds. This can be mitigated by using the "Preserve assessment model" option during the upgrade.
  • Improvements of the language analysis, e.g. more fine-grained detection of objects or links
  • Extended automatic discovery of files included in the analysis
  • Bug fixes to improve the precision of results
  • And, unfortunately, a new release may also introduce new bugs which may impact the results until they are discovered and removed

Below is a list of changes made to the current release of CAST AIP that are known to cause impacts to results. You can also consult Case Study - Measurement changes after upgrade for selected customer applications which provides a more detailed analysis based on a few sample applications.

Analyzing the root causes of impacts to measurement results/grades

The following is a general description of the steps that should be taken in order to compare pre and post upgrade results:

  • Step 1: Take a snapshot (including a source code analysis) with the previous release of CAST AIP before upgrading to the new release of CAST AIP
    • Check the list of applications to be analyzed, the list of files per application and list of SQL objects from the Analysis Service.
  • Step 2: Compare the source code in version 1 (before upgrade) with the source code in the new version 2 (after upgrade)
    • Compare the list of analyzed files, list of files per application and list of SQL objects between the two Analysis Services
  • Step 3: Compare the results of the application analysis and snapshot post upgrade. This can be done by comparing the snapshots available in the Dashboard Service to find the differences in:
    • Quality rules
    • Violations

    • Grades at Business Criteria level

    • Function Points

    • Transactions

    • Lines of code

  • Step 4: Compare the data functions and transactions across the source Analysis Service and the target Analysis Service post upgrade.

Impacts of changes made in CAST AIP 8.1.7 on Quality Model results post upgrade

ABAP

Avoid missing WHEN OTHERS in CASE statements - 7518

A bug has been discovered which has caused false positive violations of the Quality Rule. These false positive violations are due to the fact that the Quality Rule did not correctly handle the situation where the WHEN OTHERS clause was replaced by an ELSE clause in the ABAP source code. This bug has now been corrected and after an upgrade to CAST AIP 8.1.7 and the generation of a post upgrade snapshot, results may differ: the ELSE clause will be correctly handled and the number of false positive results will be reduced.

Multi-techno

A bug has been discovered which is causing the majority of Quality Rules to display a 100% variation in the CAST Engineering Dashboard > Investigation-quality model drilldown view, when looking at the results of a post upgrade (from CAST AIP 8.1.0 baseline) consistency snapshot. This bug has now been fixed and you therefore may see a change in the variation value (i.e. now correct) post upgrade to CAST AIP 8.1.7.

Oracle PL/SQL

Avoid SQL queries that no index can support - 7902

A bug has been discovered which meant that false positive violations of the Avoid SQL queries that no index can support - 7902 Quality Rule were being reported. This was due to the fact that IOT indexes were not correctly being taken into account by the CAST Database Extractor. This bug has now been fixed and after an upgrade to CAST AIP 8.1.7 , the re-extraction of data and the generation of a post upgrade snapshot, results may differ: the number of false positive results will be reduced.

Other impacts of changes made in CAST AIP 8.1.7

Mainframe - Cobol

A bug has been discovered which is causing warning messages to be listed in the analysis log file when a DD name contains an underscore, for example analyzing the following in a .COB file:

000440 SELECT EXTRACT-IN ASSIGN TO P327EXT_ZAZA 
000430 FILE STATUS IS IO-STATUS-CODE. 

Will produce the following error:

Analyzing Cobol Program TEST. 
Cannot resolve DD name 'ZAZA'.

This bug has now been fixed and after an upgrade to CAST AIP 8.1.7 and the generation of a post upgrade snapshot, results may differ - they will be more accurate and warning messages will be reduced.

ASP / Microsoft SQL Server

A bug has been discovered that is causing links between ASP/ASPX files and database objects to be erroneously created. The links are wrongly created between style properties in aspx/asp files and database tables that have the same name. For example, the following style  property "background-color: #FFFFFF;" will cause the creation of links to database tables called background and color (if they exist). This bug has now been fixed and after an upgrade to CAST AIP 8.1.7 and the generation of a post upgrade snapshot, results may differ - links between objects will be more accurate, which may also have a knock-on effect on on Quality Rule grades and Function Point transaction values.

Miscellaneous result changes

None.