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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

On this page:

Summary: CAST AIP 8.3.1 introduces a number of features and changes as listed below.

Upgrade

CAST Server Manager to be used instead of the CAST Update Tool

Changes have been made to CAST Server Manager in an effort to provide one tool that will meet all upgrade requirements: CAST AIP core upgrade and extension upgrade actions are now available for CAST AIP schemas installed with the Combined Installation option through one single menu option:

As such, the CAST AIP upgrade guide has been modified to take into account these changes, in particular:

  • Step by step upgrade process has been modified and no longer discusses the use of the CAST Update Tool (CUT) to perform the upgrade
  • Step by step upgrade process - workaround method has been added. This page presents the legacy method described in CAST AIP 8.3.0 for performing a CAST AIP core upgrade via the CAST Update Tool (CUT) and CAST Server Manager to upgrade extensions. The instructions in this page should only be followed if you have difficulty running an upgrade as described in Step by step upgrade process.

Upgrade batch file

The upgrade batch file (see Automating the CAST AIP Upgrade process) should not be used to upgrade to CAST AIP 8.3.1. The script contains known bugs which are being fixed for a future release.

Extensions

Information about extensions shipped with CAST AIP 8.3.1 and installed as part of the upgrade/new installation

As part of CAST's drive to improve and speed up the frequency of software releases, a process of "externalizing" the source code delivery and analysis capabilities of CAST AIP has begun in CAST AIP 8.3.x. To this end the following items (official CAST AIP extensions) are shipped with CAST AIP 8.3.1 and are installed automatically as part of the upgrade process and also when installing new CAST AIP "triplets". Please ensure that you read the documentation for the these extensions and take note of any Known Issues that may occur.

Snapshot management

When deleting a snapshot (whether through the CAST Management Studio GUI or CLI (DeleteSnapshotsInList, DeleteSnapshotsWithinRange)), when changing the capture date on a snapshot (through the CAST Management Studio GUI), when performing a consolidate action on an older snapshot (through the CAST Management Studio GUI) or setting the capture date prior to existing snapshots for a snapshot (whether through the CAST Management Studio GUI or CLI), it is no longer necessary to perform a snapshot re-consolidation action to update data:

ActionNew behavior

Remove one or multiple older snapshots

If you remove an older snapshot (i.e. not the most recent) then the next snapshot will be updated:

  • delta and AEP/EFP metrics are recalculated, and the post process procedures that update schema tables required for dashboards are relaunched.
  • new data is also pushed to the associated Measurement Service schema (if one is associated to the Management Service schema for the Application).

Update Functional Date

If you update the functional date now, three snapshots will be updated:

  • the snapshot you updated
  • the previous next snapshot 
  • the new next snapshot

For these three snapshots, CAST AIP will:

  • recalculate the delta and AEP/EFP metrics, the post process procedures are launched
  • new data is also pushed to the associated Measurement Service schema (if one is associated to the Management Service schema for the Application).

If the snapshot you updated was already the latest, source code and object properties will be removed (as they no longer match with the new latest snapshot).

Consolidate an older snapshot

If you reconsolidate an older (i.e. not the most recent), then the next snapshot will be updated:

  • delta is recalculated, and the post process procedures that update schema tables required for dashboards are relaunched.
  • new data is also pushed to the associated Measurement Service schema (if one is associated to the Management Service schema for the Application).
Snapshot generation with a capture date that is before an existing snapshot

If you generate a snapshot, with a capture date that is before an existing snapshot, the existing snapshot will be updated:

  • delta is recalculated, and the post process procedures that update schema tables required for dashboards are relaunched.
  • new data is also pushed to the associated Measurement Service schema (if one is associated to the Management Service schema for the Application).

CAST Application Analytics / Engineering Dashboards / Rest API

User authentication / data authorization

An error in the example given in the roles.xml file (delivered with CAST Application Analytics / Engineering Dashboards and the Rest API) for configuring roles for LDAP groups has been corrected. In addition, the documentation has been updated as a result. The following pages have therefore been updated:

CAST Application Analytics Dashboard

Configurable Technical Size indicators

It is now possible to customize the list of Technical Size indicators (Number of Critical Violations, Number of Code Lines, Number of Files etc.) that are displayed for the drill down page available at Application level for the Technical Size tile (click to enlarge):

