References

[1] Gentleman R C, Carey V J, Bates D M. Bioconductor: open software development for computational biology and bioinformatics.. Genome Biol, 2004, 5: R80 CrossRef PubMed Google Scholar http://scholar.google.com/scholar_lookup?title=Bioconductor: open software development for computational biology and bioinformatics.&author=Gentleman R C&author=Carey V J&author=Bates D M&publication_year=2004&journal=Genome Biol&volume=5&pages=R80

[2] Forward A, Lethbridge T C. The relevance of software documentation, tools and technologies: a survey. In: Proceedings of the 2002 ACM Symposium on Document engi-neering. New York: ACM, 2002. 26--33. Google Scholar http://scholar.google.com/scholar_lookup?title=Forward A, Lethbridge T C. The relevance of software documentation, tools and technologies: a survey. In: Proceedings of the 2002 ACM Symposium on Document engi-neering. New York: ACM, 2002. 26--33&

[3] 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. Google Scholar http://scholar.google.com/scholar_lookup?title=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&

[4] Dekel U, Herbsleb J D. Improving api documentation usability with knowledge pushing. In: Proceedings of the 31st International Conference on Software Engineering. IEEE Computer Society, 2009. 320--330. Google Scholar http://scholar.google.com/scholar_lookup?title=Dekel U, Herbsleb J D. Improving api documentation usability with knowledge pushing. In: Proceedings of the 31st International Conference on Software Engineering. IEEE Computer Society, 2009. 320--330&

[5] 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. Google Scholar http://scholar.google.com/scholar_lookup?title=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&

[6] Uddin G, Robillard M P. How API documentation fails. IEEE Software, 2015, 32: 68--75. Google Scholar http://scholar.google.com/scholar_lookup?title=Uddin G, Robillard M P. How API documentation fails. IEEE Software, 2015, 32: 68--75&

[7] 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. Google Scholar http://scholar.google.com/scholar_lookup?title=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&

[8] 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. Google Scholar http://scholar.google.com/scholar_lookup?title=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&