Object-oriented development in an industrial environment
OOPSLA '87 Conference proceedings on Object-oriented programming systems, languages and applications
Software engineering metrics and models
Software engineering metrics and models
Object-oriented software engineering
Object-oriented software engineering
Software sizing and estimating: Mk II FPA (Function Point Analysis)
Software sizing and estimating: Mk II FPA (Function Point Analysis)
Applying use cases: a practical guide
Applying use cases: a practical guide
Software size measurement and productivity rating in a large-scale software development department
Proceedings of the 20th international conference on Software engineering
Writing Effective Use Cases
Patterns for Effective Use Cases
Patterns for Effective Use Cases
Software Cost Estimation with Cocomo II with Cdrom
Software Cost Estimation with Cocomo II with Cdrom
Software Metrics: A Rigorous and Practical Approach
Software Metrics: A Rigorous and Practical Approach
Counterpoint: The Problem with Function Points
IEEE Software
A Comparison of Function Point Counting Techniques
IEEE Transactions on Software Engineering
Estimating Software Development Effort Based on Use Cases-Experiences from Industry
«UML» '01 Proceedings of the 4th International Conference on The Unified Modeling Language, Modeling Languages, Concepts, and Tools
An Empirical Study of the Correlations Between Function Point Elements
METRICS '99 Proceedings of the 6th International Symposium on Software Metrics
Requirements Engineering: The State of the Practice
IEEE Software
Introduction to Machine Learning (Adaptive Computation and Machine Learning)
Introduction to Machine Learning (Adaptive Computation and Machine Learning)
IEEE Transactions on Software Engineering
Effort estimation of use cases for incremental large-scale software development
Proceedings of the 27th international conference on Software engineering
Estimating software based on use case points
OOPSLA '05 Companion to the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Software estimation in the maintenance context
ACM SIGSOFT Software Engineering Notes
Software Effort Estimation Based on Use Cases
COMPSAC '06 Proceedings of the 30th Annual International Computer Software and Applications Conference - Volume 01
Use cases modeling and software estimation: applying use case points
ACM SIGSOFT Software Engineering Notes
Automatic Transactions Identification in Use Cases
Balancing Agility and Formalism in Software Engineering
The IT Measurement Compendium: Estimating and Benchmarking Success with Functional Size Measurement
The IT Measurement Compendium: Estimating and Benchmarking Success with Functional Size Measurement
Transactions and paths: Two use case based metrics which improve the early effort estimation
ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement
Improving the reliability of transaction identification in use cases
Information and Software Technology
Towards an early software estimation using log-linear regression and a multilayer perceptron model
Journal of Systems and Software
Value estimation of the use case parameters using SOM and fuzzy rules
Proceedings of the International Conference on Management of Emergent Digital EcoSystems
Proceedings of the 5th ACM SIGCHI symposium on Engineering interactive computing systems
Hi-index | 0.00 |
Context: The Use Case Points (UCP) method can be used to estimate software development effort based on a use-case model and two sets of adjustment factors relating to the environmental and technical complexity of a project. The question arises whether all of these components are important from the effort estimation point of view. Objective: This paper investigates the construction of UCP in order to find possible ways of simplifying it. Method: The cross-validation procedure was used to compare the accuracy of the different variants of UCP (with and without the investigated simplifications). The analysis was based on data derived from a set of 14 projects for which effort ranged from 277 to 3593 man-hours. In addition, the factor analysis was performed to investigate the possibility of reducing the number of adjustment factors. Results: The two variants of UCP - with and without unadjusted actor weights (UAW) provided similar prediction accuracy. In addition, a minor influence of the adjustment factors on the accuracy of UCP was observed. The results of the factor analysis indicated that the number of adjustment factors could be reduced from 21 to 6 (2 environmental factors and 4 technical complexity factors). Another observation was made that the variants of UCP calculated based on steps were slightly more accurate than the variants calculated based on transactions. Finally, a recently proposed use-case-based size metric TTPoints provided better accuracy than any of the investigated variants of UCP. Conclusion: The observation in this study was that the UCP method could be simplified by rejecting UAW; calculating UCP based on steps instead of transactions; or just counting the total number of steps in use cases. Moreover, two recently proposed use-case-based size metrics Transactions and TTPoints could be used as an alternative to UCP to estimate effort at the early stages of software development.