Software Cost Estimation with Cocomo II with Cdrom
Software Cost Estimation with Cocomo II with Cdrom
Counterpoint: The Problem with Function Points
IEEE Software
Object Oriented Design Function Points
APAQS '00 Proceedings of the The First Asia-Pacific Conference on Quality Software (APAQS'00)
Definition and Experimental Evaluation of Function Points for Object-Oriented Systems
METRICS '98 Proceedings of the 5th International Symposium on Software Metrics
Function Point Measurement Tool for UML Design Specification
METRICS '99 Proceedings of the 6th International Symposium on Software Metrics
The Rational Unified Process: An Introduction
The Rational Unified Process: An Introduction
Applying Function Point to Unified Modeling Language: Conversion Model and Pilot Study
METRICS '04 Proceedings of the Software Metrics, 10th International Symposium
Extending Function Point Analysis of Object-Oriented Requirements Specifications
METRICS '05 Proceedings of the 11th IEEE International Software Metrics Symposium
Quality gates in use-case driven development
Proceedings of the 2006 international workshop on Software quality
Synergia: a software engineering laboratory to bridge the gap between university and industry
Proceedings of the 2006 international workshop on Summit on software engineering education
The study of resource allocation among software development phases: an economics-based approach
Advances in Software Engineering
Using UML stereotypes to support the requirement engineering: a case study
ICCSA'12 Proceedings of the 12th international conference on Computational Science and Its Applications - Volume Part IV
Hi-index | 0.00 |
Function Point Analysis (FPA) is a widely used technique for measuring software size. It measures software functionality from the user's perspective, usually based on a requirements description. In many software processes, these requirements are represented by UML models. Although there have been attempts to automate the measurement process, FPA counting requires a considerable amount of interpretation which, to be reliable, should be made by experts. On the other hand, fully manual counting methods usually fail to keep synchronized with the requirements model, since requirements frequently change during the development cycle. This paper describes an approach for counting FPA and a compliant tool. This approach makes use of UML requirement models. The tool, called ReMoFP (Requirement Model Function Point counter), leaves all the counting decisions to the analyst, but supports him by ensuring consistency with the requirements represented in the models. The ReMoFP was developed by a software development laboratory in Brazil, and helped it to improve counting productivity, consistency, and maintainability.