Summary: this section provides an introduction to working with Transactions and Function Points in Console.


The CAST Application Intelligence Platform enables users to measure Automatic Function Points from the source code of an application. CAST measures the functional size of an application using OMG-compliant Automated Function Points and uses a default algorithm that is applied "out-of-the-box". You can find out more in CAST OMG-compliant Automated Function Points.

However, Function Points is a functional size measure that is based on the application's specifications and requires knowledge of the intent of the application's designers ("primary intent" mentioned in the OMG-compliant Automated Function Points Counting manual). So, to make the measure possible, Function Point Experts and Consultants need to calibrate the initial automatic count made by CAST . Calibration includes:

  • removing technical and temporary objects from the list of Function Points counted
  • merging several function points into one (and unmerging)
  • changing the type of the Data or Transactional Functions

Once calibration is complete, function point data can then be re-computed.

How does it work?

  • The most recent snapshot data for a given Application or set of applications is displayed - OMG-compliant Automated Function Points and Transaction information is displayed
  • You can then calibrate these results to your liking, by creating new rules, merging objects etc.
  • Finally you compute the results (or generate a new snapshot) to ensure new Function Point values are displayed

What can you do with Console?

Note that in order to view information about Transactions and Function Points in Console, a snapshot must have already been generated.

At the current time, the following is possible with the Console interface:


  • View the number of valid/invalid transactions identified in the Application during the analysis
  • View detailed information about the number of transactions and data entities identified in the Application during the analysis
  • View detailed information about the rules (default and custom) used to identify Transaction entry-points, Data entities, Transaction end points and excluded items, including:
    • The package providing the rule
    • The number of objects identified by the rule
    • Whether the package has been updated
    • Whether the package is active or not
  • Ability to create a new custom rule

Function Points

  • View the total number of Automatic Function Points (AFP) identified in the Application during the snapshot, including a breakdown for Transactional Functions (TF) and Data Functions (DF)
  • View detailed information about the Transactional Functions (TF) and Data Functions (DF) identified in the Application during the analysis
  • Ability to edit each Transactional Functions (TF) and Data Functions (DF):
    • change the type (ILF, EIF, EI, EO, EQ) and the value of each Data Function or Transactional Function that has been identified in the Application during the analysis/snapshot
    • Delete, merge or unmerge Transactional Functions (TF) or Data Functions (DF)
  • Change the counting mode used: AEP (default) or EFP (legacy)

Computing function points

Once calibrated, a compute function point action can be run to view up-to-date information based on the calibration that you have performed (or you can generate a new snapshot which will include the compute function point action).