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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Enhancement node - Right hand panel


The Enhancement node has been designed in response to a specific issue. Please read below to find out more information.

Background

In previous versions of CAST AIP, when examining Function Point data between successive snapshots it became clear that a large quantity of Function Points were being flagged as "modified" with a discrepancy compared to the actual number of artifacts that were flagged as modified. As such, this was preventing users from gathering reliable information about what had really changed between two snapshots. The Enhancement feature is a direct response to this issue.

The concept of items (Data Functions/Transactional Functions) that have been added and deleted between snapshots is relatively easy to comprehend, however, an item that is flagged as modified is more complex: in basic terms an item is flagged as modified when its checksum value is deemed to have changed since the previous snapshot. However, an item has a checksum value that is the sum of the checksum values for ALL of the objects that form the original item:

  • the initial object (the Data Function/Transactional Function)
  • the data function record objects that are used by the entry-point object (tables and persistence objects described as data entities or end-points)
  • all objects that are located on the call graph between the entry and end-point objects.

If any of these objects change between successive snapshots, then the overall item checksum value will change and the item will be flagged as modified. For example, an added or removed comma or white space would cause a change in the checksum value. Modified Function Points are the sum of the Function Point values for each modified item - as such it was not uncommon to find that changing something very trivial in one object that was shared between multiple items caused a large number of items to be flagged as modified between snapshots, thus making the Modified Function Point value also very high.

Enhancement feature

In essence the Enhancement feature provides a detailed presentation of both Data Functions / Transactional Functions in separate nodes:

Each node contains a list of snapshots (Upper left panel) and a list of all objects present in the selected snapshot (Upper right panel) allowing you to understand why certain items have been marked as modified/added/deleted between snapshots. The Enhancement feature will identify all the objects that form each item (displayed in the Lower panel) and between how many items each object is shared (only available for Transactional Functions: a Transactional Function can belong to more than one "item" - see the Shared Counter option below). Once the object identification is complete you can then decide whether an object or objects should be included or excluded in the checksum value calculation for all items (Data Functions/Transactional Functions). When you have included or excluded an object from the checksum value calculation, you can then re-calculate (using the Recompute checksums and snapshot statuses option) all checksums for all items and all snapshots. The metrics (in particular the modified function points metric) are then also re-calculated based on the new checksum values and will be redisplayed in the Upper left panel allowing you to check whether the value is more in line with expectations.

Measures used to calculate enhancement Function Points

CAST AIP uses two distinct measures to calculate enhancement Functions Points - these can be chosen when you generate a snapshot with the CAST Management Studio:

OMG Automated Enhancement Points (AEP)

Note that this measure is used by default from CAST AIP 8.2.x onwards.

CAST integrates the estimation of OMG Automated Enhancement Points (AEP). Like EFP, the feature helps to evaluate overtime the size of evolutions implemented by teams producing applications. It computes and displays data functions and transactional functions that have been modified, added, or deleted, and information on the technical components of applications that do not belong to any transaction. The unadjusted function points that are calculated are weighted with Complexity Factors based on the objects complexity.

The AEP measure considers both the functional and the technical sides of the application enhancement. Therefore, the computation of Automated Enhancement Points (AEP) is divided in two sections: Automated Enhancement Function Points (AEFP) and Automated Enhancement Technical Points (AETP). The total AEP will be the addition of these two: AEP = AEFP + AETP.

AEFP Computation

The total value of Automated Enhancement Function Points (AEFP) is calculated by adding the AEFP value of all Transactional Functions and Data Functions in the application. The AEFP of each individual Transactional Function / Data Function is calculated by multiplying its FP value by its Complexity Factor (AEFP = FP x CF). The Complexity Factor of a certain Transactional Function / Data Function is an adjustment factor (defined by an OMG-specification) which is calculated based on its status (added / modified / deleted) and the complexity of the objects inside the Transactional Function / Data Function.
NOTE: the value reported for AEFP includes only added, modified and deleted Functions. All unchanged Functions are automatically excluded from this value (their Complexity Factor is considered as 0, and thus their AEFP value will also be 0).

AETP Computation

Automated Enhancement Technical Points calculation considers all technical objects in the application, i.e. those computational elements which are not the Automated Enhancement Function Point scope.

OMG Enhancement Function Points (EFP)

In addition to AEP, CAST also integrates the estimation of Enhancement Function Points (EFP) also called Project Function Points, so that CAST provides both baselining, e.g sizing an entire application using Automated Function Points and Enhancement Function Points. With the Enhancement Function Points feature, CAST AIP is in a position to display detailed information about the changes between two versions of an application and between two snapshots of the same application.

This feature helps to evaluate overtime the efficiency of teams producing applications. It is particularly useful in outsourcing contexts as many outsourcing contracts are based on FP when it comes to determine the size of the deliverables. This feature computes and displays data functions & transactional functions that have been modified, added or deleted. For each application, CAST AIP will provide 3 different pieces of information:

  1. Added FPs: FPs identified from the functions identified as created in the Vn+1 (i.e. that is added by the enhancement project)
  2. Modified FPs: FPs counted because existing function is changed during the enhancement project
  3. Deleted FPs: function points counted for function deleted during the enhancement project. 

Differences between the two measures

