
- •Version 4.1 Revision e5
- •Index 70
- •Preface
- •Revisions
- •Revision 4.1 5/1/1998
- •Notices
- •Brief cosmos Product Description
- •Cosmos Capabilities and Theory of Operation
- •Cosmos Project Level Estimation
- •Cosmos System Level Estimation
- •Cosmos Versions and Development History
- •Cosmos Personnel
- •Chapter 2: Function Point Model
- •Introduction to Function Points
- •Function Point Analysis
- •Application Boundary
- •Functionality
- •Data Functionality
- •Transaction Functionality
- •Complexity
- •Complexity Weights
- •Value Adjustment Factor and Adjusted Function Points
- •Backfire Method
- •Added, Changed, and Deleted Functionality
- •Comparison of Function Points and sloc
- •Cosmos and Function Point Analysis
- •Function Point Formulae Unadjusted Function Point Count
- •Total Degree of Influence
- •Value Adjustment Factor
- •Adjusted Function Point Count
- •Source Lines of Code: Backfire Method
- •Differences in Function Point Terminology
- •Chapter 3: cocomo Model cocomo Model Description
- •Cocomo Equations
- •Sloc and Delivered Source Instructions
- •Cocomo Modes
- •Cocomo Cost Drivers
- •Product Attributes
- •Hardware Attributes
- •Personnel Attributes
- •Project Attributes
- •Cocomo Complexity Influence Assignments
- •Cocomo Phase Distribution
- •Cocomo Formulae
- •Rayleigh Equations – General Description
- •Putnam’s Analysis: Software Equation
- •Manpower Buildup Index
- •Rayleigh Model
- •Development Phases
- •Application Type and Productivity
- •Rayleigh Formulae Software Equation
- •Manpower Buildup Index Equation
- •Chapter 5: Project Estimation Overview
- •Model Interrelationships
- •Import and Export of Models
- •Project Report
- •Chapter 6: System Estimation System Description
- •System Development Phases
- •System-LevelEffortEstimates
- •System-LevelScheduleEstimates
- •System-Level Manpower Buildup Index Level
- •System-Level Project Specification and Management
- •Schedule Compression
- •System Development and cocomo
- •System Output Report
- •References
- •Glossary
- •Customizing
Backfire Method
The Backfire Method is a means of estimating the count of SLOC that is equivalent to the adjusted function point count. Software Productivity Research, a firm lead by software metrics expert Capers Jones, has established “language multiplier” values for the major programming languages. The language multiplier gives the average number of SLOC per function point for that language. If the implementation language is chosen, one can estimate SLOC by multiplying the adjusted function point count by the language multiplier.
The Backfire Method is not part of the formal Function Point Analysis as defined by IFPUG. In COSMOS, however, the Backfire Method is used along with the Function Point Analysis, and is implemented in the Function Point Model.
Added, Changed, and Deleted Functionality
A software development project can basically do three things, separately or in combination:
Functionality can be added – new functionality.(If the application does not already exist, this is all that can be done)
Functionality can be changed – different functionality.
Functionality can be deleted – removed functionality.
All three of these possibilities are reflected in IFPUG’s formula for the function points of a development project with software enhancement:
EFP = [ ( ADD + CHGA + CFP ) * VAFA ] + ( DEL * VAFB )
-
where:
EFP = Enhancement project function point count
ADD = Unadjusted function point count of added functionality
CHGA = Unadjusted function point count of changed functionality, after the project
CFP = Unadjusted function point count of conversion functionality
DEL = Unadjusted function point count of deleted functionality
VAFA = Value adjustment factor, after the project
VAFB = Value adjustment factor, before the project
If the project only includes new development – added functionality – the formula for the project function point count reduces to:
DFP = ( UFP + CFP ) * VAF
-
where:
DFP = Development project function point count
UFP = Unadjusted function point count of new functionality
CFP = Unadjusted function point count of conversion functionality
VAF = Value adjustment factor
In a COSMOS function point model (and project), only one VAF is computed. Because of this, COSMOS projects have one restriction: Deleted functionality cannot be included in the same project as added functionality and changed functionality.If application functionality must be deleted, that must be estimated as a separate project with its own general system characteristic settings (and VAF value). This is because in IFPUG’s formula for computing the function point of a development project, deleted function points are adjusted by the VAF of the applicationbeforethe project, notafter.
It is perfectly fine to include added functionality and changed functionality in the same COSMOS project.