ACM Home Page
Please provide us with feedback. Feedback
Informing Eclipse API production and consumption
Full text PdfPdf (481 KB)
Source OOPSLA workshop on eclipse technology eXchange archive
Proceedings of the 2007 OOPSLA workshop on eclipse technology eXchange table of contents
Montreal, Quebec, Canada
Pages 70-74  
Year of Publication: 2007
ISBN:978-1-60558-015-9
Authors
Reid Holmes  University of Calgary, Calgary, Alberta, Canada
Robert J. Walker  University of Calgary, Calgary, Alberta, Canada
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 3,   Downloads (12 Months): 46,   Citation Count: 3
Additional Information:

abstract   references   cited by   collaborative colleagues  

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

ABSTRACT

Application programming interfaces (APIs) inform application developers as to the functionality provided by a library and how to interact with it. APIs are a double-edged sword: if they do not permit the needed functionality to be accessed and adapted as needed, they are obstructing; if they permit all things to all people, they are complex, leading application developers to have difficulty understanding how to use them correctly. Thus, the developers of APIs have a delicate balance to strike between providing configurable functionality and simple interfaces. Inevitably, the wrong balance is sometimes chosen, as the actual usage is different from the expected usage; APIs need to evolve, or to be re-documented to account for this disparity. In this paper we propose a simple technique for quantitatively determining how existing APIs are used, and demonstrate its application to Eclipse. This technique would enable application developers to more easily understand how others have used the APIs and would allow API developers to more easily understand how their APIs are being used.


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
3
 
4
J. des Rivières. Evolving Java-based APIs. http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs, 14 February 2007. Revision 1.1.
5
6
7
 
8
 
9
 
10
11
 
12
R. E. Johnson and B. Foote. Designing reusable classes. Journal of Object-Oriented Programming, 1(5):22--35, 1988.
 
13
A. Mendelzon and J. Sametinger. Reverse engineering by visualizing and querying. Software: Concepts and Tools, 16:170--182, 1995.
 
14
 
15
 
16
 
17
18
 
19
 
20
 
21
22

Collaborative Colleagues:
Reid Holmes: colleagues
Robert J. Walker: colleagues