Application - Legacy Overview

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

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)

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

• JEE
• DOTNET

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:

• Dynamic link rules
• Update application schema
• Explicit filter in modules (see Filters under User Defined Modules)

Status of the current version. Possible values:

• Delivered
• Accepted
• Not Delivered
• Analysis ongoing
• Analysis data prepared
• Snapshot done

The CAST Extension Console has used to process the file. Note that some primary file extensions may be listed as processed with multiple extensions. For example the .js file extension will appear twice:

• once with com.castsoftware.html5 
• once with com.castsoftware.jee.

Click to download the report as a .CSV file. When opened in Microsoft Excel (or equivalent), two tabs are available:

• Source Files Analysis Summary : displays an overview, i.e. the same data available in Console UI.
• Details: displays a list of files with their primary file extension, their technology, the list of CAST extensions that support the technology, and the status (excluded, analyzed, not analyzed).

• 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.
  

These two values are generated during the snapshot/analysis. These will help understand what information the report is providing. For example, for the ALV Report:

• Automatic validation of dynamic links : 87.5% > this number indicates the percentage of dynamic links that have automatically been validated.
• Number of remaining link to manually validate: 1 > this number indicates that there is only one dynamic link to manually inspect.

• <4000 = 3 stars
• >=4000 and < 4500 = 2 stars
• >=4500 and < 5000 = 1 star

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%

• 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%

• 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.

• 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. 

• 3:    >=95%
• 2: >=70  and  <95%
• 1: >=50% and <70 

• 3:  =0
• 2: N/A
• 1: N/A

• 3: =0%
• 2: >0% and < 20%
• 1: >=20% and <30%

• 3 : databases are the same in the 2 snapshots
• 2 : N/A
• 1 : N/A
• - : one/some databases have been added, removed, or renamed

• 3 : >=-20% and <=20%
• 2 : (>=-30% and <-20%) or (>20% and <=30%)
• 1 : (>=-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

• 3: >=-5% and <=5%
• 2: =5% or =-5%
• 1: (>5% and <10% )  or (<-5% and >-10% ) 

• 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

• 3 : technologies are the same in the 2 snapshots
• 2 : N/A
• 1 : N/A
• - : some technologies have appeared and/or some other have disappeared

• 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

• 3: >-5% and <5%
• 2: =5% or =-5%
• 1: (>5% and <15% )  or (<-5% and >-15% ) 

• 3: >-5% and <5%
• 2: =5% or =-5%
• 1: (>5% and <15% )  or (<-5% and >-15% ) 

• 3: >=0% and <=2%
• 2:>2% and < 4%
• 1:>=4% and <=5%

TF and DF that have been deleted and recreated.

Note: this is different from Added/Deleted situation in the same snapshot which is when the object ID of the TF/DF has changed because of change in the path of the object for example.

• 3: <5%* 3: <5%
• 2: >=5% and < 10%
• 1: >=10% and <=15%

• 3:  <=0
• 2: >0 and <5
• 1: >=5 and <10

• 3:  <=0
• 2: >0 and <2
• 1: >=2 and <5

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%)

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.

• 3:  >-5% and <5%
• 2: =5% or =-5%
• 1: (>5% and <15% )  or (<-5% and >-15% )

• 3:  <=15%
• 2: >15% and <20%
• 1: >=20% and <=25%

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.

• 3: >-5% and <5%
• 2: =5% or =-5%
• 1: (>=5% and <15% ) or (<-5% and >-15% )

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.

• 3:  >-5% and <5%
• 2: =5% or =-5%
• 1: (>=5% and <15% )  or (<-5% and >-15% )

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.

• 3:  >-5% and <5%
• 2: =5% or =-5%
• 1: (>=5% and <15% )  or (<-5% and >-15% )

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.

• 3:  >-5% and <5%
• 2: =5% or =-5%
• 1: (>=5% and <10% )  or (<-5% and >-10% )

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.

• 3:  >-5% and <5%
• 2: =5% or =-5%
• 1: (>=5% and <10% )  or (<-5% and >-10% )

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.

• 3:  >-5% and <5%
• 2: =5% or =-5%
• 1: (>=5% and <10% )  or (<-5% and >-10% )

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.

• 3:  >-5% and <5%
• 2: =5% or =-5%
• 1: (>=5% and <10% )  or (<-5% and >-10% ) 

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.

• 3:  >-5% and <5%
• 2: =5% or =-5%
• 1: (>=5% and <15% )  or (<-5% and >-15% ) 

• 3: >=50%
• 2: <50% and >=40%
• 1: <40% and >=30%

• 3: <=30%
• 2: >30% and <=50%
• 1: >50% and <=70%

• 3: >=90%
• 2: <90% and >=70%
• 1: <70% and >=50%

• 3: <= 10%
• 2: <= 30% and > 10%
• 1: <= 40% and > 30 %

• 3: >= 70%
• 2: >= 50% and < 70%
• 1: >= 30% and < 50%

• 3: >=  50%
• 2: >= 30% and < 50%
• 1: >=10% and < 30%

• 3: >=2 and <4
• 2: ( >=1 and <2 )  or (>=4 and <5)
• 1: (>0 and <1) or (>=5 and <6)