An empirical validation of software cost estimation models
Communications of the ACM
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
Does Code Decay? Assessing the Evidence from Change Management Data
IEEE Transactions on Software Engineering
Writing Effective Use Cases
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
Function Point Measurement Tool for UML Design Specification
METRICS '99 Proceedings of the 6th International Symposium on Software Metrics
Implications of Evolution Metrics on Software Maintenance
ICSM '98 Proceedings of the International Conference on Software Maintenance
Metrics of Software Evolution as Effort Predictors - A Case Study
ICSM '00 Proceedings of the International Conference on Software Maintenance (ICSM'00)
Combining techniques to optimize effort predictions in software project management
Journal of Systems and Software
Project Estimation: A Simple Use-Case-Based Model
IT Professional
ISESE '04 Proceedings of the 2004 International Symposium on Empirical Software Engineering
A Software Product Line Life Cycle Cost Estimation Model
ISESE '04 Proceedings of the 2004 International Symposium on Empirical Software Engineering
An Empirical Study of eServices Product UML Sizing Metrics
ISESE '04 Proceedings of the 2004 International Symposium on Empirical Software Engineering
Proceedings of the 2008 ACM symposium on Applied computing
The size and effort estimates in iterative development
Information and Software Technology
An approach to estimating work effort for enterprise systems software projects
Enterprise Information Systems
Conceptual data model-based software size estimation for information systems
ACM Transactions on Software Engineering and Methodology (TOSEM)
Productivity trends in incremental and iterative software development
ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement
Simplifying effort estimation based on Use Case Points
Information and Software Technology
Towards quantitative software reliability assessment in incremental development processes
Proceedings of the 33rd International Conference on Software Engineering
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
Software effort estimation as a multiobjective learning problem
ACM Transactions on Software Engineering and Methodology (TOSEM) - Testing, debugging, and error handling, formal methods, lifecycle concerns, evolution and maintenance
Hi-index | 0.00 |
This paper describes an industrial study of an effort estimation method based on use cases, the Use Case Points method. The original method was adapted to incremental development and evaluated on a large industrial system with modification of software from the previous release. We modified the following elements of the original method: a) complexity assessment of actors and use cases, and b) the handling of non-functional requirements and team factors that may affect effort. For incremental development, we added two elements to the method: c) counting both all and the modified actors and transactions of use cases, and d) effort estimation for secondary changes of software not reflected in use cases. We finally extended the method to: e) cover all development effort in a very large project. The method was calibrated using data from one release and it produced an estimate for the successive release that was only 17% lower than the actual effort. The study identified factors affecting effort on large projects with incremental development. It also showed how these factors can be calibrated for a specific context and produce relatively accurate estimates.