1. Albrecht, A. J. (1979). Measuring Application Development Productivity. In Proceedings of the Joint SHARE/GUIDE/IBM Application Development Symposium, Monterey, California (pp. 83-92). IBM Corporation.
Reference Detail: In this foundational paper, Albrecht introduces Function Points as a measure of the "function value delivered to the user" (Section: "A New Way of Sizing and Estimating"). He explicitly contrasts this with Lines of Code, which he notes is language-dependent and a poor measure of productivity and value.
2. International Function Point Users Group (IFPUG). (2010). Function Point Counting Practices Manual (CPM), Release 4.3.1.
Reference Detail: Chapter 1, Section 1.1, "Introduction," defines Function Point Analysis as a method for "sizing software based on the functions that are perceived by the user." The manual's methodology is based on identifying logical user functions (e.g., inputs, outputs, inquiries) and has no component for counting physical lines of code.
3. Garmus, D., & Herron, D. (2001). Function Point Analysis: Measurement Practices for Successful Software Projects. Addison-Wesley Professional.
Reference Detail: Chapter 2, "Function Point Fundamentals," states, "Function points are a unit of measure for software size... They are independent of technology. For example, a project's function point count will not change regardless of the language, development tools, or hardware platform used." This directly contradicts the idea that they measure LOC, which is language-specific.