TCC - Calibrate on Documentation - V2

TCC - Change the Computed FP

Mon, 01 Jan 0001 00:00:00 +0000

Change the Computed FP

By default, CAST will use internal algorithms to define how the Function Point size of a specific object is computed. As discussed in Change the Computed Type, the method of computing the Function Points size is determined by which category the object falls into.

You will see how CAST computed the Function Point size of each individual object in the Data Functions/Transactional Functions nodes (part of the AFP Calibration node - Right hand panel), under the Computed FP column:

TCC - Change the Computed Type

Mon, 01 Jan 0001 00:00:00 +0000

Change the Computed Type

By default, CAST will use internal algorithms to define how the Function Point size of a specific object is computed. The method of computing the Function Points size is determined by which category the object falls into:

Data Function type objects > EIF (External Interface Files), ILF (Internal Logical File).

Note that by default the CAST Transaction Configuration Center will consider all Data Functions as EIF, unless the Data Function is linked by Update/Delete/Insert/Write links, in which case it will be considered as ILF. You can override this setting at global level for ALL Applictions, or at Application level. Please see Compute for more information.

TCC - Delete an object

Mon, 01 Jan 0001 00:00:00 +0000

Delete/Undelete an object

Delete an object

In some circumstances, an object that is displayed in the AFP Calibration node may not be relevant. If this is the case, and you no longer wish this object to be included in future Function Point calculations, then you can use the CAST Transaction Configuration Center to delete the object.

Move to the AFP Calibration node - Right hand panel to begin calibration
Choose either the Data Functions or Transactional Functions sub node

TCC - Editing multiple objects

Mon, 01 Jan 0001 00:00:00 +0000

Editing multiple objects

If you need to Change the Computed FP or Change the Computed Type or even change the Functional Name of multiple objects, it is possible to do so as follows:

Move to the AFP Calibration node - Right hand panel to begin calibration
Choose either the Data Functions or Transactional Functions sub node
Hold down the CTRL key and select (with the mouse) the objects you want to edit so that they are highlighted as follows:

TCC - Ignore/Unignore an object

Mon, 01 Jan 0001 00:00:00 +0000

Ignore/Unignore an object

Ignore an object

In some circumstances, an object that is displayed in the Result node may not be relevant. If this is the case, and you no longer wish this object to be included in future Function Point calculations, then you can use the CAST Transaction Configuration Center to ignore the object.

Move to the AFP Calibration node - Right hand panel to begin calibration
Choose either the Data Functions or Transactional Functions sub node

TCC - Merge/Unsplit objects

Mon, 01 Jan 0001 00:00:00 +0000

Merge/Unsplit objects

CAST provides two manual mechanisms that can be used to group objects together. They are similar, but different:

Merge > A merge can be used with either Data Functions or Transactional Functions. Any number of objects can be merged together.
Unsplit > An unsplit can ONLY be used with Transactional Functions that have already been split. It is equivalent of reversing the split action. All objects added during the split action are removed from the results and the split Transactional Function returned to its normal state - i.e. it encompasses all its sub-objects and called objects.

Merging objects

The process of merging Data Functions and merging Transactional Functions is identical.

TCC - Split an object

Mon, 01 Jan 0001 00:00:00 +0000

Split an object

The way in which the CAST algorithm determines the existence of Data Functions and Transactions means that one object can be split into multiple objects if required. The table below indicates how a Data Function and Transaction can be formed and how they can be split:

Object type	How the item is formed	How the item can be split
Data Function	Can contain one or more data storage objects (for example SQL tables)	Split into constituent objects every time.
Transaction	Is always based on one object (for example a user entry form, which is usually a UI screen that interacts with database objects). The item itself and any sub objects (control and events for example) are taken together as roots for the call graph.	A choice will be offered: Split by sub-objects: the item itself, without any sub object, is considered as a single transaction, and each sub object (control or event) becomes the single root of new transactions. This is adapted to a use case where a complex UI screen contains buttons which run distinct transactions. Split by called objects: uses called objects of all roots (the form and its sub-objects), and creates a new transaction for each called object (only at the first call level). The called objects are typically methods called in reaction to user actions on the UI screen.

When an object is split, its constituent objects are then also displayed in the CAST Transaction Configuration Center so that you can calibrate them as well - see image below that shows objects that have been split or are a result of an object that has been split: