TCC - AFP Calibration - Data Functions/Transactional Functions sub-nodes - Right hand panel

AFP Calibration - Data Functions/Transactional Functions sub-nodes - Right hand panel

The Data Functions and Transactional Functions sub nodes (in the AFP Calibration node) enable you to:

• view the default CAST results in the CAST Analysis Service (from the Snapshot generation) prior to any calibration taking place
• calibrate the default results as required (for more information about calibration and how to do it, please see Calibrate):
  • change the type (ILF, EIF, EI, EO, EQ) and the value of each Data Function or Transactional Function that has been "detected" via the pre-defined set(s) or the specific set(s) that you have created
  • Delete, split or merge objects

Summary of right hand panel options:

Show valid, empty and ignore, deleted items

Use these options to hide (from display) all objects as follows:

• Valid > Valid objects are objects that have a Computed FP value above 0.
• Empty/Ignored > Empty objects are Transactional type objects that have a Function Point value of 0 - an object will have a Function Point value of 0 when the DET (Data Element Type) and FTR (File Type Reference) values are also both 0. Note that Data Functions type objects are never classed as empty as the RET (Record Element Type) value is always at least 1. Ignored objects are those that you have marked as Ignore as part of the Calibration process (right click an object or objects and select Ignore selected Data Functions/Transactions)
• Deleted > Deleted objects are those that you have marked as Deleted as part of the Calibration process (right click an object or objects and select Delete selected Data Functions/Transactions)

Column headings

Technical name	The object's technical name as stored in the CAST Analysis Service
Object type	The object's type - these are internal to CAST
Functional name	The object's functional name as stored in the CAST Analysis Service
Computed type	Indicates how the CAST algorithm computed the object during the snapshot generation (determines the computed Function Point value of an object). The following can be displayed: Data functions > EIF (External Interface Files), ILF (Internal Logical File) Transactions > EI (External Inputs), EO (External Outputs), EQ (External Inquiries) - or a mix of the above (e.g.: EO_EQ).
Custom type	This column enables you to change the Computed type - in other words, you can calibrate the results and change the way in which the CAST AIP algorithm will calculate the object in question. Use the drop down list to choose a custom type - all those mentioned above for Computed Type are available for selection. Changing the computed type will affect, primarily, the Computed Function Point value.
FP value	Displays the Function Point value of the object in question - in other words the value determined by the CAST AIP algorithm during the snapshot generation.
Custom FP	This column enables you to change the Function Point value for the object in question - in other words you can calibrate the original results to suit your environment.
# DET	Number of Data Element Types (a non-repetitive field in an ILF) for the object in question.
# FTR	Number of File Type References (a file referenced by a transaction) for the object in question. Only displayed in the Transactional node.
# RET	Number of Record Element Types (a subgroup of data elements inside a logical file) for the object in question. Only displayed in the Data function node.
Status	Indicates the current status of an object: Object has been calibrated (i.e. modified) in some way - e.g. new value in the New FP column. The object has not yet been saved: if you attempt to use the Compute action you will be requested to save the changes first. In addition, the status bar at the bottom of the GUI will reflect the fact that the changes have not yet been saved: Object has details - right click and select View details for more information about the objects involved with the current object. Object is marked as deleted. See Delete an object. Object has been split into its constituent sub-objects. See Split an object. Object has been split into the objects it calls. An object that is visible in the list because the parent object has been split. An object that is visible in the list because an object that calls the current object has been split. An object that has been merged - this can occur automatically during the snapshot generation process, or it can be done manually - see Merge/Unsplit objects for more information. Object is marked as ignored. See Ignore/Unignore an object.
Full name	Displays the object's full name to help recognition.
Default FP Value	Only displayed in the Transactional Functions node! This column indicates if the number displayed as "FP value" is: computed "default" (because the transactional function was originally empty). For empty transactions (those with 0 DET and FTR, and thus FP value = 0), the CAST Transaction Configuration Center can set a pre-defined Function Point value via the computation settings (see the Compute section for more information), in order to avoid having empty transactions in the AFP Calibration result. Items with "default FP values" will be flagged with a green icon in the Default FP Value column: Items that are "assessed" (when the Default FP value for empty Transaction Functions option is set to ASSESS in Compute settings) will be marked with a blue icon in the Default FP Value column:

Right click contextual menu options

OMG CISQ AFP Specifications for Data Entities

Please see Built-in parameters node - Right hand panel (section OMG CISQ AFP Specifications for Data Entities) for an explanation of why certain objects may not be displayed as Data Entities even though you expect them to be be present.