Reading the documentation of invoked API functions in program comprehension

IEEE International Conference on Program Comprehension

Volumn , Issue , 2009, Pages 168-177

  Dekel, Uri ^a   Herbsleb, James D ^a  

^a Carnegie Mellon University ^*  (United States)

Author keywords

[No Author keywords available]

Indexed keywords

API FUNCTIONS; CODE FRAGMENTS; INFORMATION FORAGING; PROGRAM COMPREHENSION;

APPLICATION PROGRAMMING INTERFACES (API); KNOWLEDGE ACQUISITION; LAW ENFORCEMENT;

PROGRAM DOCUMENTATION;

EID: 70350000172     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ICPC.2009.5090040     Document Type: Article

References (13)

1. E. Berglund. Designing electronic reference documentation for software component libraries. J. Syst. Softw., 68(1):65-75, 2003.
2. U. Dekel. eMoose project page. http://emoose.cs.cmu.edu
3. U. Dekel and J. D. Herbsleb. Improving API documentation usability with knowledge pushing. To appear in ICSE '09.
4. A. Dunsmore, M. Roper, and M. Wood. Further investigations into the development and evaluation of reading techniques for object-oriented code inspection. In ICSE '02, pages 47-57.
5. G. Fairbanks, D. Garlan, and W. Scherlis. Design fragments make using frameworks easier. In OOPSLA '06, pages 75-88.
6. G. Froehlich, H. J. Hoover, L. Liu, and P. Sorenson. Hooking into object-oriented application frameworks. In ICSE '97, pages 491-501.
7. M. Kersten and G. C. Murphy. Using task context to improve programmer productivity. In FSE '06, pages 1-11.
8. D. Kramer. Api documentation from source code comments: a case study of javadoc. In SIGDOC '99, pages 147-153.
9. T. D. LaToza, D. Garlan, J. D. Herbsleb, and B. A. Myers. Program comprehension as fact finding. In FSE '07, pages 361-370.
10. J. Lawrance, R. Bellamy, M. Burnett, and K. Rector. Using information scent to model the dynamic foraging behavior of programmers in maintenance tasks. In CHI '08, pages 1323-1332.
11. P. L. T. Pirolli. Information Foraging Theory: Adaptive Interaction with Information. Oxford Series in Human-Technology Interaction, 2007.
12. E. Soloway, R. Lampert, S. Letovsky, D. Littman, and J. Pinto. Designing documentation to compensate for delocalized plans. Commun. ACM, 31(11):1259-1267, 1988.
13. Sun Microsystems. Requirements for writing java api specifications. http://java.sun.com/j2se/javadoc/writingapispecs