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


Summary: this section provides an explanation of the Overview section for a given Application.

Introduction

The Overview section provides detailed information about the Application - information is derived from versions/analyses/snapshot, therefore the section will be empty if no versions/analyses/snapshots exist for a given Application. The section contains several "boxes" each providing different information. Each box is described in detail below.

Click to enlarge

Access the options

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

Locate the Application and click the Application name as highlighted below:

The Overview section will then be displayed:

Layout

The Overview section provides detailed information about the Application - information is derived from an analysis/snapshot, therefore the section will be empty if no analyses/snapshots have been run for a given Application. The section contains several "boxes" each providing different information. Each box is described in detail below.

Application ID card

This box provides a quick ID information about the application:

NameThe name of the application.
Domain

The name of the domain (see Administration Center - Applications) the application is assigned to. If the application is not assigned to a domain then '-' is displayed.

Number of versionsNumber of versions added for the application.
Onboarding dateThe date the application was created in AIP Console.
Last processing dateThe last time any action (job) was processed for the application.
CAST AIP version

The AIP Core release assigned to the application - this is determined by the AIP Node the application is managed on (see Administration Center - Nodes).

Analysis Configuration

Click to enlarge

This box provides information about how the analysis is configured:

Module Strategy

The module strategy selected for the application. This is set when adding a new version, and can also be modified once the version has been delivered in Application - Config - Modules. Possible values:

  • None (Manual Creation) 
  • Full content
  • Per analysis unit
  • Unassigned objects
Enhancement measure

The function point enhancement method selected for the application. This is configured in Application - Config - Enhancement Measure. Possible values: 

  • AEP (Automated Enhancement Points - default)
  • EFP (Enhancement Function Points)
Architecture model attachedNumber of architecture models attached to the application. Clicking the number will direct you to the Application - Config - Architecture panel where you can view a list of the models attached to the Application.
Security dataflow

Indicates whether the Security Dataflow option was enabled for this analysis and which technology it was enabled for. Possible values:

  • JEE
  • DOTNET
Advanced customization

Displays any advanced analysis customization options that have been configured for the Application - options are clickable and will take you direct to the relevant configuration panel. Possible values:

Version view

This section provides information about a specific version within the application. By default, data for the most recent version is displayed, however, you can manually select a different version:

State & Sizing

This section provides information about the current version selected in the drop down:

DateDate the version was created.
Status

Status of the current version. Possible values:

  • Delivered
  • Accepted
  • Not Delivered
  • Analysis ongoing
  • Analysis data prepared
  • Snapshot done
Lines of codeTotal number of lines of code counted during the snapshot. This value is not present if a snapshot has not been generated.
Functional sizeTotal Automated Function Points (AFP) identified in the Application during the snapshot. These details can also be seen in Application - Function Points. This value is not present if a snapshot has not been generated.
Enhancement sizeTotal Automated Enhancement Points (AEP) identified in the Application during the snapshot. These details can also be seen in Application - Function Points. This value is not present if a snapshot has not been generated.
Activated extensionsTotal number extensions that were installed for the current version.  Clicking the number will direct you to the Included tab in the Application - Extensions panel.

Architecture Map

This section provides information about the architecture of the application in two separate sections:

  • Source code architecture
  • Technologies

Source code architecture

This section displays, by default, a graphical representation of the Version's source code before an analysis is run. This view is built once the the Version has been delivered and the source code has been "discovered". The view's primary aim is to help check the completeness of the source code that has been delivered.

All links between blocks are based on supposition only. Final architecture from an analysis may be different.

Toggling the Before analysis switch will change the display to show a graphical representation of the source code when an analysis has been run (if an analysis has not been run, this display is not available).

  • Items marked in green confirm expected elements (technologies, frameworks, and links).
  • Items marked in blue denote an additional element that has been identified during the analysis.
  • Items in dashed white show an expected element that has not been found during the analysis.
  • Numbers correspond to the number of occurrences of the item that have been found.

Technologies

This section displays a treemap of the technologies have been discovered automatically by the AIP Console when a Version has been Set as the current version (this action is included in a Standard onboarding). The size of each rectangle/square is proportionate to the number of files discovered in each technology.

