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.2.11 on Quality Model results
  • other impacts of changes made in CAST AIP 8.2.11
  • miscellaneous result changes

The changes listed assume that an upgrade from CAST AIP 8.2.10 to CAST AIP 8.2.11 has taken place.

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.2.11 on Quality Model results post upgrade

JEE

Do not use auto wiring - 7714

A bug has been discovered which is causing the Quality Rule "Do not use auto wiring -7714" to report more failed checks than total checks. This bug has now been fixed and after an upgrade to CAST AIP 8.2.11, results may differ for this Quality Rule - there will be a reduction in the number of failed checks.

Mainframe

When using binary data items (COMP), then use the SYNCHRONIZED clause - 7938

A bug has been discovered which is causing the Quality Rule "When using binary data items (COMP), then use the SYNCHRONIZED clause - 7938" to be falsely violated. This bug has now been fixed and after an upgrade to CAST AIP 8.2.11, results may differ for this Quality Rule - there will be a reduction in false positives.

.NET

Avoid unreferenced Methods - 7908

A bug has been discovered which is causing the Quality Rule "Avoid unreferenced Methods - 7908" to be falsely violated by objects that are called by NET framework objects. These objects should not be part of the scope of this Quality Rule. This bug has now been fixed and after an upgrade to CAST AIP 8.2.11, results may differ for this Quality Rule - there will be a reduction in false positives.

All technos

Avoid too many copy pasted artifacts - 7156

A bug has been discovered which is causing the Quality Rule "Avoid too many copy pasted artifacts - 7156" to be falsely violated. This bug has now been fixed and after an upgrade to CAST AIP 8.2.11, results may differ for this Quality Rule - there will be a reduction in false positives.

Avoid artifacts having recursive calls - 7388

A bug has been discovered which is causing the Quality Rule "Avoid artifacts having recursive calls - 7388" to be falsely violated. This violation is the results of an incoherence in the analyzer where an ABAP method is identified (incorrectly) as calling itself. This bug has now been fixed and after an upgrade to CAST AIP 8.2.11, results may differ for this Quality Rule - there will be a reduction in false positives.

Other impacts of changes made in CAST AIP 8.2.11

JEE

Can not resolve warning in analysis log

A bug has been discovered which causes the following message to appear in the analysis log:

Can not resolve 'x' as type or variable in lambda expression 'y' from lambda expression.

This warning resulted in a missing link between the lambda expression and the called method, hence a transaction was incomplete. This bug has now been fixed, therefore after an upgrade to CAST AIP 8.2.11 and the generation of a post upgrade snapshot, you may see differences in results.

SAP / ABAP

Unresolved obejcts for ABAP keywords wd_this, wd_that and ANY

A bug has been discovered which is causing "unresolved" objects to be identified for the ABAP keywords "wd_this", "wd_assist" and "ANY". This bug has now been fixed, therefore after an upgrade to CAST AIP 8.2.11 and the generation of a post upgrade snapshot, these unresolved objects will no longer exist, nor will any links to these objects.

CAST Application Analytics and Engineering Dashboards

Discrepancy in number of violations displayed in both dashboards

When technical modules contained in a module share some objects and these shared objects have Quality Rule violations, then the violations on shared objects will be counted multiple times: if an object is shared N times then it will be counted as violation N times instead of one time. This issue manifests itself with a discrepancy between the number of violations reported in the CAST Application Analytics and Engineering Dashboards. This bug has now been fixed and after an upgrade to CAST AIP 8.2.11, results may differ in comparison with previous snapshots. However, the results are now accurate and the discrepancies between the dashboards will no longer be visible.

Miscellaneous result changes

N/A

  • No labels