An empirical study of factors impacting the size of object-oriented component code documentation

Authors:
Parag C. Pendharkar;James A. Rodger
Affiliations:
Penn State Harrisburg, Middletown, PA;Indiana University of Pennsylvania, Indiana, PA
Venue:
Proceedings of the 20th annual international conference on Computer documentation
Year:
2002

Citing 7
Cited 4

Software complexity: measures and methods

Software complexity: measures and methods
Object-oriented software metrics: a practical guide

Object-oriented software metrics: a practical guide
A field study of scale economies in software maintenance

Management Science - Special issue: Frontier research on information systems and economics
Effort estimation and prediction of object-oriented systems

Journal of Systems and Software
Improving Size Estimates Using Historical Data

IEEE Software
Empirically Guided Software Effort Guesstimation

IEEE Software
A Metrics Suite for Object Oriented Design

IEEE Transactions on Software Engineering

Identifying poorly documented object oriented software components

International Journal of Hybrid Intelligent Systems
An automated procedure for identifying poorly documented object oriented software components

C3S2E '09 Proceedings of the 2nd Canadian Conference on Computer Science and Software Engineering
Improving Web Service descriptions for effective service discovery

Science of Computer Programming
Empirically assessing the impact of dependency injection on the development of web service applications

Journal of Web Engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

In this paper, we identify a set of factors that may be used to forecast source code documentation for object oriented software components. Using field data on 152 object oriented (OO) software components and the multiple regression model, we empirically test the impact of proposed factors on the prediction of OO source code documentation. Our results indicate that the number of methods, the number of sub-classes, the number of GUI elements and the number of events handled all increase the number of lines of code for OO source code documentation. Additionally, we show that scale economies exist in OO source code documentation and use non-linear regression model Classification and Regression Tree (CART) to improve OO source code documentation forecasting accuracy.