If the Set as current version action has not yet been executed, no "discovered" technologies will be displayed.

Frameworks

This section displays a treemap of the frameworks have been discovered automatically by the AIP Console when a Version has been Set as the current version (this action is included in a Standard onboarding). 

If the Set as current version action has not yet been executed, no "discovered" frameworks will be displayed.

Delivery Indicators

This section lists any indicators that are generated during the source code delivery for your version. They are designed to help you validate the delivery of the source code:

Click to enlarge

IndicatorSee list of available indicators below for more information.
ValueThe value generated for the given indicator. Can be a value, ratio or a percentage.
StatusStatus of the indicator - the more stars the better the results.
Remedy Action

Click to view a suggestion for how to improve the result in the next source code delivery. For example:

Details

Some indicators store results in a CSV file - click this option to download the CSV file. This can help you work out why a poor result has been produced, for example. CSV files are generated and stored on the node in:

%PROGRAMDATA%\CAST\AipConsole\AipNode\snapshot-indicator\{appGuid}\{snapshotGuid}

Where details are not available, the option will be greyed out.

Available Delivery Indicators

 Click here to expand...
Available inIndicator NameDescriptionStars/ThresholdDetails in CSV fileRemedy Action
v. ≥ 1.20Pending DMT alertsCount of alerts raised by the DMT during the source code delivery.
  • 3: = 0
  • > 0 
-

Alerts denote issues in source code delivery that can disturb or prevent the analysis and therefore that can impact the results. Review the source code delivery and package to resolve the issues. Go to the Versions page to see the list of alerts for the version:

  • in the Value column , if the number of alerts > 0, a link (e.g. See alerts) takes you directly to the alerts.

Reports

This section will display any report that has been generated during the analysis/snapshot. All reports can be downloaded using the option highlighted below:

Reports are primarily generated by the installation of an extension - for example, in the screenshot above:

Snapshot Indicators

This section displays a set of indicators for a given snapshot. These indicators are designed to provide basic information quickly so that the snapshot can be validated. The indicators are generated during the snapshot in a dedicated step:

This feature is enabled "out-of-the-box" in AIP Console ≥ 1.20.x. A new snapshot must be generated before any indicators are visible.

Click to enlarge

This drop down filters the Indicators in the list by category. By default, all categories are displayed in the list.


Choose the snapshot you would like to view indicators for. By default the most recent snapshot for the Application will be displayed.

Use this to search on the Indicator name.

This option enables you to download Microsoft Excel reports containing detailed information about the indicators in each category. A zip file will be generated, containing the relevant XLSX files - one per category. The file name used for the ZIP file and the XLSX files will contain a time stamp using the following format: <year><month><day>_<hour><minute><second>. The time stamp is generated when the Download report button is clicked.

Excel file report contents

  • The first sheet has information related to application name, snapshot name, snapshot date and category for which this report is generated. It also contains a summary for all the indicators belonging to that category i.e. name, description, thresholds, value, status, details, remedy action and justification.
  • The indicator value is computed along with status which is a star rating based on the thresholds of that indicator.
  • The details column contains the hyperlink to the details sheet of that indicator.

This option enables you to download Microsoft Excel reports containing detailed information about the indicators in each category:

  • If All Categories is selected (see option above) then a ZIP file will be downloaded containing the relevant XLSX files - one per category
  • If a specific category is selected, then a XLSX file will be downloaded.

The file name used for the ZIP file and the XLSX files will contain a time stamp using the following format: <year><month><day>_<hour><minute><second>. The time stamp is generated when the Download button is clicked.

Excel file report contents

  • The first sheet has information related to application name, snapshot name, snapshot date and category for which this report is generated. It also contains a summary for all the indicators belonging to that category i.e. name, description, thresholds, value, status, details, remedy action and justification.
  • The indicator value is computed along with status which is a star rating based on the thresholds of that indicator.
  • The details column contains the hyperlink to the details sheet of that indicator.
IndicatorSee list of available indicators below for more information.
Value

