Applying use cases: a practical guide
Applying use cases: a practical guide
Software estimation in the maintenance context
ACM SIGSOFT Software Engineering Notes
Structuring complex requirements
ACM SIGSOFT Software Engineering Notes
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
Reliability of transaction identification in use cases
Proceedings of the Workshop on Advances in Functional Size Measurement and Effort Estimation
Simplifying effort estimation based on Use Case Points
Information and Software Technology
Improving the reliability of transaction identification in use cases
Information and Software Technology
CEE-SET'08 Proceedings of the Third IFIP TC 2 Central and East European conference on Software engineering techniques
iUCP – estimating interaction design projects with enhanced use case points
TAMODIA'09 Proceedings of the 8th international conference on Task Models and Diagrams for User Interface Design
Towards an early software estimation using log-linear regression and a multilayer perceptron model
Journal of Systems and Software
| Hi-index | 0.00 |
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.