IEEE Transactions on Software Engineering
Extraction of Function-Points from Source-Code
IWSM '00 Proceedings of the 10th International Workshop on New Approaches in Software Measurement
Communications of the ACM - Homeland security
Cost estimation for global software development
Proceedings of the 2006 international workshop on Economics driven software engineering research
Calibrated estimation model for a maintenance project
SEA '07 Proceedings of the 11th IASTED International Conference on Software Engineering and Applications
On the relationship between functional size and software code size
Proceedings of the 2010 ICSE Workshop on Emerging Trends in Software Metrics
Categorization of real-time software components for code size estimation
Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
An investigation of using neuro-fuzzy with software size estimation
WOSQ'09 Proceedings of the Seventh ICSE conference on Software quality
An empirical model of technical debt and interest
Proceedings of the 2nd Workshop on Managing Technical Debt
Assessing programming language impact on development and maintenance: a study on c and c++
Proceedings of the 33rd International Conference on Software Engineering
| Hi-index | 4.11 |
The availability of empirical data from projects that use both function-point and lines-of-code metrics has led to a useful technique called backfiring. Backfiring is the direct mathematical conversion of LOC data into equivalent function-point data. Because the backfiring equations are bidirectional, they also provide a powerful way of sizing, or predicting, source-code volume for any known programming language or combination of languages. The function-point metric, invented by A.J. Albrecht of IBM in the middle 1970s, is a synthetic metric derived by a weighted formula that includes five elements: inputs, outputs, logical files, inquiries, and interfaces. IBM put it into the public domain in 1979, and its use spread rapidly, particularly after the formation of the International Function Point Users Group (IFPUG) in the mid-1980s. By then, hundreds of software projects had been measured using both function points and lines of source code. Since an application's function-point total is independent of the source code, this dual analysis has led to several important discoveries