The value generated for the current snapshot. Can be a ratio or a percentage. For some indicators when only one snapshot exists, the value may be N/A, for example:

  • for indicators measuring the variation between two snapshots, the value will be N/A on the first snapshot
  • for the Large SCC count indicator the value can be N/A when no option is set in the Analysis schema to count the large SCC, so the indicator can not be calculated. 
Status

Status of the indicator - the more stars the better the results. Rolling the mouse over the stars will show the thresholds required to improve:

Justification

A free text field enabling you to enter a justification for the result. Free text is saved and is retained for the next snapshot that is generated. For example:

  • Do you agree?
  • Is the coverage as expected?
Justifications can only be edited for the most recent snapshot. If the snapshot selector is changed to a historic snapshot, the field becomes read-only.
Remedy Action

Click to view a suggestion for how to improve the result in the next snapshot. Any links are clickable.

Details

Some indicators store results in a CSV file - click this option to download the CSV file. This can help you work out why a poor result has been produced, for example. CSV files are generated and stored on the AIP Node in:

%PROGRAMDATA%\CAST\AipConsole\AipNode\snapshot-indicator\{appGuid}\{snapshotGuid}

Available Snapshot Indicators

 Click here to expand...
Available inIndicator NameDescriptionStars/ThresholdDetails in CSV fileRemedy Action
v. ≥ 1.20Artifacts in transactions variationVariation in percentage of artifacts involved in transactions compared to the previous snapshot.
  • 3: <=3%
  • 2: >3% and <= 5%
  • 1: >5% and <=7%
-Review the source code delivery with regards to the transaction configuration. If the value is not within the required range, then you should review the transactions configuration, identify entry and end points, identify missing links or provide justification on objects in technical side if they are actually valid. If they are invalid, then take necessary actions to include them as valid.
v. ≥ 1.20Objects not in Dashboard ServicePercentage of objects created in the Analysis Service that have not been transferred to the Dashboard Service. 
  • 3:  <=5%
  • 2: >3% and <= 10%
  • 1:>10% and <=15%
-Check the definition of user-defined modules to ensure that objects have not been missed. If they are required in Dashboard Service, then add them to a module.
v. ≥ 1.20Entry Points moved to technical part

Percentage of transactions that were considered as functional and that are now considered as technical. 

Associated details contain the transactions that led to TF and that does not now. 

  • 3: =0%
  • 2: >0% and <10%
  • 1:>=10% and <=20%
List of transactions that were in functional part and that are now in technical part.Check if links are broken during rescan due to change in source code or due to deleted artifacts.
v. ≥ 1.20Unexpected objects countPercentage of objects related to third-party libraries or that are generated by AIP analysis tools captured by modules.
 
These objects are identified by finding any of the following tags in their comments:
  • generated by, generated on, generated code
  • copyright, (c)
  • MIT License License: MIT
  • Apache license, licensed to Apache software foundation
  • General Public License, GPL, GNU
  • creative commons
  • 3: =0%
  • 2: >0% and <=5%
  • 1: >5% and <=10%
  • - : >10%
Associated details contain third-party objects and generated objects that have been captured by modules.Review suspicious objects and decide if they must be excluded from analysis scope.
v. ≥ 1.20Unreferenced objects variationVariation in number of not-referenced objects. 
such as followings: 
  • Classes
  • Code ( ASP) 
  • Forms  
  • Functions 
  • Includes
  • Interfaces 
  • JSP pages 
  • Modules
  • Files
  • 3:  <3%
  • 2: >=3% and <= 4%
  • 1:<5%
-

Justify the variation between 2 snapshots that could be due to added or deleted code which is unreferenced.

Another reason could be missing links or new links between objects when compared to previous version.

v. ≥ 1.20Incomplete Transaction VariationVariation in percentage of transactions that are incomplete, compared to the previous snapshot.
  • 3:  <=1% and >=-1%
  • 2: ( >=-2% and < -1%) Or (>1% and <=2%)
  • 1: (>-3% and < -2%) Or ( >2% and <3%) 
-

Check if entry points and/or end points have been added or removed in new version of source code due to added/removed files or have been added/removed manually.

Check if entry points and/or end points have been added or removed in new version of source code due to added/removed files or have been added/removed manually. You can also check if transaction call graphs have been impacted by added or missing links. 

