Cited by 26Software Engineering ResearchSoftware Engineering Techniques and PracticesUsability and User Interface Design

Understanding How Programmers Can Use Annotations on Documentation

Open access
Horvath, Amber, Liu, Michael Xieyang, Hendriksen, River, Shannon, Connor, Paterson, Emma, Jawad, Kazi, Macvean, Andrew, Myers, Brad A·2022·CHI Conference on Human Factors in Computing Systems

Abstract

Modern software development requires developers to find and effectively utilize new APIs and their documentation, but documentation has many well-known issues. Despite this, developers eventually overcome these issues but have no way of sharing what they learned. We investigate sharing this documentation-specific information through annotations, which have advantages over developer forums as the information is contextualized, not disruptive, and is short, thus easy to author. Developers can also author annotations to support their own comprehension. In order to support the documentation usage behaviors we found, we built the Adamite annotation tool, which provides features such as multiple anchors, annotation types, and pinning. In our user study, we found that developers are able to create annotations that are useful to themselves and are able to utilize annotations created by other developers when learning a new API, with readers of the annotations completing 67% more of the task, on average, than the baseline.

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1145/3491102.3502095

Cites

42 of 45 references verified0 citation errors · 3 not checkable

Statistics

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • The VEGA and VEGA-LITE editor [59] includes specialized affordances for those libraries, such as debugging [20] and performance [64] tools.

    “For instance, the VEGA and VEGA-LITE editor [59] includes specialized affordances for those libraries, such as debugging [20] and performance [64] tools.”

    From Considering Visualization Example Galleries (2024) · cites this paper as [20]

    The Future Work section discusses a proposed IDE extension for Adamite and mentions debugging only in connection with developers’ notes. Searches for VEGA, VEGA-LITE, and debugging tools found no passage about specialized tools in the VEGA or VEGA-LITE editor; our copy therefore does not address the attributed claim. (LLM, conf=0.76)

    Experimental — accuracy not yet measured

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Cites

Flagged first, then by citations

Research works printed but not linked: 6

  1. C.R. Cook, J.C. Scholtz, and J.C. Spohrer. 1993. Empirical Studies of Programmers: Fifth Workshop : Papers Presented at the Fifth Workshop on Empirical Studies of Programmers, December 3-5, 1993, Palo Alto, CA. Ablex Publishing Corporation, Norwood, NJ, USA. https://books.google.com/books?id=rMmxq8q0CGYC
  2. Adam Fourney and Meredith Ringel Morris. 2013. Enhancing Technical Q&A Forums with CiteHistory. In ICWSM 2013. AAAI, Palo Alto, CA, USA, 1-10.
  3. Thomas D. LaToza, David Garlan, James D. Herbsleb, and Brad A. Myers. 2007. Program comprehension as fact fnding. In ESEC-FSE 2007. ACM, New York, NY, USA, 361-270.
  4. Seyed Mehdi Nasehi, Jonathan Sillito, Frank Maurer, and Chris Burns. 2012. What makes a good code example?: A study of programming Q&A in StackOverfow. In ICSM 2012. IEEE, New York, NY, USA, 25-34.
  5. Tobias Roehm, Rebecca Tiarks, Rainer Koschke, and Walid Maalej. 2012. How do API documentation and static typing afect API usability?. In ICSE 2012. ACM, New York, NY, USA, 632-542. https://doi.org/10.1109/ICSE.2012.6227188 · DOI
  6. Tianyi Zhang, Ganesha Upadhyaya, Anastasia Reinhardt, Hridesh Rajan, and Miryung Kim. 2018. Are Code Examples on an Online Q&A Forum Reliable? A Study of API Misuse on Stack Overfow. In ICSE 2018. ACM, New York, NY, USA, 886-896.

Cited by

Sorted by citations

  • Considering Visualization Example Galleries

    Yang, J., McNutt, A. M., & Battle, L. (2024) · 2024 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC) · doi:10.1109/vl/hcc60511.2024.00043 · Cited by 5 · see citing works

    “Studies have explored how documentation might be enhanced by supporting sustainable maintenance [22], annotation [21], automated creation [10], [17], [29], enhancements to the development environment [35], [47], among others.”
    Background

Authors
Horvath, A., Liu, M. X., Hendriksen, R., Shannon, C., Paterson, E., Jawad, K., Macvean, A., & Myers, B. A.
Affiliations
  • Carnegie Mellon University (US)
  • University of Pittsburgh (US)
  • Tufts University (US)
  • Google (United States) (US)
Venue
CHI Conference on Human Factors in Computing Systems
Publisher
ACM
Published
2022-04-27
Pages
1-16
OpenAlex
W3212201636
Cited by
26
References
45
Citations by year
2026: 2 · 2025: 6 · 2024: 8 · 2023: 5 · 2022: 5
FWCI
5.37
Type
conference paper
Language
en
Open access
Locations
  • CHI Conference on Human Factors in Computing Systems (publishedVersion, cc-by)
  • arXiv (Cornell University) (submittedVersion)
  • arXiv (Cornell University) (cc-by)
Funders
NSF (CCF-2007482)
Topics
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Human-Computer Interaction › Usability and User Interface Design
Keywords
API documentation, annotation, developer learning, knowledge sharing, developer forums, multiple anchors, annotation types

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review