Transaction Configuration Center - Enhancement - Automated Enhancement Technical Points variation - No DELETED AETP with removed source code

This page handle the case when there is a list of removed files that have been discovered and extracted by the CAST Delivery Manager Tool     DMT - Package Content tab - Files found

but no AETP value has not variate

Step by Step scenario

1. Run analysis
2. Take snapshot
3. Open TCC
4. Go to Enhancement node

Perform the below actions

1. Check if it is supposed to analyse the removed files in the previous run, example - files of extension ".png" are not supposed to be analyzed.
   1. Get the extension of the list of removed files from CAST Delivery Manager Tool -    DMT - Package Content tab - Files found
      
      
   2. Get the extension that is supposed to be analyzed, for the observed file extension of the AU - 2.1.2. Confirm the Analysis Configuration
      
      
   3. If the extension of the removed files is by default not supposed to be analyzed or if the Analysis Unit was manually configured to not analyze the extension, then it's normal that Deleted AETP is equal to zero
   4. Else If the extension of the removed files is by default supposed to be analyzed or if the Analysis Unit was manually configured to analyze the extension then, it's not normal that Deleted AETP is equal to zero, we need to investigate the root cause by following the steps bellow:
      1. Identify the set of objects that variate between the 2 snapshots
         1. Get the Id of snapshots from where you are observing the variation, for this refer to SQL Queries - CAST Central Base - Queries on snapshots - How to get the ID and name of a snapshot for a given application

         2. Get the set of objects that are part of the previous run but not the current run, for that execute the following on the central schema - SQL Queries - CAST Central Base - Queries on Objects - How to get the delta of objects between two snapshots

            1. If the query does not return rows, then there is no negative variation between the 2 snapshots at central schema level. So, we are facing an issue of missing objects from the previous run, in this case refer to CAST Engineering Dashboard - Object - Missing objects

            2. Else If the query returns rows, then there is negative variation between the 2 snapshots at central schema level, but this variation does not contribute to the AETP. At this stage, we need to develop our understanding of Automated Enhancement Technical Points - TCC - CAST Transaction Configuration Center - Right hand pane

               The DMT delivery, report the physical objects while TCC report technical and functional objects, while Automated Enhancement Technical Points calculation considers all technical objects in the application, i.e. those computational elements which are not in the Automated Enhancement Function Point scope. So if the physical objects (DMT) were part of the Automated Enhancement Function Point scope then they were not part of the Automated Enhancement Technical Points scope. So if they are physically removed from DMT they will be functionally removed from the Automated Enhancement Function Point but they will not be technically removed from the Automated Enhancement Technical Points, which explain why you will not get Deleted Automated Enhancement Technical Points. Allow myself to illustrate this with the following figure:

               

               With this, we will check if the objects present in the previous run but not current run are part of one of the Transactions in previous run , for this we will run the following on the central schema - SQL Queries - CAST Central Base - Queries on Objects - How to check if the objects present in the previous snapshot but not current snapshot are part of one of the Transactions in previous snapshot
               

   1. 1. 1. 1. 1. If count1=count2=0, then you should not be in the current step, you should be able to investigate missing object from previous run - CAST Engineering Dashboard - Object - Missing objects
                  

               2. Else If count1=count2≠0 then the objects physically removed from DMT are functionally removed from the Automated Enhancement Function Point, which justify why they are not technically removed from the Automated Enhancement Technical Points

               3. Else If count1≠count2

                  1. If count1≠count2 and count 2=0, then all the objects physically removed from DMT are not functionally removed from the Automated Enhancement Function Point, hence they MUST be technically removed from the Automated Enhancement Technical Points

                  2. Else If count1≠count2 and count 2≠0 then:

                     1. Part of the objects physically removed from DMT are not functionally removed from the Automated Enhancement Function Point, hence they MUST be technically removed from the Automated Enhancement Technical Points

                     2. The other part of the objects physically removed from DMT are functionally removed from the Automated Enhancement Function Point which justify why they are not technically removed from the Automated Enhancement Technical Points

                  Whatever the case, when count1≠count2 then we need to justify why there is no DELETED AETP. At this stage we will check if the issue is due to the metric computation, on deleted technical objects:

                  1. Compute the following query on the central schema to check if the objects technically deleted are considered in metric computation - SQL Queries - CAST Central Base - Queries on Objects - How to check if the deleted technical objects has the Deleted status

                     1. If the query does not returns rows, then the metric computation does not consider the Deleted object as DELETED, ADDED, MODIFIED or UNCHANGED , the issue can be due to the fact that consolidation of successful snapshots are not done on chronological order, in fact this can occur when the capture date of a snapshot id is changed and the product does not do the needed consolidation after this action, which explains totally the results of the above query - lets illustrate the case with a case study:

                        1. Initially, the application has 2 snapshots S1 of capture date D1 and S2 of capture date D2 where D1 < D2 and there are some objects deleted from snapshot S2

                        2. We change the capture date of D1 with the capture date D3 where D2 < D3
                           

                        If no consolidation is done after that, then technically the objects are deleted from S2 but chronologically there is no deleted objects from S2 since the capture date of S2 is the lowest date, impossible to get deleted objects from the first snapshot because nothing is created before the first snapshot.
                        First we will check if the capture date was changed across snapshots, for that run the following on central schema - SQL Queries - CAST Central Base - Queries on snapshots - How to check if the capture date was changed across snapshots

                        1. If the query returns rows then

                           1. Spot all the snapshots Id's between the following rows:

                              Query result example

                              Start DSS_UPD_FunctionalDate for snapshot 2"
                              End DSS_UPD_FunctionalDate"

                              in our example the Id's are 1, 2, 3

                           2. Get the snapshots Id's that are greater than the greatest snapshots Id's involved in the capture date for help refer to - SQL Queries - CAST Central Base - Queries on snapshots - How to get the ID and name of a snapshot for a given application

                           3. Get the name of all snapshots (the ones involved in the capture date Update and snapshots Id's that are greater then the greatest snapshots Id's involved in the capture date Update), for help refer to SQL Queries - CAST Central Base - Queries on snapshots - How to get the ID and name of a snapshot for a given application

                              Consolidate the snapshots -  CMS - Execute tab

                              

                              
                              

                        2. Else, if the query does't return rows then contact  CAST Technical Support. with the following Relevant input
                     2. Else if the query returns rows:

                        1. If the status of all objects is DELETED, then the metric computation consider the Deleted object as DELETED so the issue is not due to metric computation, contact  CAST Technical Support. with the following Relevant input

                        2. Else if the status of at least one object is added, modified or unchanged, then the metric computation consider some Deleted objects as ADDED, MODIFIED or UNCHANGED this is due to metric computation, contact CAST Technical Support. with the following Relevant input

2. If the above steps do not solve your issue contact CAST Technical Support. with the following Relevant input

Ticket # 13065