v. ≥ 1.20Dynamic Links reviewedPercentage of Dynamic Links that have been reviewed. 
  • 3:    >=95%
  • 2: >=70  and  <95%
  • 1: >=50% and <70 
-

Check if Automatic Link Validator Extension is installed.

Review DL manually or define filtering rules to be applied at analysis time.   

v. ≥ 1.20Technologies not interacting with othersTechnologies not interacting with others
  • 3:  =0
  • 2: N/A
  • 1: N/A
List of technologies not interacting with othersReview source code delivery, analysis configuration, and the cause for potential missing links.
v. ≥ 1.20Technology wise LOC - No ChangePercentage of technologies involved in the application for which there is a lack of variation in LoC compared to the previous version.
Associated details contains the list of technologies with no changes in LOC.
  • 3: =0%
  • 2: >0% and < 20%
  • 1: >=20% and <30%
The list of technologies with no changes in LOC.Check if it is normal to not have any variation in LoC for the technologies involved in the application. This can denote an issue during the version delivery.
v. ≥ 1.19Databases variationIndicates whether the list of the databases that are accessed by the application has changed since the previous snapshot
  • : databases are the same in the 2 snapshots
  • : N/A
  • : N/A
  • - : one/some databases have been added, removed, or renamed
Databases that have been added and/or those that have been removed since the previous snapshot; databases that have been renamed or whose host instance has changed will be listed as added/deletedJustify the root cause of databases' list change.
v. ≥ 1.19LoC variation (technology level)Variation in the number of LoC by technology.Below, the % retained for rating is the biggest one (in absolute value) among all technologies whose number of LoC has changed:
  • : >=-20% and <=20%
  • : (>=-30% and <-20%) or (>20% and <=30%)
  • : (>=-40% and <-30%) or (>30% and <=40%)
  • - : <-40% or >40%, or a technology that was used in the previous snapshot isn't used any more
Per technology: whether it was added or removed, or is unchanged, along with the number of LoC in the previous and current snapshots, and the LoC variation value and percentageFind the root cause of variation and justify.
1. Check if new files are added/deleted in new version of source code for a particular technology.
2. Check if new version of Technology Extension is applied recently which contains some enhancements and capturing more lines of code or vice versa.
v. ≥ 1.19LoC variation (file level)Variation in number of LoC for source files.
Associated details contain the source files that have been added or removed since previous version.
  • 3: >=-5% and <=5%
  • 2: =5% or =-5%
  • 1: (>5% and <10% )  or (<-5% and >-10% ) 
Per file: whether it was added or removed, or is unchanged, along with the number of LoC in the previous and current snapshots, and the LoC variation value and percentage
  • Review the Release Notes to track changes in analyzers.
  • Find the root cause of variation and justify.
  • Check if new files are added/deleted in new version of source code
v. ≥ 1.19Technologies variationVariation in the number of technologies identified in the source code
  • : technologies are the same in the 2 snapshots
  • : N/A
  • : N/A
  • - : some technologies have appeared and/or some other have disappeared
Technologies that have appeared or disappeared since the previous snapshotJustify the change.
1. Check with Application team if they have added/removed a new technology.
2. Add appropriate extensions to analyze that newly added technology.
v. ≥ 1.19Large SCC countCount of Strongly Connected Components with more than a certain number of objects
  • 3: The 'GRAPH_SAVE_LARGEST_SCC_GROUP' option is set and no large SCC was found during computation of the Transactions' call graphs
  • 2: N/A
  • 1: The 'GRAPH_SAVE_LARGEST_SCC_GROUP' option is not set or its value is 0 (it is not known whether large SCCs exist or not)
  • - : The 'GRAPH_SAVE_LARGEST_SCC_GROUP' option is set and there exists at least one large SCC
    or
    The 'GRAPH_SAVE_LARGEST_SCC_GROUP' option is set but its value is not an integer >= 0
  1. The maximum number of objects allowed in an SCC before it is marked as large (the default value is 1000)
  2. The maximum number of large SCCs whose objects can be saved for further investigation
  3. How many SCCs had their objects saved during the last Function Point computation and what their sizes were

