References
Gentleman R C, Carey V J, Bates D M, et al. Bioconductor: open software development for computational biology and bioinformatics. Genome Biol, 2004, 5: R80
Forward A, Lethbridge T C. The relevance of software documentation, tools and technologies: a survey. In: Proceedings of the 2002 ACM Symposium on Document Engineering. New York: ACM, 2002. 26–33
Roehm T, Tiarks R, Koschke R, et al. How do professional developers comprehend software? In: Proceedings of the 34th International Conference on Software Engineering. New York: IEEE Press, 2012. 255–265
Dekel U, Herbsleb J D. Improving api documentation usability with knowledge pushing. In: Proceedings of the 31st International Conference on Software Engineering. Washington: IEEE Computer Society, 2009. 320–330
Chen C, Zhang K. Who asked what: integrating crowdsourced faqs into api documentation. In: Proceedings of the 36th International Conference on Software Engineering. New York: ACM, 2014. 456–459
Hartmann B, Dhillon M, Chan M K. Hypersource: bridging the gap between source and code-related web sites. In: Proceedings of the SIGCHI Conference on Human Factors in Computing Systems. New York: ACM, 2011. 2207–2210
Linares-Vasquez M, Bavota G, Di Penta M, et al. How do api changes trigger stack overflow discussions? a study on the android sdk. In: Proceedings of the 22nd International Conference on Program Comprehension. New York: ACM, 2014. 83–94
Acknowledgements
This work was supported by National Grand R&D Plan (Grant No. 2018-YFB1004202) and National Natural Science Foundation of China (Grant No. 61702534).
Author information
Authors and Affiliations
Corresponding authors
Rights and permissions
About this article
Cite this article
Fan, Q., Yu, Y., Wang, T. et al. Why API documentation is insufficient for developers: an empirical study. Sci. China Inf. Sci. 64, 119102 (2021). https://doi.org/10.1007/s11432-019-9880-8
Received:
Revised:
Accepted:
Published:
DOI: https://doi.org/10.1007/s11432-019-9880-8