Effort estimation of use cases for incremental large-scale software development
Proceedings of the 27th international conference on Software engineering
Impact and contributions of MBASE on software engineering graduate courses
Journal of Systems and Software
Comparative study on applicability of two novel effort estimation models in web projects
ECC'10 Proceedings of the 4th conference on European computing conference
Two novel effort estimation models based on quality metrics in web projects
WSEAS Transactions on Information Science and Applications
Towards an ontology-based retrieval of UML Class Diagrams
Information and Software Technology
Evolving an experience base for software process research
SPW'05 Proceedings of the 2005 international conference on Unifying the Software Process Spectrum
Information and Software Technology
| Hi-index | 0.00 |
Size is one of the most fundamental measurements of software. For the past two decades, the source line of code (SLOC) and function point (FP) metrics have been dominating software sizing approaches. However both approaches have significant defects. For example, SLOC can only be counted when the software construction is complete, while the FP counting is time consuming, expensive, and subjective. In the late 1990s researchers have been exploring faster, cheaper, and more effective sizing methods, such as Unified Modeling Language (UML) based software sizing. In this paper we present an empirical 14-project-study of three different sizing metrics which cover different software life-cycle activities: requirement metrics (requirement), UML metrics (architecture), and SLOC metrics (implementation). Our results show that the software size in terms of SLOC was moderately well correlated with the number of external use cases and the number of classes. We also demonstrate that the number of sequence diagram steps per external use case is a possible complexity indicator of software size. However, we conclude that at least for this 14-project e-Services applications sample, the UML-based metrics were insufficiently well-defined and codified to serve as precise sizing metrics.