Review links and try to remove extra-links. For more details refers to Troubleshooting guides:

  1. Impact of SCC
  2. How to check
  3. Reduce SCC
v. ≥ 1.19AFP variationVariation in functional weight. 
Associated details contain the TF and DF that appeared, disappeared, or that have been modified since the previous snapshot. 
  • 3: >-5% and <5%
  • 2: =5% or =-5%
  • 1: (>5% and <15% )  or (<-5% and >-15% ) 
New TF, deleted TF, modified TF
New DF, deleted DF, modified DF
Check the transaction configuration rules. 
Check the source code delivery for new source files and new technologies. 
Check the source code delivery for missing source files and missing technologies. 
v. ≥ 1.19LoC per FP variationVariation in FP density with regards to source code size
  • 3: >-5% and <5%
  • 2: =5% or =-5%
  • 1: (>5% and <15% )  or (<-5% and >-15% ) 
-Review source code delivery and transaction configuration. 
Check if new components arrived in technical part of the application.
v. ≥ 1.19 Recreated functions Percentage of functions that disappeared and that reappeared. 
Associated details contain TF and DF that are recreated.
  • 3: >=0% and <=2%
  • 2:>2% and < 4%
  • 1:>=4% and <=5%
TF and DF that have been deleted and recreated.Check the transaction configuration rules. 
Check if objects have been deleted and then recreated. 
Check if server part has been correctly delivered and analyzed. 
v. ≥ 1.19New technical codePercentage of new objects that belong to the technical side of the application. 
Associated details contain new objects that are assigned to the technical part of the application.
  • 3: <5%* 3: <5%
  • 2: >=5% and < 10%
  • 1: >=10% and <=15%
New objects that are in technical part.Validate with application team if new code is functional or technical. 
Review the transaction configuration accordingly.
v. ≥ 1.19Quality rules variationVariation in number of quality rules. 
Associated details contain the quality rules that have been added or removed since the previous snapshot.
  • 3:  <=0
  • 2: >0 and <5
  • 1: >=5 and <10
QR that have been added or removed since last snapshotValidate new rules that have been added to the Assessment Model. This could be the consequence of an upgrade (AIP Core and/or extensions). 
Review the Release Notes to track changes.
Check if new files are added/deleted in new version of source code due to which added/deleted metrics are appearing.
v. ≥ 1.19Added/Deleted excluded objects countCount of objects that are excluded from quality rule violations and that present the "added/deleted syndrome". 
Associated details contain objects excluded from violations and that are also "added/deleted". 
  • 3:  <=0
  • 2: >0 and <2
  • 1: >=2 and <5
objects that are excluded from rule violations and seen as deleted and re-addedReview the list of deleted/re-added objects and investigate the root cause. 
v. ≥ 1.19Violation variation per rule

Variation in number of violations per rule, when more than 5 rules with at least 10 added or removed violations.
Associated details contain the list of rules with too much variation in number of violations.

  • 3: >-5% and <5%
  • 2: (>=5% and <10% ) or (>=-10% and <-5%)
  • 1: (>=10% and <15%) Or ( >-15% and <=-10%)
 List of rules with too much variation in number of violations

Check if new files are added/deleted in new version of source code due to which violations are added/deleted.

Check if new version of extension is applied during rescan and whether the new version includes some fixes related to quality for which the variation will be recorded.

v. ≥ 1.19AEFP/AEP variationVariation in ratio between AEFP and AEP. 
  • 3:  >-5% and <5%
  • 2: =5% or =-5%
  • 1: (>5% and <15% )  or (<-5% and >-15% )
-Validate with application team the goal of the version.
Check if new components or technologies have been added or if existing components or technologies have been removed
v. ≥ 1.19Added/Deleted objects variationVariation in number of objects that present the "added/deleted syndrome". Associated details contain "added/deleted" objects.
  • 3:  <=15%
  • 2: >15% and <20%
  • 1: >=20% and <=25%
Objects that have been added and deleted since the previous snapshot.

Check if new files are added/deleted in new version of source code

Check if same objects are coming added/deleted that may be due to the change in directory path between 2 versions.

