ACM Home Page
Please provide us with feedback. Feedback
Jadeite: improving API documentation using usage information
Full text PdfPdf (672 KB)
Source
Conference on Human Factors in Computing Systems archive
Proceedings of the 27th international conference extended abstracts on Human factors in computing systems table of contents
Boston, MA, USA
SESSION: Spotlight on work in progress session 2 table of contents
Pages 4429-4434  
Year of Publication: 2009
ISBN:978-1-60558-247-4
Authors
Jeffrey Stylos  Carnegie Mellon University, Pittsburgh, PA, USA
Brad A. Myers  Carnegie Mellon University, Pittsburgh, PA, USA
Zizhuang Yang  Carnegie Mellon University, Pittsburgh, PA, USA
Sponsors
ACM: Association for Computing Machinery
SIGCHI: ACM Special Interest Group on Computer-Human Interaction
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): n/a,   Downloads (12 Months): n/a,   Citation Count: 1
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1520340.1520678
What is a DOI?

ABSTRACT

Jadeite is a new Javadoc-like API documentation system that takes advantage of multiple users' aggregate experience to reduce difficulties that programmers have learning new APIs. Previous studies have shown that programmers often guessed that certain classes or methods should exist, and looked for these in the API. Jadeite's "placeholders" let users add new "pretend" classes or methods that are displayed in the actual API documentation, and can be annotated with the appropriate APIs to use instead. Since studies showed that programmers had difficulty finding the right classes from long lists in documentation, Jadeite takes advantage of usage statistics to display commonly used classes more prominently. Programmers had difficulty finding the right helper objects and discovering how to instantiate objects, so Jadeite uses a large corpus of sample code to automatically identify the most common ways to construct an instance of any given class.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
Clarke, S. 2004. Measuring API Usability. Dr. Dobbs Journal, Windows / .NET Supplement. May 2004. 6--9.
 
3
 
4
5
6
 
7
8
 
9


Collaborative Colleagues:
Jeffrey Stylos: colleagues
Brad A. Myers: colleagues
Zizhuang Yang: colleagues