1.15.3

Resolved issues

New release to correct the following issues:

1.15.2

Resolved issues

New release to correct the following issues:

1.15.1

Resolved issues

New release to correct the following issues:

1.15.0

New features and updates

Architecture Studio

WEBI-6642 and WEBI-6643 - New selection criteria available for Architecture Models

Two new selection criteria have been made available when using the AIP Console - Architecture Studio - Model editor to create a custom model:

• Analysis Units
• Modules

Click to enlarge

WEBI-6822 - Dynamic Links are now highlighted when checking an Architecture Model for violations

When checking an Architecture Model for violations, the resulting list of violations will now include two new columns that highlight whether the violation of the model is based on a Dynamic Link (see Validate Dynamic Links):

• A tick in the Dynamic column indicates that the link is a Dynamic Link
• The Dynamic Info column displays information about the Dynamic Link:

  • Inference Engine - this indicates that the analyzer has inferred that this link exists based on its inference engine capabilities (i.e. link detection in variables, function parameters, function returns, and instance variables).

  • Grep-Validated - this indicates that the link has been created based on the names of objects and the link has already been validated as true
  • Grep-Not Reviewed - this indicates that the link has been created based on the names of objects and the link has not been validated yet

Click to enlarge

WEBI-6891 - Category of types have been added to Architecture Studio library

It is now possible to create sets for Architecture Models (in the AIP Console - Architecture Studio) based on specific categories of types that have been added to the Library of elements:

Click to enlarge

Transactions/Function Points

WEBI-6556 - Check content now available in the Transaction rule

It is now possible to check the content of a specific Transaction rule when Working in Free Definition mode:

Results are listed in a popup box:

WEBI-6566 - Assessing Function Points for empty Transactional Functions based on non-empty Transactional Functions

It is now possible to assess Function Points for all Transactional Functions for which the call graph does not reach a data entity nor an end-point based on existing Function Points that have been computed.

AIP Console determines the average number of nodes in the call graph of non-empty Transactional Functions corresponding to one DET. This ratio allows AIP Console to assign the number of DET to empty Transactional Functions, depending on the number of nodes in their associated call graph. The Function Point value will be then assessed based on that number of DET and with an FTR=1.

To achieve this, an option has been added in the Function Point Settings panel:

Click to enlarge

WEBI-6576 - Saving empty transaction objects

Transactions are more and more frequently used for purposes other than AFP/AEP counting. However, the concept of "Transaction" was until now strongly Function Points-oriented, meaning Transactions which did not access any Data Entity or End Point did not always have their objects saved. This new feature aims to change the way such Transactions are collected and managed.

All Transactions are still identified by their Entry Points, but objects that are part of Transactions which do not access any Data Entity or End Point can now be saved, whichever enhancement measure is selected for their application: EFP (Enhancement Function Points) or AEP (Automated Enhancement Points)  - see Application - Config - Enhancement Measure.

To achieve this, an option has been added in the Function Point Settings panel:

Click to enlarge

WEBI-6830 and WEBI-6831 - List of objects called by a transaction and their source code can now be viewed

It is now possible to view a list of objects that are called by a selected transaction and view the source code of these objects:

Click to enlarge

Click to enlarge

WEBI-6788 - Full Call Graph of a transaction is now available

It is now possible to view the Full Call Graph for a given transaction - see also Working with Transactions:

Click to enlarge

There are two views available:

Other features include:

GUI changes

WEBI-6720 - Maven repository settings now available in Administration Center

Settings for declaring the location of remote and local Maven repositories (which are crucial to ensure that any associated JAR files can be automatically discovered and that POM dependencies can also be located) are now available in the Administration Center. Out of the box in v. 1.15.x https://repo.maven.apache.org/maven2/ will be predefined. 

• You can remove an HTTP repository if you do not use it (use the trash icon).
• You can add additional repositories by clicking the ADD button.
• You can change the order of the repositories by dragging and dropping them in to the correct position (this is the order in which the repositories are scanned for artifacts).
• Local repositories can also be defined at AIP Node level using the <installation_folder>\AipNode\data\aip-node-app.properties file.

• Repositories discovered in the uploaded source code and any local repositories always take priority over any HTTP repositories defined in this new options panel.

WEBI-6779 - Proxy server configuration settings added to start-up wizard and Admin center

Proxy server settings have been added to the start-up wizard and the Administration Center, replacing the need to manually configure proxy settings in launch batch files. This therefore allows you to configure AIP Console and AIP Nodes to use a proxy server for all communication if one is implemented in your environment. You can choose to use:

• No Proxy
• Use system proxy settings
• Manual proxy configuration

Click to enlarge

WEBI-6799 - Status of CAST Storage Server/PostgreSQL instance assigned to each node now visible

The status of each CAST Storage Service/PostgreSQL instance associated to an AIP Node is now visible in Administration Center - Nodes:

Server up:

Server down:

WEBI-6751 - Source code delivery from folder in addition to ZIP file

It is now possible to deliver source code direct from a designated folder. This is in addition to the existing option to deliver source code as a ZIP file. A folder can be designated in the Administration Center - Settings - Source Folder Location panel:

Click to enlarge

When the option is configured, and you create a new version, you can choose to deliver direct from this designated folder:

Only one folder in the designated path can be selected, so please ensure that all source code is presented in one "root" folder (you can organise it however you need to underneath this root folder):

WEBI-6751 - Delivering source code for version Vn+1

When delivering source code for a new Version (where one exists already) the source code path of the previous version will be retained and will be pre-populated. You can choose to continue with this existing source code path, or use the DELETE option to remove it and add a new ZIP/source code:

WEBI-6908 - Option added to perform re-sync between CAST Management Studio and AIP Console

Currently AIP Console does not contain every single option and setting that is available in CAST Management Studio (Reference Patterns, Dynamic Link validation etc.), as such it is sometimes necessary to use CAST Management Studio on an AIP Node to perform one of these actions when working in Legacy application onboarding - Step-by-step onboarding mode.

If you change a setting in the CAST Management Studio that also performs an analysis/snapshot, or is also available in AIP Console, or if you remove a snapshot or other similar action, then AIP Console will become "desynchronised" because it does not know about the actions that have been performed. This new option has been made available to resolve this desynchronisation situation and bring AIP Console back up-to-date. See also Administration Center - Applications:

WEBI-5904 - Architecture Models and Transaction Rules - OR combination blocks now available

It is now possible to create OR combination blocks within Architecture Model Layers/Sets and in Transaction Rules:

Click to enlarge

For example:

Click to enlarge

Allow CAST to automatically collect anonymous statistical data

A new option has been added to the start-up wizard and the Administration Center to control the collection of anonymous usage data:

In order to provide an estimate of the time required to fully analyze a given application version, CAST needs to collect anonymous data relating to the volume of files to be analyzed, the performance/specification of the analysis server and the actual time taken to perform analyses and generate snapshots. The data collected by AIP Console will be stored by CAST on its CAST Extend server and will not contain any information that would allow the identification of any customer related information or application. The data stored by CAST is purely statistical and is related only to the size and duration of analyses and snapshot generation (an example of the data collected by CAST is available for download in .json format). The richer the database of information we hold, the more accurate the estimation will be.

By default, this option is enabled in the initial start-up wizard – in other words you are automatically opted-in and can disable the option if you prefer.

Miscellaneous

Detect .NET assemblies in the source code (BETA)

It is now possible to force AIP Console to attempt to detect the location of .NET framework system assemblies based on the source code you have delivered. This feature can be enabled per AIP Node using the following file (you will need to modify the configuration file on each node that will manage an Application containing .NET source code):

<installation_folder>\AipNode\data\aip-node-app.properties

Edit the file with a text editor and locate the following section:

# ==============
# .NET assembly configuration
# --------------
# Provide a list of locations to use for .NET Assemblies to be given to the code scanner
# Provide a full path separated by ';' like
#scanner.assembly.locations=C:/dotNet/v4.0;C:/dotNet/v4.5;C:/dotNet/v3.5
scanner.dotnet.assembly.locations=
scanner.detect.dotnet.assemblies=

Set scanner.detect.dotnet.assemblies= to true:

# ==============
# .NET assembly configuration
# --------------
# Provide a list of locations to use for .NET Assemblies to be given to the code scanner
# Provide a full path separated by ';' like
#scanner.assembly.locations=C:/dotNet/v4.0;C:/dotNet/v4.5;C:/dotNet/v3.5
scanner.dotnet.assembly.locations=
scanner.detect.dotnet.assemblies=true

If you have already manually added locations to the line scanner.dotnet.assembly.locations= there is no impact: any locations detected by AIP Console will be used in conjunction with those specified manually. See also Configuring source code delivery for .NET.

Improvements made to the Application import feature

Some improvements and bug fixes have been added to the Import an Application managed with CAST Management Studio into AIP Console feature. This feature is now officially supported.

Resolved issues

Known issues

None.

Delivered CAST Dashboard release

The AIP Console includes the following release of the CAST Health and Engineering Dashboards (see New customer installation for more information):