Page tree
Skip to end of metadata
Go to start of metadata

On this page:

Target audience:

CAST AI Administrators

Calibrating the automated function point count is only required when there is a need to align the calculation to: 

  • OMG-compliant Automated Function Point based manual count
  • other automated counts computed with a prior version of CAST AIP

Calibrate AFP count for Data Functions

The calibration of Automated Function Point count can be performed using the CAST Transaction Configuration Center (TCC). Calibration relies on an accurate and complete identification of transactions (see Transaction validation and identification).

  1. Exclude (select Ignore or Delete from right click pop-up menu) from Data Functions all non server side object types such as (but not limited to) objects that store data. Criteria is often based on object name. For example exclude Data Functions with names including the suffix tmp or sys (these do not belong to a functional transaction).
  2. Combine Data Functions. Also in this case the first strategy is to look at object names. Remember Data Functions are often database table rows that combine these rows into tables improving the FP scoring algorithm (refer to CAST OMG-compliant Automated Function Points for more details).
  3. Optionally review aggregation with App Team Architect/ SME to confirm aggregation or identify new ones.
  4. Remember to recompute the application FP to see changes
  5. Override the AFP count by entering a new figure (use only when you must force a specific FP count)
  6. Save your configuration before you proceed


Calibrate Transactions

  1. Review transactions and refine type assignment: External Inquire (EQ), External Input (EI) or External Output (EO)
  2. Merge and Split transactions. You can leverage the naming convention (exclusion should have been already in place as part of the link review) and the Transaction Full Call Graph view (available from right click pop-up menu) combined with the information gathered during the Architecture review.
  3. Access to an Application Team's Architect or SME can improve the results of this calibration.
  4. Recompute FP and save the configuration

AFP counts can also be overwritten to force a specific count if required.

Using the Compute option

Before running the Compute action as described above, you need to have at least already run an analysis (see 2.2.1. Run the Analysis) on your Application, if not, you cannot use the Compute action at all.

If you have run an analysis and you then attempt to run the Compute action, the CAST Transaction Configuration Center will prompt you that no snapshot data is present:

The CAST Transaction Configuration Center requires a special function (the pre-snapshot preparation action) to have been run before the Compute action can be run - this is to ensure that the Function Point data for Data Functions and Transactions is correct and up-to-date. The pre-snapshot preparation action is executed as part of a snapshot generation, as such, CAST recommends that you generate a snapshot before you attempt to run the Compute action. However, generating a snapshot can be time consuming particularly if you are generating multiple snapshots to take into account small adjustments in the analysis configuration to correctly analyze the Transactions and Data Functions you require.

In previous versions of CAST AIP, this issue was avoided through the creation of a specific Snapshot Preparation Assistant job that could be configured to run automatically immediately after running an analysis - or independently - this was then sufficient to run the Compute action in the CAST Transaction Configuration Center. In the current version of CAST AIP, the Snapshot Preparation Assistant is no longer available, therefore, and in order for you to avoid having to generate a snapshot each time you change your analysis configuration, you can do one of two things:

Run a pre-snapshot preparation in the CAST Transaction Configuration Center

If you attempt to run the Compute action and no snapshot is present (and you have already run the analysis (see 2.2.1. Run the Analysis)), then the following dialog box will be displayed:

Clicking Yes will run the pre-snapshot preparation action (this is equivalent to running the Snapshot Preparation Assistant in previous releases of CAST AIP) and then the Compute action will be executed. Clicking No will run the Compute action anyway, but the Function Point data will not be up-to-date.

Run a pre-snapshot preparation action via the command line

If you prefer to automate the pre-snapshot preparation action, you can use the CAST Management Studio command line option "PrepareSnapshot" from a batch file (see the CAST Management Studio help for more information about the Command Line options):

CAST-MS-cli.exe PrepareSnapshot -connectionProfile CAST_MNGT -appli "TEST" 

Running this option from the command line is identical to running the pre-snapshot preparation option in the CAST Transaction Configuration Center (and is also identical to running the Snapshot Preparation Assistant in previous versions of CAST AIP).

Previous: 2.2.3. Snapshot generation and validation
Next
2.3. Analysis Automation

  • No labels