A challenge in implementing Function Point Analysis (FPA) is making it understandable to developers, cost analysts, and customers alike. Because Function Points are based on functional user requirements (what the software does), irrespective of the physical implementation (how the software is implemented), users of the method must think in terms of the logical functional requirements. This article discusses difficulties that arise with developers and clarifies a number of terms that often cause confusion.