Sergey Diev
Abstract
This article discusses software size/effort estimation by the Use Case Points method (UCP). It is based on the experience accumulated during deployment of the UCP in a software development department of a major financial institution. Typical for such an environment is that software is developed on top of existing applications, and that there are significant differences between projects in business domains, scope, size, complexity, project management details, etc. In a previous article [3] an extension of the Use Case Points method, called UCPm, was described that addresses these issues.Due to their level, use cases make high-level estimation easier. However, this article, presenting a number of real world situations, demonstrates that to obtain reasonably accurate estimates we need to reflect in use case models some aspects of the existing application and of the current project. It also suggests some clarifications of the concept of use case transaction and outlines some ways to support use case models consistency within and across projects.
- Karner, Gustav. Metrics for Objectory. Diploma thesis, University of Linköping, Sweden. No. LiTHIDA-Ex-9344:21. December 1993.Google Scholar
- Schneider, Geri, Winters, Jason P. Applying Use Cases: A Practical Guide. Addison-Wesley, 1998. Google ScholarDigital Library
- Diev, Sergey. Software estimation in the maintenance context. ACM SIGSOFT Software Engineering Notes. Volume 31, Issue 2 (March 2006), 8 pages. Google ScholarDigital Library
- Function Point Counting Practices Manual. Release 4.2. The International Function Point Users Group, 2004.Google Scholar
Index Terms
- Use cases modeling and software estimation: applying use case points
Recommendations
Applying requirement based complexity for the estimation of software development and testing effort
The need of computing the software complexity in requirement analysis phase of software development life cycle (SDLC) would be an enormous benefit for estimating the required development and testing effort for yet to be developed software. Various ...
Effort estimation model for software development projects based on use case reuse
AbstractThis paper describes a new effort estimation model based on use case reuse, called the use case reusability (UCR), intended for the projects that are reusing artifacts previously developed in past projects with similar scope. Analysis of the ...
This paper describes a new effort estimation model based on use case reuse, called the use case reusability (UCR), intended for the projects that are reusing artifacts previously developed in past projects with similar scope. The baseline for the new ...
The state‐of‐the‐art in software development effort estimation
AbstractThe software developers and researchers have been facing difficulties regarding software development effort estimation (SDEE) since 1960s. Both overestimation and underestimation are problematic for future software development. The software ...
This state‐of‐the‐art review provides an additional insight of existing SDEE models while considering five points of reference: underlying technique, strengths and weaknesses of different models, availability of data sets, data set characteristics, and ...
Comments