Identifying poorly documented object oriented software components

Authors:
Parag C. Pendharkar
Affiliations:
School of Business Administration, Pennsylvania State University at Harrisburg, 777 West Harrisburg Pike, Middletown, PA 17057, USA. Tel.: +1 717 948 6028/ Fax: +1 717 948 6456/ E-mail: pxp19@psu. ...
Venue:
International Journal of Hybrid Intelligent Systems
Year:
2009

Citing 22
Cited 0

Software Size Estimation of Object-Oriented Systems

IEEE Transactions on Software Engineering
Software complexity: measures and methods

Software complexity: measures and methods
A Software Size Model

IEEE Transactions on Software Engineering
A neural network approach for early detection of program modules having high risk in the maintenance phase

Selected papers of the sixth annual Oregon workshop on Software metrics
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
Corrigenda: a hierarchy-aware approach to faceted classification of object-oriented components

ACM Transactions on Software Engineering and Methodology (TOSEM)
Data mining: practical machine learning tools and techniques with Java implementations

Data mining: practical machine learning tools and techniques with Java implementations
A Validation of the Component-Based Method for Software Size Estimation

IEEE Transactions on Software Engineering - special section on current trends in exception handling—part II
An empirical study of factors impacting the size of object-oriented component code documentation

Proceedings of the 20th annual international conference on Computer documentation
Improving Size Estimates Using Historical Data

IEEE Software
A Metrics Suite for Object Oriented Design

IEEE Transactions on Software Engineering
What we can learn from extreme programming

Journal of Computing Sciences in Colleges
Identifying High Performance ERP Projects

IEEE Transactions on Software Engineering
When Can We Test Less?

METRICS '03 Proceedings of the 9th International Symposium on Software Metrics
Software Engineering: A Practitioner's Approach (McGraw-Hill Series in Computer Science)

Software Engineering: A Practitioner's Approach (McGraw-Hill Series in Computer Science)
An exploratory study of object-oriented software component size determinants and the application of regression tree forecasting models

Information and Management
Automatic goal-oriented classification of failure behaviors for testing XML-based multimedia software applications: An experimental case study

Journal of Systems and Software - Special issue: Quality software
Optimal resource allocation for cost and reliability of modular software systems in the testing phase

Journal of Systems and Software - Special issue: Quality software
Hybrid Intelligence in Software Release Planning

International Journal of Hybrid Intelligent Systems
Evolutionary reinforcement learning of artificial neural networks

International Journal of Hybrid Intelligent Systems - Hybridization of Intelligent Systems
How good is your blind spot sampling policy

HASE'04 Proceedings of the Eighth IEEE international conference on High assurance systems engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

Recent research suggests that software testing consumes substantial resources and documenting source code is one way to reduce software maintenance cost. The software engineering literature provides little information on how to establish whether a software component is adequately documented. It appears that benchmarking can be used to identify a software component with little or no documentation. In this paper, we propose and illustrate how a hybrid Data Envelopment Analysis (DEA), Kohonen self-organizing mapping, and Euclidean distance based algorithm can be used to identify poorly documented software components.