This page provides the detailed information on all the processes and steps that take place after computing function points and loading results. It will give details about the information that is written in the logs that are generated for computation.

Figure 1

For 8.2.x Online help : CAST Management Studio - Help > Content

In this page, the different log lines corresponding to the Compute function points and load results are listed with functional and technical explanation of the logs that it generates. You can get the TCC log file at CAST Logs location or by choosing the Log option from the GUI toolbar:

Figure 2

TransactionConfigurationCenter.<YYYYMMDDHHMMSS>.log.txt

Connect to the management schema

Connecting...

Retrieve information about the application (application name, application id)
Initializing...

Proceed to the compute Function Points operation on the application, and provide the application name and the application ID
About to compute Function Points of application "application_name" (#application_id)...

Connect to the Analysis service

Synchronizing local site...

Build sets susceptible to be part of the list of entry point, end point, Data Functions and excluded items, refer to the following link for more information TCC - Data functions, Transaction end points, Transaction entry point nodes, Excluded items - Right hand panel

Building sets...

The computation of application function point has started

Preparing computation...

The computation of Data Function and Transactions is in progress, this include the following actions:

• Manage Data Function merge for more information refer to TCC - Merge/Unsplit objects
• Define exclusions from TCC parameters for more information refer to Excluded Items
• Cleanup existing Data Functions from tables to ignore, for more information refer to OMG CISQ AFP Specifications for Data Functions
• Build list of Data Functions built and Transaction end points built from Transaction Configuration Center parameters, for more information refer to TCC - Data functions, Transaction end points, Transaction entry point nodes, Excluded items - Right hand panel
• Delete obsolete Data Functions, for example Data Function where the related table is not anymore part of the application
• Manage Data Function merge after the deletion of the obsolete Data Functions deletion
• Create Data Function objects, Identify the Data Functions
• Compute RET, DET and FP for Data Functions for more information refer to Counting Function Points
• Manage Transaction merge for more information refer toTCC - Merge/Unsplit objects
• Build list of Transaction entry points built from Transaction Configuration Center, for more information refer to TCC - Data functions, Transaction end points, Transaction entry point nodes, Excluded items - Right hand panel
• Delete obsolete Transactions, for example Transactions for which the entry point in no more configured
• Manage Transaction merge after the deletion of the obsolete Transaction  TCC - Merge/Unsplit objects

Computing data functions... Aug 29, 2017 10:36:34 AM

Compute the call graphs between Transaction entry points and Data Function,

The computation is done through a command line, the command line launch the executable DssRun.exe, and specify the option CONNECT_LOCAL and LOCAL_REDUCED_GRAPH. The first option is used to connect on the Analysis service on which the application is analyzed, the second option is used to compute Transactions call graph.

Computing transactions call graph...  
DssRun.exe - command line arguments: -CONNECT_LOCAL('RDBMS','//host:port/postgres','username','password,'local_schema') -LOCAL_REDUCED_GRAPH  

Form the reduced Transaction call graphs that reach Data functions and end-points only. They are only used for counting AFP and EFP.

Starting transaction reduced graph computation (64-bits version)...  

Load reduced Transaction call graphs

Loading reduced graph data...  

Detect and correct the badly calibration that can be due to customization

 Refer to the following link for more information about how to custom calibration Automation-Insert custom treatments during the computation

Badly calibrated Data & Transactional Functions repair for application #application_id:  

No Data/Transactional Function calibration problem found. 

Count AFP and EFP

Starting transaction reduced graph analysis...
Graph analysis done.

Reduced graph results is about to be saved on the analysis service
Saving reduced graph results...  

Save call graphs of Transactions and provide also the number of Transaction links generated
Saved call graphs of transactions in application #application_id (#Number of transaction links generated). 

Compute Transactions call graph has finished
Computation finished.  

Compute Transactional values on the discovered Transactions:

• Compute DET and FP for all Transactions, refer to Counting Function Points
• Compute object checksums Data Functions and Transactions, note that the checksum values are calculated by CAST AIP for objects resulting from an analysis and are used to determine whether an object has changed between successive snapshots

 Finalizing function points computation...

Computation of application function point has finished

Job finished.

Report Transactional information

Function points computation report:

Number of applications with reduced call graph : #Number of applications with reduced call graph (#Application id)   

Number of relevant objects in repository : #Number of objets loaded from the Knowledge base

Number of OMG AFP-links in repository : #Number of links loaded from the Knowledge base  

Number of data functions : #Number of Data Functions

Number of transactions : #Number of Transactions  

Number of empty transactions : #Number of empty Transactions   

Number of transaction links generated : #Number of links involved in Transactions

Number of objects in largest transaction : #Number of objects in largest Transaction

Number of elements in largest SCC group : #Number of element in the largest Strongly Connected Component

Number of elements allowed in SCC groups: #Number of allowed element in a largest Strongly Connected Component, By defaultst he value is equal to 1000

Number of elements in largest used SCC group : #Number element in the largest Strongly Connected Component that is part of at least one Transaction

Number of ignored SCC groups (too large) : #Number of ignored largest Strongly Connected Component, an SCC is ignored if the element contained in it is bigeer than the number of elements allowed in SCC groups

This sections report the computing duration
Computing duration: #Duration