Function Point Method Research Articles

Function points in SSADM

A set of explicit counting rules for the use of function point analysis in SSADM v4 is presented, motivated by the need for an unambiguous, objective, and inexpensive measure of system size during the development process. Unadjusted MKII function points can be derived from the requirements specification (RS) phase of SSADM; it is argued that the ‘complexity adjustment’ factor of the standard function point method can be safely omitted. A prescriptive approach is taken, resulting in a repeatable and objective counting technique that may be automated.

An object‐oriented tool for function point analysis

Abstract: Function points have become an accepted measure of software size and are becoming an industry standard. However, the application of function point analysis is fairly complex and requires experience and a good understanding to apply it in a consistent manner. This paper describes the development of a knowledge‐based, object‐oriented system to assist an analyst in performing function point analysis. The objective of the function point analysis (FPA) tool is to allow an analyst to estimate system size in function points without having extensive training or experience using the function point method. The FPA tool uses information available in a functional specification that is a product of the requirements analysis phase of the software development life cycle. An object‐oriented model was used to represent the functional requirements of a software system.

Successful experience of using function points to estimate project costs early in the life-cycle

The paper describes the results of an experiment in software costing. The Mark II Function Point method was used to predict the cost of a number of projects at the Inland Revenue's Information Technology. The results were compared with individual managers' estimates and the actual expenditure. The results give some cause for optimism in the use of the function point model that was used.

Examining the Feasibility of a Case-Based Reasoning Model for Software Effort Estimation

Existing algorithmic models fail to produce accurate software development effort estimates. To address this problem, a case.based reasoning model, called Estor, was developed based on the verbal protocols of a human expert solving a set of estimation problems. Estor was then presented with 15 software effort estimation tasks. The estimates of Estor were compared to those of the expert as well as those of the function point and COCOMO estimations of the projects. The estimates generated by the human expert and Estor were more accurate and consistent than those of the function point and COCOMO methods. In fact, Estor was nearly as accurate and consistent as the expert. These results sug.

An Empirical Validation of a Software Cost Model

An algorithmic model for the estimation of development costs of software, MACOS, is presented. MACOS is based on the function point method for defining the size of the product, adding 32 other factors wich represent the technical complexity of the product and the influence of the environment on the development effort. These 32 factors were selected from the results if a nation-wide survey to people in charge of software development projects. The initial data base included 12 completed projects. The model was checked by an analysis of 20 additional software projects (small to large in size) developed by chilean enterprises. The data for the projects were collected by interviews in order to guarantee fidelity and uniformity. The data for the new projects were included in the data base, giving a refined model for the estimation of software development costs.

Measuring the Productivity of Computer Systems Development Activities with Function Points

The function point method of measuring application development productivity developed by Albrecht is reviewed and a productivity improvement measure introduced. The measurement methodology is then applied to 24 development projects. Size, environment, and language effects on productivity are examined. The concept of a productivity index which removes size effects is defined and an analysis of the statistical significance of results is presented.