AFP — automated function point counting tool that utilizes source code may encourage sloppiness over elegance

9. Software engineers are often incented to write more lines of code rather than fewer. The propensity to write more “code” may be represented in productivity measures (though not good ones), driven by ego (a desire to write more than their peers), or poor engineering skills (poor design or implementation2). Research suggests that size is not related to a developer only, but also to the familiarity of the developer with the problem being solved. Again, the proclivity to “write more code” is associated with poor designs, more defects, and higher support costs. So, an automated function point counting tool that utilizes source code may encourage sloppiness over elegance. Worse, the foreknowledge that the code will be measured may inspire the developer to add functionality that increases the generated size. Unfortunately, this reaction will increase product volatility and further remove the product from what was contracted to what looks “bigger” (e.g., more valuable from the developer’s (versus the customer’s) perspective).

This is a problem in how Function Point counts are used in productivity analysis rather than in the specification. This and many other points must be considered to valid data and guide improvements.
Revised Text:
>none<
Disposition: Closed, no change