CAST AIP 8.3.x Documentation
Page tree
Skip to end of metadata
Go to start of metadata

This documentation is no longer maintained and may contain obsolete information.

Page frame name:

FRAME_PORTAL_ASSESSMENT_VIEW

This view is designed to deliver information about a single Application necessary to identify situations in the source code where further investigation could prove useful. There is no certainty that each situation is the source of a real issue, but situations that have been identified are likely candidates.

This view requires access to at least one Application.

Layout

Left hand panel

Please see the section Left hand panel in Using the CAST Engineering Dashboard for more information about this.

Main window panels

Four main panels are available:

Current Overall StatusCurrent grade (see Threshold indicator colours in Using the CAST Engineering Dashboard) of the Application for the five main Business Criteria
Critical Violations by ModuleLists the Critical Violations for the five main Business Criteria for each Module in the parent Application: Total refers to the total number of violations for the current snapshot, Added refers to the number of new Critical Violations that have been detected in the current snapshot that did not exist in the previous snapshot and Removed refers to the number of Critical Violations that were present in the previous snapshot but no longer exist in the current snapshot (i.e. they have been resolved).
Compliance to Objectives

Shows Achievement Ratios in the current snapshot for only new and modified code and for the entire Application. These Achievement Ratios are based on the number of Critical Violations that are present, and are derived as follows:

  • To achieve 100% in the latest delivery, there must be no Critical Violations present in any new or modified code since the last snapshot
  • To achieve 100% in the entire Application, there must be no Critical Violations present in the entire Application's source code
  • If you introduce new Critical Violations in a future snapshot the ratio will stay the same - but you are reducing the quality
  • If you deliver clean code in a future snapshot, you will attain 100% for the delivery (only new and modified code) and a lower Achievement Ratio for the entire Application. This means you avoid being penalised for having intervened in a very poor quality Application.
Compliance to Objectives by Complexity LevelShows the location of the Critical Violations - i.e. whether they are in Low, Average, High or Very High complexity code. This allows you to determine how difficult the required corrections might be.
  • No labels