Application onboarding with Fast Scan - validate the results on Documentation - V2

Validate using alerts and logs

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

Use the a variety of meansto check for alerts and consult log messages:

Missing dependencies/JAR file alerts

“Missing dependencies/JAR file” type alerts, are particularly important for the accuracy of the overall analysis results - for example if JAR files referenced in the source code (for example via a Maven pom.xml file) cannot be found then some objects will not be created, links will be missing, transactions will be incomplete etc. It is therefore crucial to check your configuration to avoid these alerts.

Validate using the Overview panel

Mon, 01 Jan 0001 00:00:00 +0000

Move to the Console screen if you are not already there:

Locate the Application and click it:

In the Application - Overview with Fast Scan page, you should now check the following sections:

Header section
Architecture Preview
Analysis Reports

Header section

If any missing dependencies are detected in your source code during the deep analysis (i.e. code that is calling another piece of code that cannot be found) a warning icon will be displayed. This should be fully investigated and corrected because it means that results may not be coherent. Clicking the warning triangle will direct you straight to the log file to see the missing dependencies alerts. See also Validate dependency configuration.

Validate technology specific settings

Mon, 01 Jan 0001 00:00:00 +0000

Move to the Console screen if you are not already there:

Locate the Application and click it:

Now click the Config option in the left hand panel. The Application - Config - Analysis screen is displayed showing a list of all technologies detected in the application and for which analysis configuration settings exist.

In the first instance, you should ensure that all technologies that you are expecting are listed in this screen. If any technologies are not listed, then there is likely an issue with the delivery of the source code and the source code should be rejected and redelivered.

Validate dependency configuration

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

This step involves checking that the dependencies settings are correct for all your technologies. Dependencies are configured at Application level for each technology and are configured between **individual Analysis Units/groups of Analysis Units.**Move to the Console screen if you are not already there:

Locate the Application and click it:

Now click the Config option in the left hand panel, expand each Technology and locate the Dependencies section:

Validate modules and content

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

Modules are used extensively in the CAST Imaging / CAST Dashboards and other CAST features as a means to configure analysis results for a given Application into meaningful groups or sets for display purposes. Indeed, objects that are not part of a module:

cannot be included in Transaction/Function Point****configurations
cannot be seen in the CAST dashboards
cannot be included in Architecture Models

The definition of modules for a given Application also impacts the accessibility and usability of application assessment results. Specifically, in the CAST quality and quantity model, the module is the smallest assessment entity. The definition of a module can improve the relevance of the analysis results by linking modules to development teams and application functional layers etc.

Validate Dynamic Links

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

Ensuring the correct discovery of transactions is a multi-step process that may be complex and time consuming for applications that are not supported out-of-the-box. At the core of CAST transaction discovery algorithm is the understanding of the links between objects discovered during the source code analysis of the target application.

CAST automatically sets up default Dependency Rules (see Validate dependency configuration) when the source code is delivered and set as the current version: the source code objects are scanned for references to other objects and links are created where appropriate. Not all links generated in this fashion are valid and their validation by the AIP Super Operator is therefore required.

Validate and configure transactions - optional

Mon, 01 Jan 0001 00:00:00 +0000

See the following pages:

Transaction and Function Point management

Validate in CAST Imaging

Mon, 01 Jan 0001 00:00:00 +0000

Move to the Console screen if you are not already there:

First check that the version status of your Application in the AIP Console - Application Management screen is Full analysis done - this means that the source code has been analyzed and uploaded to your CAST Imaging instance. Then use the CAST Imaging iconto take you direct to the specific Application data in CAST Imaging:

You can also access your CAST Imaging instance direct from Console using the option in the top right corner:

Validate Assessment Model - optional

Mon, 01 Jan 0001 00:00:00 +0000

Info

This action is not necessary if you are not using the CAST Dashboards.

At the core of CAST and extensions that are used during an analysis is the Assessment Model: a set of rules, sizing/quality measures and distributions in a hierarchy of parent Technical Criteria and Business Criteria that are used to grade an Application and to provide information about any defects (code violations) in the Application’s source code. The set of rules, sizing/quality measures and distributions are predefined and preconfigured according to established best practices, however, it is possible to modify some aspects in order to match your own environment, for example:

Validate in CAST Dashboards - optional

Mon, 01 Jan 0001 00:00:00 +0000

Info

This action is not necessary if you are not using the CAST Dashboards.

The easiest and quickest way to check the results of a snapshot generation is to open them and view your results. If you are using embedded Dashboards, you can click the icons highlighted below (no login required):

Alternatively, you can access direct to a specific application in the Engineering Dashboard using the icon available in the AIP Console - Application Management page. Move to the Console screen if you are not already there: