Health Dashboard - Available information - Automated Enhancement Point section
Summary: An explanation of the Automated Enhancement Point (AEP) section of the Health Dashboard, the tiles available and the drill down options.
Introduction
The Health Dashboard provides AutomatedandEnhanced Function Point information about your Application accessible from the “AEP” tile in the Automated Enhancement Point section:
Depending on the enhancement Function Point counting mode that was used to generate the current snapshot (AEP or legacy EFP - see Measures used to calculate enhancement Function Pointsin **CAST OMG-compliant Automated Function Points**and also Application - Config - Enhancement Measure in the AIP Console documentation for information about how to switch between the two measures), the information displayed in the tile and the drill down behaviour will differ.
AEP measure enabled
Tile data
The AEP tile will show the total number of Automated Enhancement Points found in the current application:
Drill down behaviour
Clicking the tile will drill down into the Size Indicators section with the Enhancement Size filter ticked to provide the AEP data. A graph shows the AEP value over successive snapshots. Roll over the snapshot point in the graph to view more details:
If you require Automated Function Point data, you can add the Functional Size filter:
By default the last 12 months of data is displayed, but you can choose a different time period if required:
Further information
More detailed information about the AEP data is provided underneath the graph:
Size of the enhancement of the most recent software application release, compared with previous
Enhancement Distribution
Distribution of modifications between two points of measure. Distribution is sized in Automated Enhancement Points (AEP) and presents the functional and technical share of the activity:
Impact
The percentage value gives you an overall view about whether changes are impacting a large volume of transactions within the application. This percentage is the number of changed transactions out of the total number of transactions in the application. Impacted transactions include new transactions as well as modified transactions.
The total number of transactions and the total number of impacted transactions computed for Automated Enhancement Points (AEP) purposes also contain DELETED transactions, because DELETED transactions impact the results of AEP.
Enhancement Type
Breakdown of the changes into three categories (added, deleted, modified):
Quality of the enhancement of the most recent software application release, compared with previous release
Violation introduction
Focus on new (added) Critical and non-critical Violations in the current snapshot for the Application:
Violation removal
Focus on removed (deleted) Critical and non-critical Violations in the current snapshot for the Application:
Violation density
A quick summary of the Critical and non-Critical violation density - i.e. whether it has increased or decreased:
Complexity of the enhancement of the most recent software application release, compared with the previous
Complexity distribution
The complexity of the components impacted by the changes done in the version. The complexity of the enhancement is presented through absolute values showing the impact on the functional part compared to the technical part.
Reusability in transactions
The reusability in transactions denotes the impact of changing a few artifacts with regards to the impact on the total number of transactions.
Legacy EFP measure enabled
When the EFP measure is enabled, the AEP tile will show no data since the tile is dedicated to AEP data:
When a tile shows N/A no drill down is possible, therefore to access the EFP/AFP data, you will need to click the Technical Size tile on the application home page (or any other tile if Technical Size is not available) and ensure you are working in the Size Indicators tab:
Ensure either the Functional Size or Enhancement Size filter is selected:
Click the indicator for the snapshot you want to view:
The EFP/AFP data will then be displayed on screen:
| Functional Size selected | |
| Enhancement Size selected |
Export to Microsoft Excel for legacy EFP/AFP data
Out of the box, icons allowing the export of Enhanced and Automated Function Point data are available, however they are not activated when using standalone Engineering or Health dashboard deployments (when using the combined CAST-Health-Engineering WAR file - see Standalone Health Dashboard deployment, the icons are active). However, after a configuration change (please see Configuring export of AEP and EFP data from Health Dashboard to Microsoft Excel or CSV using a standalone Health Dashboard), the icons become active allowing an export to Microsoft Excel file:
When you click the icon, you will be prompted to either Open or Save the file depending on your browser. Clicking Open will launch the program associated with the .xlsx file type (usually Microsoft Excel), while clicking Save will prompt you to choose a location to store the file for future use. The Excel file contains detailed about how the Enhanced/Automated Function Point value has been derived:
Note that when exporting the Enhancement Size, AEFP (Automated Enhancement Function Points) and AETP (Automated Enhancement Technical Points) data are both provided. This is done using two different tabs in the Excel spreadsheet:
- Functional Part = AEFP
- Technical Part = AETP
XLSX column headings
The following columns are displayed in the XLSX file:
Functional Size data (i.e. AFP)
| Columns | Description | Type | Occurs |
|---|---|---|---|
| Element Type | Whether this object is a Data Function or a Transaction | String | 1 |
| Function Name | Name of the Function | ||
| Object Name | Full name of the object | String | 1 |
| Nb of FPs | Number of Function Points for this OMG-compliant Automated Function Points Function | Integer | 1 |
| Type | OMG-compliant Automated Function Points Function type | String | 0..1 |
| DET | Data Element Type | Integer | 0..1 |
| RET | Record Element Type | Integer | 0..1 |
| EIF | External Interface File | Integer | 0..1 |
| ILF | Internal Logical File | Integer | 0..1 |
| FTR | File Type Referenced | Integer | 0..1 |
| Object Type | Type of this OMG-compliant Automated Function Points Function | String | 1 |
| Module name | Name of a functional module containing this OMG-compliant Automated Function Points Function | String | 1 |
| Technology | Technology to which this OMG-compliant Automated Function Points Function belongs | String | 1 |
Enhancement Size (CISQ/OMG) data (i.e. AEP)
Functional Part tab
| Columns | Description | Type | Occurs |
|---|---|---|---|
| Element Type | Whether this object is a Data Function or a Transaction | String | 1 |
| Function Name | Name of the Function | String | 1 |
| Object Name | Full name of the object | String | 1 |
| Nb of FPs | Number of Function Points for this OMG-compliant Automated Function Points Function | Integer | 1 |
| Complexity Factor | OMG-compliant formula to calculate complexity | Integer | 1 |
| Updated Artifacts | Number of artifacts that have been updated | Integer | 1 |
| Object Type | Type of this OMG-compliant Automated Function Points Function | String | 1 |
| Module name | Name of a functional module containing this OMG-compliant Automated Function Points Function | String | 1 |
| Technology | Technology to which this OMG-compliant Automated Function Points Function belongs | String | 1 |
Technical Part tab
| Columns | Description | Type | Occurs |
|---|---|---|---|
| Object id | Objects ID | Integer | 1 |
| Object name | Full name of the object | String | 1 |
| Object name location | Object’s parent | String | 1 |
| Object type | Type of object | String | 1 |
| Object status | Status of object: added, deleted, updated | Integer | 1 |
| Effort complexity | See | Integer | 1 |
| Equivalence ratio | See | Integer | 1 |
| AEP | Automated Enhancement Points value | Integer | 1 |
Exporting to CSV instead of XLSX
By default, the export file format is set to Microsoft Excel (.xlsx). However, it is possible to change this to .csv if you prefer - see exportformat in Health Dashboard json configuration options. If you set the export to CSV please take note that by default, the semi-colon (;) is used as the delimiter value for the CSV file. You may need to change the List Separator value in Control Panel > Region and Settings > Formats tab > Additional Settings in order for the CSV file to display correctly:
