Nothing Special   »   [go: up one dir, main page]

skip to main content
10.1109/ICSE.2019.00122acmconferencesArticle/Chapter ViewAbstractPublication PagesicseConference Proceedingsconference-collections
research-article

Software documentation issues unveiled

Published: 25 May 2019 Publication History

Abstract

(Good) Software documentation provides developers and users with a description of what a software system does, how it operates, and how it should be used. For example, technical documentation (e.g., an API reference guide) aids developers during evolution/maintenance activities, while a user manual explains how users are to interact with a system. Despite its intrinsic value, the creation and the maintenance of documentation is often neglected, negatively impacting its quality and usefulness, ultimately leading to a generally unfavorable take on documentation.
Previous studies investigating documentation issues have been based on surveying developers, which naturally leads to a somewhat biased view of problems affecting documentation. We present a large scale empirical study, where we mined, analyzed, and categorized 878 documentation-related artifacts stemming from four different sources, namely mailing lists, Stack Overflow discussions, issue repositories, and pull requests. The result is a detailed taxonomy of documentation issues from which we infer a series of actionable proposals both for researchers and practitioners.

References

[1]
A. Forward and T. C. Lethbridge, "The Relevance of Software Documentation, Tools and Technologies: A Survey," in Proc. of the 2002 ACM Symp. on Doc. Eng. (DocEng). ACM, 2002, pp. 26--33.
[2]
T. C. Lethbridge, J. Singer, and A. Forward, "How software engineers use documentation: The state of the practice," IEEE Softw., vol. 20, no. 6, pp. 35--39, Nov. 2003.
[3]
M. Kajko-Mattsson, "A Survey of Documentation Practice within Corrective Maintenance," Empirical Software Engineering, vol. 10, no. 1, pp. 31--55, 2005.
[4]
J. Zhi, V. Garousi-Yusifoglu, B. Sun, G. Garousi, S. Shahnewaz, and G. Ruhe, "Cost, benefits and quality of software development documentation: A systematic mapping," Journal of Systems and Software, vol. 99, pp. 175--198, 2015.
[5]
B. Fluri, M. Wursch, and H. C. Gall, "Do code and comments co-evolve? on the relation between source code and comment changes," in WCRE'07, Oct 2007, pp. 70--79.
[6]
J. C. Chen and S. J. Huang, "An empirical analysis of the impact of software development problem factors on software maintainability," Journal of Systems and Software, vol. 82, no. 6, pp. 981--992, 2009.
[7]
M. Linares-Vásquez, B. Li, C. Vendome, and D. Poshyvanyk, "How do developers document database usages in source code? (n)," in ASE'15, Nov 2015, pp. 36--41.
[8]
P. W. McBurney and C. McMillan, "Automatic source code summarization of context for Java methods," IEEE Transactions on Software Engineering, vol. 42, no. 2, pp. 103--119, Feb 2016.
[9]
M. P. Robillard, A. Marcus, C. Treude, G. Bavota, O. Chaparro, N. Ernst, M. A. Gerosa, M. Godfrey, M. Lanza, M. Linares-Vásquez, G. C. Murphy, L. Moreno, D. Shepherd, and E. Wong, "On-demand Developer Documentation," in Proc. of the 33rd IEEE Int. Conf. on Software Maintenance and Evolution (ICSME), sep 2017, pp. 479--483.
[10]
R. Lotufo, Z. Malik, and K. Czarnecki, "Modelling the 'hurried' bug report reading process to summarize bug reports," in Proc. of the 28th IEEE Int. Conf. on Soft. Maintenance (ICSM), Sept 2012, pp. 430--439.
[11]
S. Mani, R. Catherine, V. S. Sinha, and A. Dubey, "AUSUM: Approach for unsupervised bug report summarization," in Proc. of the ACM SIGSOFT 20th Int. Symp. on the Foundations of Software Engineering, ser. FSE '12. New York, NY, USA: ACM, 2012, pp. 11:1--11:11.
[12]
S. Rastkar, G. C. Murphy, and G. Murray, "Automatic Summarization of Bug Reports," IEEE Trans. on Soft. Eng., vol. 40, no. 4, 2014.
[13]
S. Haiduc, J. Aponte, L. Moreno, and A. Marcus, "On the use of automated text summarization techniques for summarizing source code," in Proc. of the 17th Working Conf. on Rev. Eng., Oct 2010, pp. 35--44.
[14]
G. Sridhara, E. Hill, D. Muppaneni, L. Pollock, and K. Vijay-Shanker, "Towards automatically generating summary comments for Java methods," in Proc. of the IEEE/ACM Int. Conf. on Automated Software Engineering, 2010, pp. 43--52.
[15]
L. Moreno, J. Aponte, G. Sridhara, A. Marcus, L. Pollock, and V. Shanker, "Automatic Generation of Natural Language Summaries for Java Classes," in 21st IEEE Int. Conf. on Program Comprehension (ICPC'13). San Francisco, USA: IEEE, 2013, pp. 23--32.
[16]
P. Rodeghero, C. McMillan, P. W. McBurney, N. Bosch, and S. D'Mello, "Improving automated source code summarization via an eye-tracking study of programmers," in Proc. of the 36th Int. Conf. on Software Engineering (ICSE 2014). ACM, 2014, pp. 390--401.
[17]
P. W. McBurney and C. McMillan, "Automatic documentation generation via source code summarization of method context," in Proc. of the 22nd Int. Conf. on Program Comprehension (ICPC 2014). ACM, 2014, pp. 279--290.
[18]
P. W. McBurney, C. Liu, C. McMillan, and T. Weninger, "Improving topic model source code summarization," in Proc. of the 22nd Int. Conf. on Program Comprehension (ICPC 2014). ACM, 2014, pp. 291--294.
[19]
M. Linares-Vásquez, B. Li, C. Vendome, and D. Poshyvanyk, "Documenting database usages and schema constraints in database-centric applications," in Proc. of the 25th Int. Symp. on Software Testing and Analysis (ISSTA 2016). ACM, 2016, pp. 270--281.
[20]
S. Panichella, A. Panichella, M. Beller, A. Zaidman, and H. C. Gall, "The impact of test case summaries on bug fixing performance: An empirical investigation," in Proc. of the 38th Int. Conf. on Software Engineering (ICSE 2016). ACM, 2016, pp. 547--558.
[21]
B. Li, C. Vendome, M. Linares-Vásquez, D. Poshyvanyk, and N. A. Kraft, "Automatically documenting unit test cases," in Proc. of the IEEE Int. Conf. on Software Testing, Verification and Validation (ICST 2016), April 2016, pp. 341--352.
[22]
L. F. Cortés-Coy, M. Linares-Vásquez, J. Aponte, and D. Poshyvanyk, "On automatically generating commit messages via summarization of source code changes," in Proc. of the IEEE 14th Int. Working Conf. on Source Code Analysis and Manipulation, Sept 2014, pp. 275--284.
[23]
M. Linares-Vásquez, L. F. Cortés-Coy, J. Aponte, and D. Poshyvanyk, "ChangeScribe: A tool for automatically generating commit messages," in 2015 IEEE/ACM 37th IEEE Int. Conf. on Software Engineering, vol. 2, May 2015, pp. 709--712.
[24]
S. Jiang and C. McMillan, "Towards automatic generation of short summaries of commits," in Proc. of the 25th IEEE/ACM Int. Conf. on Program Comprehension (ICPC 2017), May 2017, pp. 320--323.
[25]
L. Moreno, G. Bavota, M. Di Penta, R. Oliveto, A. Marcus, and G. Canfora, "Automatic generation of release notes," in Proc. of the 22nd ACM SIGSOFT Int. Symp. on Foundations of Software Engineering (FSE 2014). ACM, 2014, pp. 484--495.
[26]
L. Moreno, G. Bavota, M. D. Penta, R. Oliveto, A. Marcus, and G. Canfora, "ARENA: An approach for the automated generation of release notes," IEEE Trans. on Soft. Eng., vol. 43, no. 2, Feb 2017.
[27]
A. Di Sorbo, S. Panichella, C. V. Alexandru, J. Shimagaki, C. A. Visaggio, G. Canfora, and H. C. Gall, "What would users change in my app? Summarizing app reviews for recommending software changes," in Proc. of the 24th ACM SIGSOFT Int. Symp. on Foundations of Software Engineering (FSE 2016). ACM, 2016, pp. 499--510.
[28]
A. T. T. Ying and M. P. Robillard, "Code fragment summarization," in Proc. of the 9th Joint Meeting on Foundations of Software Engineering (ESEC/FSE 2013). ACM, 2013, pp. 655--658.
[29]
R. Krasniqi, S. Jiang, and C. McMillan, "Tracelab components for generating extractive summaries of user stories," in 2017 IEEE Int. Conf. on Soft. Maint. and Evolution (ICSME), Sept 2017, pp. 658--658.
[30]
R. Holmes and G. C. Murphy, "Using structural context to recommend source code examples," in Proc. of the 27th Int. Conf. on Software Engineering (ICSE 2005). ACM, 2005, pp. 117--125.
[31]
J. Stylos and B. A. Myers, "Mica: A web-search tool for finding api components and examples," in Proc. of the Visual Languages and Human-Centric Computing (VLHCC 2006). IEEE, 2006, pp. 195--202.
[32]
G. C. Murphy, R. J. Walker, and R. Holmes, "Approximate structural context matching: An approach to recommend relevant examples," IEEE Transactions on Software Engineering, vol. 32, pp. 952--970, 12 2006.
[33]
L. Moreno, G. Bavota, M. D. Penta, R. Oliveto, and A. Marcus, "How can I use this method?" in Proc. of the 37th IEEE/ACM Int. Conf. on Software Engineering (ICSE 2015), 2015, pp. 880--890.
[34]
S. Thummalapenta and T. Xie, "Parseweb: A programmer assistant for reusing open source code on the web," in Proc. of the 22nd IEEE/ACM Int. Conf. on Automated Soft. Eng. (ASE). ACM, 2007, pp. 204--213.
[35]
S. P. Reiss, "Semantics-based code search," in Proc. of the 31st Int. Conf. on Soft. Eng. (ICSE 2009). IEEE, 2009, pp. 243--253.
[36]
C. McMillan, M. Grechanik, D. Poshyvanyk, Q. Xie, and C. Fu, "Portfolio: Finding relevant functions and their usage," in Proc. of the 33rd Int. Conf. on Soft. Eng. (ICSE 2011). ACM, 2011, pp. 111--120.
[37]
L. Ponzanelli, S. Scalabrino, G. Bavota, A. Mocci, R. Oliveto, M. D. Penta, and M. Lanza, "Supporting software developers with a holistic recommender system," in Proc. of the 39th IEEE/ACM Int. Conf. on Software Engineering (ICSE), May 2017, pp. 94--105.
[38]
L. Ponzanelli, A. Bacchelli, and M. Lanza, "Leveraging crowd knowledge for software comprehension and development," in Proc. of the 17th European Conf. on Soft. Maint. and Reeng., March 2013, pp. 57--66.
[39]
L. Ponzanelli, G. Bavota, M. Di Penta, R. Oliveto, and M. Lanza, "Mining StackOverflow to turn the IDE into a self-confident programming prompter," in Proc. of the 11th Working Conf. on Mining Software Repositories (MSR 2014). ACM, 2014, pp. 102--111.
[40]
M. P. Robillard, "What makes APIs hard to learn? Answers from developers," IEEE Software, vol. 26, no. 6, pp. 27--34, 2009.
[41]
B. Dagenais and M. P. Robillard, "Creating and evolving developer documentation," Proc. of the 18th ACM SIGSOFT Int. Symp. on Foundations of Software Engineering (FSE 2010), p. 127, 2010.
[42]
M. P. Robillard and R. Deline, "A field study of API learning obstacles," Empirical Software Engineering, vol. 16, no. 6, pp. 703--732, 2011.
[43]
R. Plösch, A. Dautovic, and M. Saft, "The Value of Software Documentation Quality," in Proc. of the 14th Int. Conf. on Quality Software, oct 2014, pp. 333--342.
[44]
G. Garousi, V. Garousi-Yusifoglu, G. Ruhe, J. Zhi, M. Moussavi, and B. Smith, "Usage and usefulness of technical software documentation: An industrial case study," Information and Software Technology, vol. 57, no. 1, pp. 664--682, 2015.
[45]
G. Uddin and M. P. Robillard, "How API Documentation Fails," IEEE Software, vol. 32, no. 4, pp. 68--75, 2015.
[46]
N. Alhindawi, O. M. Al-Hazaimeh, R. Malkawi, and J. Alsakran, "A Topic Modeling Based Solution for Confirming Software Documentation Quality," Int. Journal of Advanced Computer Science and Applications, vol. 7, no. 2, pp. 200--206, 2016.
[47]
S. M. Sohan, F. Maurer, C. Anslow, and M. P. Robillard, "A study of the effectiveness of usage examples in REST API documentation," Proc. of IEEE Symposium on Visual Languages and Human-Centric Computing, VL/HCC, vol. 2017-October, pp. 53--61, 2017.
[48]
J. D. Arthur and K. T. Stevens, "Document quality indicators: A framework for assessing documentation adequacy," Journal of Software Maintenance: Research and Practice, vol. 4, no. 3, pp. 129--142, 1992.
[49]
A. Dautovic, "Automatic assessment of software documentation quality," in 2011 26th IEEE/ACM Int. Conf. on Automated Software Engineering (ASE 2011), nov 2011, pp. 665--669.
[50]
T. C. Lethbridge, J. Singer, and A. Forward, "Use Documentation : The State of the Practice Documentation," Ieee Focus, p. 5, 2003.
[51]
M. Visconti and C. R. Cook, "Assessing the State of Software Documentation Practices," in Product Focused Software Process Improvement, 2004, pp. 485--496.
[52]
M. Linares-Vásquez, B. Dit, and D. Poshyvanyk, "An exploratory analysis of mobile development issues using Stack Overflow," in Proc. of the 10th Working Conf. on Mining Software Repositories (MSR), May 2013, pp. 93--96.
[53]
A. Barua, S. W. Thomas, and A. E. Hassan, "What are developers talking about? An analysis of topics and trends in Stack Overflow," Empirical Softw. Eng., vol. 19, no. 3, pp. 619--654, Jun. 2014.
[54]
C. Rosen and E. Shihab, "What are mobile developers asking about? A large scale study using Stack Overflow," Empirical Softw. Eng., vol. 21, no. 3, pp. 1192--1223, Jun. 2016.
[55]
H. Khalid, E. Shihab, M. Nagappan, and A. E. Hassan, "What do mobile app users complain about?" IEEE Software, vol. 32, no. 3, pp. 70--77, May 2015.
[56]
"Replication Package," https://github.com/REVEAL-ICSE19-DocIssues/ReplicationPackage.
[57]
I. Grigorik, "GitHub Archive," https://www.githubarchive.org.
[58]
GitHub, "Event Types & Payloads," https://developer.github.com/v3/activity/events/types/.
[59]
A. S. Foundation, "Apache Mail Archives," http://mail-archives.apache.org/mod_mbox/.
[60]
G. Antoniol, G. Canfora, G. Casazza, A. D. Lucia, and E. Merlo, "Recovering traceability links between code and documentation," IEEE Trans. on Soft. Eng., vol. 28, no. 10, pp. 970--983, 2002.
[61]
R. Koschke, "Survey of research on software clones," in Duplication, Redundancy, and Similarity in Software, ser. Dagstuhl Seminar Proceedings, no. 06301. Internationales Begegnungs- und Forschungszentrum für Informatik (IBFI), Schloss Dagstuhl, Germany, 2007. {Online}. Available: http://drops.dagstuhl.de/opus/volltexte/2007/962
[62]
S. Scalabrino, M. Linares-Vásquez, R. Oliveto, and D. Poshyvanyk, "A comprehensive model for code readability," Journal of Software: Evolution and Process, vol. 30, no. 6, 2018.
[63]
J. Kincaid, R. Fishburne, R. Rogers, and B. Chissom, "Derivation of new readability formulas (automated readability index, fog count and flesch reading ease formula) for navy enlisted personnel," Institute for Simulation and Training, Tech. Rep., 1975.
[64]
H. Zhong and Z. Su, "Detecting API documentation errors," SIGPLAN Not., vol. 48, no. 10, pp. 803--816, Oct. 2013.
[65]
"GitHub Issue of acid-state/acid-state." http://bit.ly/2wokNDJ
[66]
"GitHub Issue of rockstor/rockstor-core." http://bit.ly/2wr2AFo
[67]
"GitHub Issue of pluskid/mocha.jl." http://bit.ly/2wop8H1
[68]
"GitHub PR of silverstripe/silverstripe-framework." http://bit.ly/2wnCvXQ
[69]
"Apache Mailing List httpd-docs." http://bit.ly/2wqx4Y2
[70]
"Apache Mailing List httpd-docs." http://bit.ly/2wmverj
[71]
"GitHub Issue of tinymce/tinymce." http://bit.ly/2wmTIAB
[72]
"GitHub Issue of mlpack/mlpack." http://bit.ly/2wsvBAS
[73]
"GitHub Issue of elliotchance/c2go." http://bit.ly/2wmSk0T
[74]
"GitHub PR of falconry/falcon." http://bit.ly/2wixz6s
[75]
"GitHub Issue of trilinos/trilinos." http://bit.ly/2wmAM57
[76]
"GitHub Issue of bytedeco/javacpp-presets." http://bit.ly/2wnfqEF
[77]
"GitHub Issue of nodemcu/nodemcu-firmware.' http://bit.ly/2wqzMgt
[78]
"GitHub Issue of facebook/watchman. http://bit.ly/2wpzpmb
[79]
"Apache Mailing List forrest-dev." http://bit.ly/2wr91Z6
[80]
"GitHub PR of coreos/etcd." http://bit.ly/2wr24aq
[81]
"GitHub Issue of d3/d3-dispatch." http://bit.ly/2wmBQWE
[82]
"GitHub PR of alibaba/rax. http://bit.ly/2wmk4TC
[83]
"Apache Mailing List systemml-dev. http://bit.ly/2wqU6y2
[84]
"GitHub Issue of domaindrivendev/swashbuckle. http://bit.ly/2wo2oa6
[85]
"GitHub Issue of doctrine/doctrine1." http://bit.ly/2wodZWN
[86]
"GitHub Issue of webpack/docs." http://bit.ly/2wmW56t
[87]
"GitHub Issue of stevegrunwell/mcavoy. http://bit.ly/2wp3QZB
[88]
"GitHub PR of asciidoctor/asciidoctorj. http://bit.ly/2woguZb
[89]
"Apache Mailing List cocoon-docs. http://bit.ly/2BJ8g3x
[90]
"Apache Mailing List directory-dev." http://bit.ly/2wvX1G3
[91]
"GitHub Issue of revapi/revapi. http://bit.ly/2wlugeZ
[92]
"GitHub PR of habitat-sh/habitat." http://bit.ly/2wogWql
[93]
"GitHub Issue of riot-os/riot. http://bit.ly/2wssVTQ
[94]
"StackOverflow discussion 30596247." http://bit.ly/2wrbAdG
[95]
"GitHub Issue of realm/jazzy." http://bit.ly/2wr2lKu
[96]
"Apache Mailing List httpd-docs." http://bit.ly/2wjbN2C
[97]
"Apache Mailing List stdcxx-user." http://bit.ly/2wmJDDN
[98]
"Apache Mailing List hc-dev." http://bit.ly/2woTcCj
[99]
"Apache Mailing List httpd-docs." http://bit.ly/2wlrsP5
[100]
"GitHub PR of rails/rails." http://bit.ly/2wmRKQL
[101]
"GitHub PR of paulcollett/vue-masonry-css." http://bit.ly/2wr28qG
[102]
"GitHub PR of composewell/streamly." http://bit.ly/2woqG3N
[103]
"GitHub PR of facebook/react-native." http://bit.ly/2wstqgG
[104]
"GitHub Issue of commercialhaskell/stack. http://bit.ly/2wkjxBu
[105]
"StackOverflow discussion 532779." http://bit.ly/2wnXfii
[106]
"StackOverflow discussion 1136234." http://bit.ly/2wp0wO7
[107]
"StackOverflow discussion 48435375." http://bit.ly/2wnz6bw
[108]
"GitHub PR of uber/luma.gl." http://bit.ly/2wooeKD
[109]
"StackOverflow discussion 23900027." http://bit.ly/2woWIwv
[110]
"GitHub Issue of pinax/pinax-badges. http://bit.ly/2wls0o7
[111]
"GitHub PR of netflix/hollow." http://bit.ly/2wqAcU5
[112]
"Apache Mailing List camel-dev. http://bit.ly/2wvWQun
[113]
"StackOverflow discussion 45737685." http://bit.ly/2wjeH7w
[114]
"GitHub Issue of phpdocumentor/phpdocumentor2. http://bit.ly/2wlsTwR
[115]
"StackOverflow discussion 23689297." http://bit.ly/2MzKoVi
[116]
"Apache Mailing List httpd-docs. http://bit.ly/2wr9GK4
[117]
"GitHub Issue of dvajs/dva. http://bit.ly/2wotluk
[118]
"Apache Mailing List tomee-dev. http://bit.ly/2woTzwH
[119]
"Apache Mailing List httpd-docs. http://bit.ly/2wpwc67
[120]
"GitHub PR of keratin/authn." http://bit.ly/2wnBb7k
[121]
"Apache Mailing List jclouds-user. http://bit.ly/2wmxJtG
[122]
"Apache Mailing List tomee-users." http://bit.ly/2MJkxJJ
[123]
"Apache Mailing List jena-dev. http://bit.ly/2wquDoF
[124]
"StackOverflow discussion 45342178." http://bit.ly/2wluSBp
[125]
"Apache Mailing List tuscany-user. http://bit.ly/2wqudyB
[126]
"Apache Mailing List systemml-dev. http://bit.ly/2o7WupT
[127]
"GitHub PR of prestodb/tempto." http://bit.ly/2wp1ZnB

Cited By

View all
  • (2024)Documenting Ethical Considerations in Open Source AI ModelsProceedings of the 18th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement10.1145/3674805.3686679(177-188)Online publication date: 24-Oct-2024
  • (2024)Inside Bug Report Templates: An Empirical Study on Bug Report Templates in Open-Source SoftwareProceedings of the 15th Asia-Pacific Symposium on Internetware10.1145/3671016.3671401(125-134)Online publication date: 24-Jul-2024
  • (2024)Capturing and Understanding the Drift Between Design, Implementation, and DocumentationProceedings of the 32nd IEEE/ACM International Conference on Program Comprehension10.1145/3643916.3644399(382-386)Online publication date: 15-Apr-2024
  • Show More Cited By

Recommendations

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image ACM Conferences
ICSE '19: Proceedings of the 41st International Conference on Software Engineering
May 2019
1318 pages

Sponsors

Publisher

IEEE Press

Publication History

Published: 25 May 2019

Check for updates

Author Tags

  1. documentation
  2. empirical study

Qualifiers

  • Research-article

Conference

ICSE '19
Sponsor:

Acceptance Rates

Overall Acceptance Rate 276 of 1,856 submissions, 15%

Upcoming Conference

ICSE 2025

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)68
  • Downloads (Last 6 weeks)5
