Using a Combination of Measurement Tools to Extract Metrics from Open Source Projects

Software measurement can play a major role in ensuring the quality and reliability of software products. The measurement activities require appropriate tools to collect relevant metric data. Currently, there are several such tools available for software measurement. The main objective of this paper is to provide some guidelines in using a combination of multiple measurement tools especially for products built using object-oriented techniques and languages. In this paper, we highlight three tools for collecting metric data, in our case from several Java-based open source projects. Our research is currently based on the work of Card and Glass, who argue that design complexity measures (data complexity and structural complexity) are indicators/predictors of procedural/cyclomatic complexity (decision counts) and errors (discovered from system tests). Their work was centered on structured design and our work is with object-oriented designs and the metrics we use parallel those of Card and Glass, being, Henry and Kafura's Information Flow Metrics, McCabe's Cyclomatic Complexity, and Chidamber and Kemerer Object-oriented Metrics

An estimate of necessary effort in the development of software projects

International Workshop on Intelligent Technologies for Software Engineering (WITSE'04). 19th IEEE International Conference on Automated Software Engineering (Linz, Austria, September 20th - 25th, 2004)The estimated of the effort in the development of software projects has already been studied in the field of software engineering. For this purpose different ways of measurement such as Unes of code and function points, generally addressed to relate software size with project cost (effort) have been used. In this work we are presenting a research project that deals with this field, us'mg machine learning techniques to predict the software project cost. Several public set of data are used. The analysed sets of data only relate the effort invested in the development of software projects and the size of the resultant code. For this reason, we can say that the data used are poor. Despite that, the results obtained are good, because they improve the ones obtained in previous analyses. In order to get results closer to reality we should find data sets of a bigger size that take into account more variables, thus offering more possibilities to obtain solutions in a more efficient way.Publicad