Recent changes to Function Point Analysis

Function Point Analysis modified by Ruben Gerad Mathew

Ruben Gerad Mathew — Tue, 01 Aug 2017 21:30:09 -0000

--- v34
+++ v35
@@ -2,9 +2,6 @@
 ===========================================================================================

 ***I conduct onsite support and training workshops for teams and organizations in FPA. Please contact Ruben at +919495400358 for more details.***
-
-Please visit the [Forums]
-(https://sourceforge.net/p/functionpoints/discussion/paidservices/thread/f6ecd57e/#44c9) 

 Progressive Function Point Analysis Workbook in excel can support standard function point analysis and also supports progressive workflow function point analysis for greater accuracy in estimation of projects.  The standard function point analysis has been enhanced by using a multiplicity factor using coefficients in the estimation of High/Medium/Low to arrive at the unadjusted function point count.

Function Point Analysis modified by Ruben Gerad Mathew

Ruben Gerad Mathew — Tue, 01 Aug 2017 21:26:26 -0000

--- v33
+++ v34
@@ -1,7 +1,7 @@
 For Licenses, Onsite Training, Online Web Support 
 ===========================================================================================

-***We conduct onsite support and training for teams and participate in assisting organizations in preparing for CPMG assessment and CMMI certification. Please contact Ruben at +919495400358 for more details.***
+***I conduct onsite support and training workshops for teams and organizations in FPA. Please contact Ruben at +919495400358 for more details.***

 Please visit the [Forums]
 (https://sourceforge.net/p/functionpoints/discussion/paidservices/thread/f6ecd57e/#44c9)

Function Point Analysis modified by Ruben Gerad Mathew

Ruben Gerad Mathew — Tue, 01 Aug 2017 21:21:12 -0000

--- v32
+++ v33
@@ -1,7 +1,7 @@
 For Licenses, Onsite Training, Online Web Support 
 ===========================================================================================

-***We conduct onsite support and training for teams and participate in assisting organizations in preparing for CPMG assessment and CMMI certification. Please contact Ruben at +918105093030 for more details.***
+***We conduct onsite support and training for teams and participate in assisting organizations in preparing for CPMG assessment and CMMI certification. Please contact Ruben at +919495400358 for more details.***

 Please visit the [Forums]
 (https://sourceforge.net/p/functionpoints/discussion/paidservices/thread/f6ecd57e/#44c9)

Function Point Analysis modified by Ruben Gerad Mathew

Ruben Gerad Mathew — Tue, 16 Sep 2014 03:27:35 -0000

--- v31
+++ v32
@@ -323,7 +323,7 @@
 Count one logical collaboration segment for each unique External Component Interface in the process flow.

 **Identifiers**
-![FPA PET](https://sourceforge.net/p/functionpoints/wiki/_discuss/thread/356b25ce/e5ea/attachment/login_act.PNG)"FPA PET")
+![FPA PET](https://sourceforge.net/p/functionpoints/wiki/_discuss/thread/356b25ce/e5ea/attachment/login_act.PNG) "FPA PET")

 Process flows are divided into many logical groups or swim lanes. Trace the function calls within the application boundary for unique operational sub tasks.  Look for operational flow outside the boundary which may be identified by the use of libraries and shared utilities to identify ECI Components.

Function Point Analysis modified by Ruben Gerad Mathew

Ruben Gerad Mathew — Tue, 16 Sep 2014 03:22:26 -0000

--- v30
+++ v31
@@ -13,6 +13,13 @@

 **Given below is an introductory tutorial to FPA and an excerpt from the Progressive Function Point Analaysis book available from Amazon and ebooks from Kindle.**
 ![Progressive Function Point Analysis](https://sourceforge.net/p/functionpoints/wiki/_discuss/thread/356b25ce/e5ea/attachment/ProgressiveFPAEbook.PNG "Progressive Function Point Analysis")
+
+EBook  [Kindle]
+(http://www.amazon.com/dp/B00NH0MMAG) 
+
+Paperback  [Printed Edition]
+(https://www.createspace.com/4996534) 
+
 Function Point Analysis
 ------------------------------
 ***Function Point Analysis (FPA)***

Function Point Analysis modified by Ruben Gerad Mathew

Ruben Gerad Mathew — Tue, 16 Sep 2014 03:09:21 -0000

--- v29
+++ v30
@@ -12,7 +12,7 @@

 **Given below is an introductory tutorial to FPA and an excerpt from the Progressive Function Point Analaysis book available from Amazon and ebooks from Kindle.**
-
+![Progressive Function Point Analysis](https://sourceforge.net/p/functionpoints/wiki/_discuss/thread/356b25ce/e5ea/attachment/ProgressiveFPAEbook.PNG "Progressive Function Point Analysis")
 Function Point Analysis
 ------------------------------
 ***Function Point Analysis (FPA)***

Function Point Analysis modified by Ruben Gerad Mathew

Ruben Gerad Mathew — Mon, 15 Sep 2014 09:52:38 -0000

--- v28
+++ v29
@@ -1,7 +1,7 @@
 For Licenses, Onsite Training, Online Web Support 
 ===========================================================================================

-***We conduct onsite support and training for teams and participate in assisting organizations in preparing for CPMP assessment and CMMI certification. Please contact Ruben at +918105093030 for more details.***
+***We conduct onsite support and training for teams and participate in assisting organizations in preparing for CPMG assessment and CMMI certification. Please contact Ruben at +918105093030 for more details.***

 Please visit the [Forums]
 (https://sourceforge.net/p/functionpoints/discussion/paidservices/thread/f6ecd57e/#44c9)

Function Point Analysis modified by Ruben Gerad Mathew

Ruben Gerad Mathew — Mon, 15 Sep 2014 08:34:27 -0000

--- v27
+++ v28
@@ -23,18 +23,15 @@

 ------------------------------

-***Development Function Point Count:***  
-Function Points can be counted at all phases of a development project from requirements leading up to implementation. This type of count is associated with new development work and may include the prototypes, which may have been required as temporary solution, which supports the conversion effort. This type of count is called a baseline function point count.
-
-------------------------------
-
-***Enhancement Function Point Count:*** 
-It is common to enhance software after it has been placed into production. This type of function point count tries to size enhancement projects and is counted as sum of all added, changed or deleted function points in the application. By tracking enhancement size and associated costs, a historical database for your organization can be built. Additionally, it is important to understand how a development project changes over time.
-
-------------------------------
-
-***Application Function Point Count:*** 
-Application counts are calculated as the function points delivered, and exclude any conversion effort (prototypes or temporary solutions) and existing functionality that may have existed. 
+***Development Function Point Count:*** Function Points can be counted at all phases of a development project from requirements leading up to implementation. This type of count is associated with new development work and may include the prototypes, which may have been required as temporary solution, which supports the conversion effort. This type of count is called a baseline function point count.
+
+------------------------------
+
+***Enhancement Function Point Count:*** It is common to enhance software after it has been placed into production. This type of function point count tries to size enhancement projects and is counted as sum of all added, changed or deleted function points in the application. By tracking enhancement size and associated costs, a historical database for your organization can be built. Additionally, it is important to understand how a development project changes over time.
+
+------------------------------
+
+***Application Function Point Count:*** Application counts are calculated as the function points delivered, and exclude any conversion effort (prototypes or temporary solutions) and existing functionality that may have existed. 

 ------------------------------

@@ -49,7 +46,7 @@

 ------------------------------

-***IFPUG: Internal Logical File (ILF)  ***
+***IFPUG: Internal Logical File (ILF) ***
 User recognizable group of logically related data or control information maintained within the boundary of the application being measured. The primary intent of an ILF is to hold data maintained through one or more elementary processes of the application being counted. 

 **Simple Definition**

Function Point Analysis modified by Ruben Gerad Mathew

Ruben Gerad Mathew — Mon, 15 Sep 2014 08:32:33 -0000

--- v26
+++ v27
@@ -15,22 +15,26 @@

 Function Point Analysis
 ------------------------------
-***Function Point Analysis (FPA)*** Function Point Analysis is a method of estimating the size of a project by considering the input and output elements that are in the project and consolidates each type of operation into data or transaction function.  The size of projects used to be computed using the KLOC (Kilo Lines of Code), but could not be applied before the project was completed, as the prediction models were far from being accurate, but the concept had similarities to FPA as observed by Allan J. Albrecht, the inventor of FPA. The FPA methodology for sizing software was devised by him at IBM. The introduction of FP Counting practice helps to ascertain the size of the project by considering all the variables in the equation to deliver the function point count, and provided better estimates than those computed by analogy and user experience.
+***Function Point Analysis (FPA)*** 
+Function Point Analysis is a method of estimating the size of a project by considering the input and output elements that are in the project and consolidates each type of operation into data or transaction function.  The size of projects used to be computed using the KLOC (Kilo Lines of Code), but could not be applied before the project was completed, as the prediction models were far from being accurate, but the concept had similarities to FPA as observed by Allan J. Albrecht, the inventor of FPA. The FPA methodology for sizing software was devised by him at IBM. The introduction of FP Counting practice helps to ascertain the size of the project by considering all the variables in the equation to deliver the function point count, and provided better estimates than those computed by analogy and user experience.
 The Function Point Analysis estimation methodology validates the individual elements and the related groups to arrive at a complexity level of high, medium and low and assigns a function point count for each subset.  There are five basic function types Internal Logical Files (ILF), External Interface Files (EIF) in data functions and External Inputs (EI), External Output (EO) and External Query (EQ) in transaction functions. The elementary variables in functions are denoted as Data Element Type (DET).  The functional complexity is computed as the total number of user identifiable groups that exists within DETs and is termed as Record Element Type (RET) in Data Functions and all referenced file types are counted as File Type Records (FTR) in Transactions Functions. A corresponding matrix holds the reference function point values for all function types namely the ILF, EIF, EI, EO and EQ, with respect to the range of DET and RET/FTR in each function.  The total sum of the high, medium and low count of all operations is the unadjusted function point count.  There are 14 General System Characteristics used to ascertain the Adjusted Function point count.  The GSC computed in each project is called the Value Adjustment Factor. This is used to calculate the complexity of environment, task and language and tweak the final count for the particular environment.
 The Project count can be broadly classified into three types as defined in the Function Point Manual by David H. Longstreet.

 ------------------------------

-***Development Function Point Count:***  Function Points can be counted at all phases of a development project from requirements leading up to implementation. This type of count is associated with new development work and may include the prototypes, which may have been required as temporary solution, which supports the conversion effort. This type of count is called a baseline function point count.
-
-------------------------------
-
-***Enhancement Function Point Count:*** It is common to enhance software after it has been placed into production. This type of function point count tries to size enhancement projects and is counted as sum of all added, changed or deleted function points in the application. By tracking enhancement size and associated costs, a historical database for your organization can be built. Additionally, it is important to understand how a development project changes over time.
-
-------------------------------
-
-***Application Function Point Count:*** Application counts are calculated as the function points delivered, and exclude any conversion effort (prototypes or temporary solutions) and existing functionality that may have existed. 
+***Development Function Point Count:***  
+Function Points can be counted at all phases of a development project from requirements leading up to implementation. This type of count is associated with new development work and may include the prototypes, which may have been required as temporary solution, which supports the conversion effort. This type of count is called a baseline function point count.
+
+------------------------------
+
+***Enhancement Function Point Count:*** 
+It is common to enhance software after it has been placed into production. This type of function point count tries to size enhancement projects and is counted as sum of all added, changed or deleted function points in the application. By tracking enhancement size and associated costs, a historical database for your organization can be built. Additionally, it is important to understand how a development project changes over time.
+
+------------------------------
+
+***Application Function Point Count:*** 
+Application counts are calculated as the function points delivered, and exclude any conversion effort (prototypes or temporary solutions) and existing functionality that may have existed. 

 ------------------------------

@@ -45,7 +49,8 @@

 ------------------------------

-***IFPUG: Internal Logical File (ILF)  ***User recognizable group of logically related data or control information maintained within the boundary of the application being measured. The primary intent of an ILF is to hold data maintained through one or more elementary processes of the application being counted. 
+***IFPUG: Internal Logical File (ILF)  ***
+User recognizable group of logically related data or control information maintained within the boundary of the application being measured. The primary intent of an ILF is to hold data maintained through one or more elementary processes of the application being counted. 

 **Simple Definition**
 The entity model to which data is persisted (stored) by the application should be within its boundary, which may be the local database, file data source or any other type of persistence mechanism.  Data is organized into groups and subgroups.  The subgroups are more commonly related to tables in a database.  A group is a collection of tables that has affinity to a particular entity, department, location or any other user identifiable selection criteria like Customer Records or Orders. The data is maintained in the ILFs through an elementary process, which is (CRUD) Create, Read, Update, and Delete operation from within the application boundary and is referenced by an Add, Update, Delete transaction function. Control information may be passed as an indicator of the process to be performed.
@@ -60,7 +65,8 @@

 - - - - - - -

-***IFPUG: External Interface File (EIF) *** An external interface file (EIF) is a user identifiable group of logically related data or control information referenced by the application, but maintained within the boundary of another application. The primary intent of an EIF is to hold data referenced through one or more elementary processes within the boundary of the application counted. This means an EIF counted for an application must be in an ILF in another application.
+***IFPUG: External Interface File (EIF) *** 
+An external interface file (EIF) is a user identifiable group of logically related data or control information referenced by the application, but maintained within the boundary of another application. The primary intent of an EIF is to hold data referenced through one or more elementary processes within the boundary of the application counted. This means an EIF counted for an application must be in an ILF in another application.

 **Simple Definition**
 Data transmitted or persisted outside the application boundary, which can be accessed through the use of a remote application interface, a remote server, or data which may be maintained by another application and managed through remote interface.  Each of the fields required may be individually counted and reference keys and structures may also be counted. The nature of storage and retrieval alter the form, such as into key value pairs, or serialized to a string, or exchanged as XML data. The groups and subgroups are derived from the logical structure and not data in its physical state.
@@ -83,7 +89,7 @@

 - - - - - - -

-***IFPUG: External Input (EI) ***IFPUG: External Input (EI) 
+***IFPUG: External Input (EI) ***
 An external input (EI) is an elementary process that processes data or control information that comes from outside the application boundary. The primary intent of an EI is to maintain one or more ILFs and/or to alter the behavior of the system.  Data entering the application boundary either by user input, data feed or an external application invocation.

 **Simple Definition**
@@ -100,7 +106,8 @@

 - - - - - - -

-***IFPUG: External Inquiry (EQ) ***An elementary process that sends data or control information outside the boundary. The primary intent of an external inquiry is to present information to the user through the retrieval of data or control information. The processing logic contains no mathematical formula or calculations, and creates no derived data. No ILF is maintained during the processing, nor is the behavior of the system altered. 
+***IFPUG: External Inquiry (EQ) ***
+An elementary process that sends data or control information outside the boundary. The primary intent of an external inquiry is to present information to the user through the retrieval of data or control information. The processing logic contains no mathematical formula or calculations, and creates no derived data. No ILF is maintained during the processing, nor is the behavior of the system altered. 

 **Simple Definition**
 Denotes a simple data read operation, where information is retrieved or data is sent outside the boundary, which may simply be a display devices such as a PC monitor or information sent in response to a remote procedure call from another application outside the boundary.  There may be some operations leading to the output which makes EQ and EO have both input and output parameters.  
@@ -120,7 +127,8 @@

 - - - - - - -

-***IFPUG: External Output (EO) ***An elementary process that sends data or control information sent outside the application’s boundary and includes additional processing beyond that of an external inquiry. The primary intent of an external output is to present information to a user through processing logic other than or in addition to the retrieval of data or control information. The processing logic must contain at least one mathematical formula or calculation, create derived data, maintain one or more ILFs, and/or alter the behavior of the system. 
+***IFPUG: External Output (EO) ***
+An elementary process that sends data or control information sent outside the application’s boundary and includes additional processing beyond that of an external inquiry. The primary intent of an external output is to present information to a user through processing logic other than or in addition to the retrieval of data or control information. The processing logic must contain at least one mathematical formula or calculation, create derived data, maintain one or more ILFs, and/or alter the behavior of the system. 

 **Simple Definition**
 This is a data read operation and the result may be displayed, printed, transmitted to an external device or application outside the application boundary and is similar in all respects to EQ.  The control information may be additional data that may include information on how the data may be processed. The main difference of an EO from an EQ is that it may contain some mathematical equation, calculation of sum, average, count or other manipulation of data, or may create additional derived fields such as totals, subtotals, calculation of final cost and may also update the ILF to reflect the computed sum. 
@@ -139,7 +147,8 @@
 - - - - - - -
 Counting Function Points
 -----------------------------------
-***IFPUG: Data Element Type (DET) *** A DET is a unique user recognizable, non-recursive field. A DET is information that is dynamic and not static. A dynamic field is read from a file or created from DET’s contained in a FTR. Additionally, a DET can invoke transactions or can be additional information regarding transactions. If a DET is recursive then only the first occurrence of the DET is considered not every occurrence.
+***IFPUG: Data Element Type (DET) *** 
+A DET is a unique user recognizable, non-recursive field. A DET is information that is dynamic and not static. A dynamic field is read from a file or created from DET’s contained in a FTR. Additionally, a DET can invoke transactions or can be additional information regarding transactions. If a DET is recursive then only the first occurrence of the DET is considered not every occurrence.

 **Simple Definition**
 Data element types are the granular elements or fields collected from each of the transaction and data functions. These are the attributes contained in the tables, fields in UI forms, parameters passed in application calls. It is may be data that is unique and user recognizable, for a data table we may reference the unique column headers, for form elements we count each of the form fields. Only the first unique instance is counted even if tables or records are repeated. By assessing the DETs in relation to the RETs in data function or FTRs in transaction function we derive the complexity and arrive at the unadjusted function point count. Screen elements that are static like system time or page counters are not counted as DETs. For every application, any one-action link to submit the form contents will also be counted as a DET.
@@ -186,7 +195,8 @@
 Identify all the ILFs and EIFs in an application, and follow the process steps in a transaction function and count each unique reference to the EIF or ILF.

 - - - - - - -
-***Reuse FP*** Reuse FP is important to denote the functional reuse that may exist within a project. There are two types of Reuse implemented in general, the functional reuse is used with each data and transaction function to denote the percentage of reuse in the given function, this is not a part of the standard IFPUG practice and is used only in progressive function point estimation. There may not be sufficient time in estimating the size of reusable modules when they are large complex libraries, or may not be available in certain COTS products when they are designed as a black box, for such instances, the weighed reuse percentage is based on user experience and analogy.  A 0% reuse represents 100% new software build, any percentage denoted shows the total amount of reusable components available to the application for integration.  
+***Reuse FP*** 
+It is important to denote the functional reuse that may exist within a project. There are two types of Reuse implemented in general, the functional reuse is used with each data and transaction function to denote the percentage of reuse in the given function, this is not a part of the standard IFPUG practice and is used only in progressive function point estimation. There may not be sufficient time in estimating the size of reusable modules when they are large complex libraries, or may not be available in certain COTS products when they are designed as a black box, for such instances, the weighed reuse percentage is based on user experience and analogy.  A 0% reuse represents 100% new software build, any percentage denoted shows the total amount of reusable components available to the application for integration.  
 Reuse % = Reusable FP Count/Total FP Count
 The second method of reuse is calculated with Adaption Adjustment Factor (AAF) was presented in an IFPUG conference to calculate reuse with respect to integration of an entire application or component as a whole for any project.  It takes into consideration three factors Design Modification (DM), Code Modification (CM), Integration & Testing (I&T).  
 AAF = .4DM +.3CM +.3I &T

Function Point Analysis modified by Ruben Gerad Mathew

Ruben Gerad Mathew — Mon, 15 Sep 2014 08:29:33 -0000

--- v25
+++ v26
@@ -309,6 +309,8 @@
 Count one logical collaboration segment for each unique External Component Interface in the process flow.

 **Identifiers**
+![FPA PET](https://sourceforge.net/p/functionpoints/wiki/_discuss/thread/356b25ce/e5ea/attachment/login_act.PNG)"FPA PET")
+
 Process flows are divided into many logical groups or swim lanes. Trace the function calls within the application boundary for unique operational sub tasks.  Look for operational flow outside the boundary which may be identified by the use of libraries and shared utilities to identify ECI Components.  

 External links