v. ≥ 1.18Changeability variationVariation in grade for the
Changeability Business Criterion. 
  • 3: >-5% and <5%
  • 2: =5% or =-5%
  • 1: (>=5% and <15% ) or (<-5% and >-15% )
N/A

Check if new source files have been delivered.

Check if many changes have been done in the version. 

Justify the variation that could be due to an increase or decrease in violations for specific rules which could be because of code change or because of missing links or because of module definition.

v. ≥ 1.18Robustness variationVariation in grade for the Robustness Business Criterion. 
  • 3:  >-5% and <5%
  • 2: =5% or =-5%
  • 1: (>=5% and <15% )  or (<-5% and >-15% )
N/A

Check if new source files have been delivered.

Check if many changes have been done in the version. 

Justify the variation that could be due to an increase or decrease in violations for specific rules which could be because of code change or because of missing links or because of module definition.

v. ≥ 1.18Transferability variationVariation in grade for the Transferability Business Criterion. 
  • 3:  >-5% and <5%
  • 2: =5% or =-5%
  • 1: (>=5% and <15% )  or (<-5% and >-15% )
N/A

Check if new source files have been delivered.

Check if many changes have been done in the version. 

Justify the variation that could be due to an increase or decrease in violations for specific rules which could be because of code change or because of missing links or because of module definition.

v. ≥ 1.18Efficiency variationVariation in grade for the Performance Business Criterion. 
  • 3:  >-5% and <5%
  • 2: =5% or =-5%
  • 1: (>=5% and <10% )  or (<-5% and >-10% )
N/A

Check if new source files have been delivered.

Check if many changes have been done in the version. 

Justify the variation that could be due to an increase or decrease in violations for specific rules which could be because of code change or because of missing links or because of module definition.

v. ≥ 1.18Security variationVariation in grade for the Security Business Criterion. 
  • 3:  >-5% and <5%
  • 2: =5% or =-5%
  • 1: (>=5% and <10% )  or (<-5% and >-10% )
N/A

Check if new source files have been delivered.

Check if many changes have been done in the version. 

Justify the variation that could be due to an increase or decrease in violations for specific rules which could be because of code change or because of missing links or because of module definition.

v. ≥ 1.18TQI variationVariation in grade for the TQI index. 
  • 3:  >-5% and <5%
  • 2: =5% or =-5%
  • 1: (>=5% and <10% )  or (<-5% and >-10% )
N/A

Check number of new technologies and new objects. 

Check new rules. 

Justify the variation that could be due to an increase or decrease in violations for specific rules which could be because of code change or because of missing links or because of module definition.

v. ≥ 1.18Critical Violations variationVariation in number of critical violations. 
Associated details contain the critical violations that have been added or removed since the previous snapshot. 
  • 3:  >-5% and <5%
  • 2: =5% or =-5%
  • 1: (>=5% and <10% )  or (<-5% and >-10% ) 
Critical violations added/removed

Check if new rules have been added to the Assessment Model. 

Check if new source files have been delivered.

Check if new objects have been created.

Justify the variation that could be due to an increase or decrease in violations for specific rules which could be because of code change or because of missing links or because of module definition.

v. ≥ 1.18Excluded objects variationVariation in number of objects that are excluded from quality rule violations. 
Associated details contain the objects that have been excluded from violations. 
  • 3:  >-5% and <5%
  • 2: =5% or =-5%
  • 1: (>=5% and <15% )  or (<-5% and >-15% ) 
List of excluded objectsIf the variance is +/-5%, then check the excluded objects list and verify if these are real candidates for exclusion. 
v. ≥ 1.17Artifacts in transactionsPercentage of artifacts involved in transactions.  Associated details contain artifacts that are not involved in any transactions.
  • 3: >=50%
  • 2: <50% and >=40%
  • 1: <40% and >=30%
List of artifacts not involved in transactionsReview the source code delivery with regards to the transaction configuration. If percentage not within required range, then AIA needs to review the transactions, identify entry/end points, identify missing links or provide justification on objects in technical side if they are actually valid. If invalid, then take necessary actions to include them as valid.
v. ≥ 1.17Complete Transactions with only end pointPercentage of complete transactions with no data entity (only end points). Associated details contain the complete transactions that do not access any data entity.
  • 3: <=30%
  • 2: >30% and <=50%
  • 1: >50% and <=70%
