Readability and computer documentation
ACM Journal of Computer Documentation (JCD)
The relevance of software documentation, tools and technologies: a survey
Proceedings of the 2002 ACM symposium on Document engineering
An Overview of Industrial Software Documentation Practice
SCCC '02 Proceedings of the XII International Conference of the Chilean Computer Science Society
An approach to program understanding by natural language understanding
Natural Language Engineering
Fine-grained processing of CVS archives with APFEL
eclipse '06 Proceedings of the 2006 OOPSLA workshop on eclipse technology eXchange
Analyzing the co-evolution of comments and source code
Software Quality Control
Expect the unexpected: error code mismatches between documentation and the real world
Proceedings of the 9th ACM SIGPLAN-SIGSOFT workshop on Program analysis for software tools and engineering
Automatic quality assessment of source code comments: the JavadocMiner
NLDB'10 Proceedings of the Natural language processing and information systems, and 15th international conference on Applications of natural language to information systems
Static extraction of program configuration options
Proceedings of the 33rd International Conference on Software Engineering
Proceedings of the 2013 International Conference on Software and System Process
Detecting API documentation errors
Proceedings of the 2013 ACM SIGPLAN international conference on Object oriented programming systems languages & applications
Data & Knowledge Engineering
Hi-index | 0.00 |
Good source code documentation, especially of programming interfaces, is essential for using and maintaining software components. In this paper, we present the Quasoledo tool that automatically measures the quality of documentation with respect to completeness, quantity, and readability. We applied our set of metrics to the Eclipse project, and benchmarked against the well-documented Java class library. The result of Quasoledo is a map of documentation quality in Eclipse, showing the best documentation for its core components. Additionally, we looked at the evolution of Eclipse and identified batch updates that caused jumps in documentation quality. For Eclipse, only 32.6% of all changes touched documentation.