Description: Function point is a unit of measurement that quantifies the functions in a software application, allowing for the evaluation of its size and complexity. It is based on the functionality that the software provides to the user, rather than on the code or development effort. This metric is used to estimate the effort required to develop, maintain, and manage applications, facilitating project planning and control. Function points are classified into five types: external inputs, external outputs, inquiries, internal files, and external files. Each of these types is evaluated based on its complexity, allowing for the assignment of a numerical value that represents its contribution to the total function points of the application. This methodology is particularly useful in various software development practices, as it enables development teams to have a clear view of the project scope and tasks to be performed, promoting better collaboration and communication among team members. Additionally, the use of function points helps project managers make comparisons between different projects and establish performance metrics, resulting in more efficient and effective management of resources and delivery timelines.
History: The concept of function point was developed in the 1970s by Allan Albrecht, an engineer at IBM, as part of an effort to improve cost and time estimation in software development. In 1979, Albrecht presented his methodology at a conference, leading to its adoption in the software industry. Over the years, the technique has evolved and been standardized, being formally recognized by the International Function Point Users Group (IFPUG) in 1986. Since then, various versions and guidelines for its application have been developed, adapting to the changing needs of the industry.
Uses: Function points are primarily used in estimating the costs and development times of software, as well as in project management. They allow project managers to assess the size of an application and anticipate the resources needed for its development. They are also useful for measuring the productivity of the development team and for making comparisons between different projects or software versions. Additionally, they are used in software audits and in evaluating software quality.
Examples: A practical example of using function points is in a software development company that is creating an inventory management system. By identifying the functions of the system, such as data entry for products, report generation, and stock inquiries, the team can calculate the total function points. This allows them to estimate the time and resources needed to complete the project. Another example is in planning a customer management system, where the required functionalities and their complexity can be assessed to determine the development effort.
