Property-Based Software Engineering Measurement
IEEE Transactions on Software Engineering
Counterpoint: The Problem with Function Points
IEEE Software
An Empirical Study of the Correlations Between Function Point Elements
METRICS '99 Proceedings of the 6th International Symposium on Software Metrics
Estimating Effort by Use Case Points: Method, Tool and Case Study
METRICS '04 Proceedings of the Software Metrics, 10th International Symposium
Introducing the evaluation of complexity in functional size measurement: a UML-based approach
Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
Traceable complexity metric from requirements to code
Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
The role of the measure of functional complexity in effort estimation
Proceedings of the 6th International Conference on Predictive Models in Software Engineering
Simplifying effort estimation based on Use Case Points
Information and Software Technology
Towards an early software estimation using log-linear regression and a multilayer perceptron model
Journal of Systems and Software
On the relationship between use cases and test suites size: an exploratory study
ACM SIGSOFT Software Engineering Notes
| Hi-index | 0.00 |
The fact that Albrecht's function point method must be frequently improved or adjusted to suit new development contexts shows that there is a need for a new approach to early estimate effort. Such approach should reduce the estimation error and it is convenient for it to be based on use cases. The authors defined two simple metrics which capture two key aspects of software applications, size and complexity, which are called Transactions (T) and Paths (P). Also, in order to demonstrate that it is possible to reduce the error of effort estimation using these two new metrics, a case study was developed.