Reflects downloads up to 14 Dec 2024

Other Metrics

Citations

Cited By

View all
  • (2024)Documenting Ethical Considerations in Open Source AI ModelsProceedings of the 18th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement10.1145/3674805.3686679(177-188)Online publication date: 24-Oct-2024
  • (2024)Inside Bug Report Templates: An Empirical Study on Bug Report Templates in Open-Source SoftwareProceedings of the 15th Asia-Pacific Symposium on Internetware10.1145/3671016.3671401(125-134)Online publication date: 24-Jul-2024
  • (2024)Capturing and Understanding the Drift Between Design, Implementation, and DocumentationProceedings of the 32nd IEEE/ACM International Conference on Program Comprehension10.1145/3643916.3644399(382-386)Online publication date: 15-Apr-2024
  • (2024)Do LLMs Meet the Needs of Software Tutorial Writers? Opportunities and Design ImplicationsProceedings of the 2024 ACM Designing Interactive Systems Conference10.1145/3643834.3660692(1760-1773)Online publication date: 1-Jul-2024
  • (2024)Why People Contribute Software DocumentationProceedings of the 2024 IEEE/ACM 17th International Conference on Cooperative and Human Aspects of Software Engineering10.1145/3641822.3641881(91-96)Online publication date: 14-Apr-2024
  • (2024)An Exploratory Study of Programmers' Analogical Reasoning and Software History Usage During Code Re-PurposingProceedings of the 2024 IEEE/ACM 17th International Conference on Cooperative and Human Aspects of Software Engineering10.1145/3641822.3641864(109-120)Online publication date: 14-Apr-2024
  • (2024)Multi-step Automated Generation of Parameter Docstrings in Python: An Exploratory StudyProceedings of the 2024 IEEE/ACM 46th International Conference on Software Engineering: Companion Proceedings10.1145/3639478.3643110(356-357)Online publication date: 14-Apr-2024
  • (2024)Understanding Documentation Use Through Log Analysis: A Case Study of Four Cloud ServicesProceedings of the 2024 CHI Conference on Human Factors in Computing Systems10.1145/3613904.3642721(1-17)Online publication date: 11-May-2024
  • (2024)More than Model Documentation: Uncovering Teachers' Bespoke Information Needs for Informed Classroom Integration of ChatGPTProceedings of the 2024 CHI Conference on Human Factors in Computing Systems10.1145/3613904.3642592(1-19)Online publication date: 11-May-2024
  • (2024)The State of Documentation Practices of Third-Party Machine Learning Models and DatasetsIEEE Software10.1109/MS.2024.336611141:5(52-59)Online publication date: 1-Sep-2024
  • Show More Cited By

View Options

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media