The main differences between the legacy Enhancement Function Points (EFP) mode and the Automated Enhancement Points (AEP) mode (introduced in CAST AIP 8.2) are as follows:

  • EFP does not consider the technical side of the application evolution; AEP does (calculating Automated Enhancement Technical Points, AETP)
  • EFP uses a transaction reduced call graph (from Entry Points to End Points / Data Entities); whereas AEP considers the transaction full call graph (it covers also the paths that do not reach an End Point / Data Entity). This means that the number of objects in the transaction call graph for AEP is higher.
  • The adjustment factor used to calculate Enhancement Function Points (EFP) is called "Impact Factor", and it is based on fixed user-defined formulas; on the contrary, the adjustment factor to calculate Automated Enhancement Function Points is called "Complexity Factor", and it is based on dynamic OMG-defined formulas.

The table below summarizes these differences:

Mode Transaction Call Graph Adjustment Factor Evolution
EFP Reduced Impact Factor (fixed user-defined formula) Only Functional
AEP Full Complexity Factor (dynamic OMG-defined formula) Functional and Technical

Note about switching between measurement modes

When changing the measurement mode it is important to take into consideration the impact this will have on the analysis/snapshot results and that it will introduce a disruption into the measurement trending. There are important differences between the two measures (AEP and EFP) that must be understood:

  • The EFP mode does not manage the technical part of application whereas AEP does.
  • When using EFP mode, Transactional Functions are based on the reduced call graph whereas for AEP, Transactional Functions are based on the full call graph.
  • The AEP specification defines Complexity Factors based on artifacts' complexity or changes made to data entities.

When moving from EFP to AEP to get more precise values, results will show objects that do not belong to the reduced transaction call graph as "added" and this will impact the measure, even if these objects have not really been added. Points related to the technical part of the Application will also appear in the results. Moreover, taking in to account object complexity to weight the FP values will impact the results as well.

Moving in the opposite direction from AEP to EFP will result in having objects that do not belong to the full transaction call graph to be considered as "deleted". This will also impact the results, even if those objects have not been really removed. In addition, Complexity Factors will be replaced by Impact Factors that are set to 1 by default and points related to the technical part of the application will disappear.

If you plan to change the measurement mode, it is necessary to recreate a new baseline snapshot. To do that, after you change the measure you must generate a new snapshot for the same Application version but it must not be considered as consistent for the new measure. The next snapshot you generate for the Application will be consistent and can be used as the first snapshot using the new enhancement measure.

Enhancement right hand panel

The data in this panel is automatically fetched from the database server and displayed when selecting the node. The data presented here represents the "evolution" of the Function and Technical Points between successive snapshots.

By default the data for the most recent snapshot will be displayed when the node is selected. If there is only one snapshot present for the selected Application, then data will show Added Function Points for both Transactional Functions and Data Functions. When more than one snapshot is present, the data show is a comparison between the current and previous snapshot. In this case, you may see Modified and Deleted Function Point data as well as Added.

Display with EFP measure

Display with AEP measure

Note about Automated Enhancement Technical Points (AETP)

AETP is the count of added / modified / deleted technical points, which are calculated based on the added / modified / deleted technical objects (i.e. objects which are not part of any transaction). In other words, AETP summarize the evolution performed in the application, but outside the functional scope (these objects are not taken into account in the functional points, so the new AEP measure introduces the concept of "technical points" to assess the enhancement done in these types of objects).

AETP data is not available when the EFP measure has been used to calculate the snapshot.

Prev. / Next buttons

It is possible to see data from a previous/next snapshot by clicking the Previous or Next buttons - data in the panel will refresh automatically.

Display AEP Detail

The formula used to generate AEP information are complex and use a variety of intermediary metrics. To help understand how AEP is generated, clicking the Display AEP Detail button will display these intermediary metrics and formula in a text file. You can find out more about this text file in Enhancement node - AEP Details.

Export List of Objects

This button can be used to export the list of technical objects that are involved in the Automated Enhancement Technical Points (AETP) calculation for a given snapshot (note that this feature will be available only for the snapshots computed using AEP measure). The output CSV file will contain the following values:

  • OBJECT_ID: Object ID

  • OBJECT_NAME: Name

  • OBJECT_FULLNAME: Full name

  • OBJECT_TYPE_STR: Type of object

  • STATUS: Status in the current snapshot

  • EFFORT_COMPLEXITY: Effort Complexity

  • ORIGIN:

    • RULE: Objects that have been captured through a set
    • MANUAL: Objects that have been manually excluded

For example:

Application Functional Size

This section shows the Automated Function Points values (for Transactional Functions, for Data Functions and total) of the application when the displayed snapshot was taken.

Warning: these values are not necessarily the same as the ones displayed in the AFP Calibration node. This node displays the AFP values at the present time, and they can suffer variations if you perform calibration actions and click on the Compute Function Points button. On the contrary, the values displayed in the Enhancement node are the definite AFP values that were computed for the application at the moment when a snapshot was executed. These values cannot be changed.

Ratios

This section provides information about the elements that comprise the current Applications and snapshot:

Number of Artifacts Total number of artifacts in the Application.
Number of classes/programs The number of main objects (classes and/or programs) in the Application.
Number of Objects The number of all objects in the Application.
TFP/DFP This is the ratio between Transactional Function points and Data-Function points.
Percentage of artifacts involved in TF The ratio of the distinct number of artifacts in all Transactional Functions in the application compared to the total number of artifacts in the Application.
Average AFP per class/program This to see if the size of the functional part (AFP) of the Application is relevant or not compared to the number of main objects (classes and/or programs).
Percentage of objects involved in TF The percentage of the objects in the Application involved in Transactional Functions.
Data Functions/Transactional Functions sub nodes

See Enhancement - Data Functions/Transactional Functions sub-nodes - Right hand panel for more information.


CAST Website

  • No labels