The relevance of software documentation, tools and technologies: a survey
Proceedings of the 2002 ACM symposium on Document engineering
The Journal of Machine Learning Research
Source Code Retrieval for Bug Localization Using Latent Dirichlet Allocation
WCRE '08 Proceedings of the 2008 15th Working Conference on Reverse Engineering
Mining the coherence of GNOME bug reports with statistical topic models
MSR '09 Proceedings of the 2009 6th IEEE International Working Conference on Mining Software Repositories
Measuring API documentation on the web
Proceedings of the 2nd International Workshop on Web 2.0 for Software Engineering
Facing up to the inequality of crowdsourced API documentation
ACM SIGSOFT Software Engineering Notes
What makes a good code example?: A study of programming Q&A in StackOverflow
ICSM '12 Proceedings of the 2012 IEEE International Conference on Software Maintenance (ICSM)
Fit or unfit: analysis and prediction of 'closed questions' on stack overflow
Proceedings of the first ACM conference on Online social networks
Hi-index | 0.00 |
A project's documentation is the primary source of information for developers using that project. With hundreds of thousands of programming-related questions posted on programming Q&A websites, such as Stack Overflow, we question whether the developer-written documentation provides enough guidance for programmers. In this study, we wanted to know if there are any topics which are inadequately covered by the project documentation. We combined questions from Stack Overflow and documentation from the PHP and Python projects. Then, we applied topic analysis to this data using latent Dirichlet allocation (LDA), and found topics in Stack Overflow that did not overlap the project documentation. We successfully located topics that had deficient project documentation. We also found topics in need of tutorial documentation that were outside of the scope of the PHP or Python projects, such as MySQL and HTML.