See CAST-AAD - Tile management for more information.

CAST Application Engineering Dashboard

Reset language option

The top user menu now has an additional drop down menu item called "Reset language". This allows a user to change the language of the text items in the dashboard, providing an administrator has configured the language:

See:

Violation details section

A new section has been added to the Source Code display called Violation details to display Violation Name along with the values of the Violation Details (i.e the "Associated Values"). See CAST Application Engineering Dashboard - CAST AED.

Change in behaviour of Risk Introduced tile

The way the Risk Introduced tile behaves has changed:

  • Clicking the tile will take you directly to the Health Factor in the Quality Investigation view, however, the Quality Investigation view will only show added and removed violation information. Any Health Factor, Technical Criterion or Quality Rule where the number of Added and/or Removed violations is 0, will not be visible. A message will reflect this:

  • If no added or removed Critical Violations or Violations are present in the snapshot, then the tile will display no data and will not be clickable:

CAST Management Studio

CLI

ImportAssessmentModel

The ImportAssessmentModel option introduced in CAST AIP 8.3.0 has been modified to remove the constraint on the naming of the .PMX file to be imported (there is now no constraint). See Automating CAST Management Studio tasks.

ConfigurePlatformPreferences

  • It is now possible to use this option to update the license key (licenseKey option) and the logs folder (jobLogRootPath option) with the CLI even if they have been set either via the Startup wizard or via the CLI already. See Automating CAST Management Studio tasks.
  • Two new parameters have been added for this command line option to enable the automatic configuration of the LISA and LTSA folders - see Automating CAST Management Studio tasks:

    • storageWorkingPath (for LISA)
    • temporaryWorkingPath (for LTSA)

CAST Architecture Checker

Log file naming and path changes

A change has been implemented with regard to the naming and path of the CAST Architecture Checker log file:

  • the log file will be named "AC-<date>-<time>.log.txt", where <date> is of the form "YYYYMMDD", and <time> of the form "HHMMSS"
  • the log file will by default be located in %ALLUSERSPROFILE%/CAST/CAST/Logs, or in the folder specified by CAST_LOG_ROOT_PATH if that variable has been defined in the flat's CASTGlobalSettings.ini file.

In previous releases of CAST AIP, the CAST Architecture Checker log files:

  • were named "ArchitectureChecker.<date><time>.log.txt" where <date> was of the form "YYMMDD", where <time> was of the form "HHMMSS"
  • were located in the CAST temp file directory

CAST Transaction Configuration Center

Log file naming and path changes

A change has been implemented with regard to the naming and path of the CAST Transaction Configuration Center log file:

  • the log file will be named "TCC-<date>-<time>.log.txt", where <date> is of the form "YYYYMMDD", and <time> of the form "HHMMSS"
  • the log file will by default be located in %ALLUSERSPROFILE%/CAST/CAST/Logs, or in the folder specified by CAST_LOG_ROOT_PATH if that variable has been defined in the flat's CASTGlobalSettings.ini file.

In previous releases of CAST AIP, the CAST Transaction Configuration Center log files:

  • were named "TransactionConfigurationCenter.<date><time>.log.txt" where <date> was of the form "YYMMDD", where <time> was of the form "HHMMSS"
  • were located in the CAST temp file directory

Log: Function Points Computation report - includes Transaction Graph Adjustment information

The Function Points Computation report (which is part of the log produced when the "Compute" action is run) now contains information about the use of the Transaction Graph Adjustment feature:

First, these lines display the current statuses of whether Standard and/or Custom TF adjustments are enabled or disabled:

  • Standard TF graph adjustment : enabled or disabled
  • Custom TF graph adjustment : enabled or disabled

Then, if there is at least one link which has been adjusted, the counts of deleted, inverted, and added links are shown:

  • Number of deleted adjusted links : 0 or # of deleted adjusted links
  • Number of inverted adjusted links : 0 or # of inverted adjusted links
  • Number of added adjusted links : 0 or # of added adjusted links

New Show Rules option in the GUI

A new "Show Rules' option has been added to the GUI to display a list of rules that the selected object matches:

This option can be accessed from the Transaction Configuration node when using the "Generate set..." buttons:

  • No labels