List of complete transactions that do not access any data entity but only end pointsCheck if data storage part has been delivered. If yes, then check if it is expected to have transactions with no access to these data entities.
v. ≥ 1.17Data entities used by transactionsPercentage of data entities accessed by transactions. Associated details contain list of data entities not access by any transaction.
  • 3: >=90%
  • 2: <90% and >=70%
  • 1: <70% and >=50%
List of data entities not accessed by any transactionReview the source code delivery with regards to the transaction configuration. Check missing links and validate with application team if it is normal these data entities are not accessed by any transactions.
v. ≥ 1.17Incomplete transactionsPercentage of incomplete transactions (that do not access any data entity and end point). Associated details contain transactions that does not access any data entity or end point.
  • 3: <= 10%
  • 2: <= 30% and > 10%
  • 1: <= 40% and > 30 %
List of incomplete transactionsReview data entities and associated transaction configuration rules. Investigate the incomplete transactions and justify if they are valid incomplete or not. If possible, add custom end points to make the incomplete transactions valid. 
v. ≥ 1.17AEFP/AEP (known as "Part of functional enhancement" in v. ≤ 1.18)Percentage of AEP that are related to the functional part of the application. 
  • 3: >= 70%
  • 2: >= 50% and < 70%
  • 1: >= 30% and < 50%
N/AValidate with application team the goal of the version.
Check if new components or technologies have been added or if existing components or technologies have been removed. 
Add new entry/end points to cover isolated objects in transaction.
Check the list of Technical Points and justify if those are actually technical objects. 
v. ≥ 1.17Programs/Classes in transactionsPercentage of programs and classes involved in transactions. Associated details contain programs and classes that are not involved in any transactions.
  • 3: >=  50%
  • 2: >= 30% and < 50%
  • 1: >=10% and < 30%
List of containers not involved in transactionsReview the source code delivery with regards to the transaction configuration. 
If the value is not within the required range, then you should review the transactions configuration,
Identify entry and end points, identify missing links or provide justification on objects in technical side if they are actually valid.
If they are invalid, then take necessary actions to include them as valid.
v. ≥ 1.17TF / DF weight RatioRatio between Transactional Functions weight and Data Functions weight. Associated details contain DF that are not involved in any TF. 
  • 3: >=2 and <4
  • 2: ( >=1 and <2 )  or (>=4 and <5)
  • 1: (>0 and <1) or (>=5 and <6)
List of DF that are not used by any TF.Check transaction configuration rules. Review incomplete transactions if any. Review DF that are not used by any TF. 

Technical information about Snapshot Indicators

  • When a snapshot is deleted all the indicators for the snapshot along with the generated CSV files are deleted. In addition, the consolidation action launched when a snapshot is deleted will only deal with Dashboard schema indicators for the next two snapshots if they exist. During consolidation, any justification text is retained for each indicator.
  • Snapshot Indicators are also deleted when a version and an application are deleted.

Logging information about Snapshot Indicators

 Click here to expand...

Log for the Indicator step:

Click to enlarge

Log for consolidating indicators in delete snapshot step:

Click to enlarge

If one of the indicators fails, AIP Console logs the error and continues computation for the next indicator:

Click to enlarge

Click to enlarge

If the indicator step fails we log the error and proceed to the next step:

Click to enlarge

Similarly if consolidating indicators fail for a reason we log the error and delete snapshot step is completed successfully. If any indicators are skipped during the process, the log will include information about the reason the indicator has been skipped:

  • <enabled>false</enabled> : Indicator xx skipped because it is disabled. 
  • <needFplicense>true</needFplicense> : Indicator xxx Skipped because it needs the FP license.
  • <enhancementMeasure>EFP</enhancementMeasure> : Indicator xx skipped because it needs enhancement measure EFP 

  • <enhancementMeasure>AEP</enhancementMeasure> : Indicator xx skipped because it needs enhancement measure AEP

  • No labels