Useful, but usable? Factors affecting the usability of APIs

Proceedings - Working Conference on Reverse Engineering, WCRE

Volumn , Issue , 2011, Pages 151-155

  Zibran, Minhaz F ^a   Eishita, Farjana Z ^a   Roy, Chanchal K ^a  

^a UNIVERSITY OF SASKATCHEWAN   (Canada)

Author keywords

API; Application Programming Interface; Usability

Indexed keywords

API; APPLICATION PROGRAMMING; CODE QUALITY; DEVELOPMENT COSTS; QUALITATIVE AND QUANTITATIVE ANALYSIS; REUSABLE COMPONENTS; USABILITY; USABILITY FACTORS;

COMPUTER SOFTWARE REUSABILITY; REVERSE ENGINEERING; SOFTWARE DESIGN; USABILITY ENGINEERING;

APPLICATION PROGRAMMING INTERFACES (API);

EID: 83455213327     PISSN: 10951350     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/WCRE.2011.26     Document Type: Conference Paper

References (21)

1. J. Beaton, S. Jeong, Y. Xie, J. Stylos, and B. Myers. Usability challenges for enterprise service-oriented architecture APIs. In VL/HCC, pages 193-196, 2008.
2. J. Bloch. How to design a good API and why it matters. In OOPSLA, pages 506-507, 2006.
3. C. Bore and S. Bore. Profiling software API usability for consumer electronics. In ICCE, pages 155-156, 2005.
4. S. Clarke and C. Becker. Using the cognitive dimensions framework to evaluate the usability of a class library. In Joint Conf. EASE & PPIG, pages 359-366, 2003.
5. J. Daughtry, U. Farooq, J. Stylos, and B. Myers. API usability: CHI'2009 special interest group meeting. In CHI, pages 2771-2774, 2009.
6. B. Ellis, J. Stylos, and B. Myers. The factory pattern in API design: A usability evaluation. In ICSE, pages 302-312, 2007.
7. M. Henning. API design matters. ACM Queue, 5(4):24-36, 2007. (Pubitemid 46928863)
8. D. Hou and L. Li. Obstacles in using frameworks and APIs: An exploratory study of programmers newsgroup discussions. In ICPC, pages 91-100, 2011.
9. S. McLellan, A. Roesler, J. Tempest, and C. Spinuzzi. Building more usable APIs. IEEE Software, 15(3):78-86, 1998. (Pubitemid 128646996)
10. B. Myers, A. Ko, S. Park, J. Stylos, T. LaToza, and J. Beaton. More natural end-user software engineering. In WEUSE, pages 30-34, 2008.
11. J. Niño. Introducing API design principles in cs2. J. Comput. Small Coll., 24(4):109-116, 2009.
12. J. Nielsen and R. Molich. Heuristic evaluation of user interfaces. In CHI, pages 249-256, 1990.
13. D. Ratiu and J. Jürjens. Evaluating the reference and representation of domain concepts in APIs. In ICPC, pages 242-247, 2008.
14. M. Robillard and R. DeLine. A field study of API learning obstacles. Empirical Softw. Engg., pages 1-30, 2010.
15. J. Stylos and S. Clarke. Usability implications of requiring parameters in objects' constructors. In ICSE, pages 529-539, 2007.
16. J. Stylos, S. Clarke, and B. Myers. Comparing API design choices with usability studies: A case study and future directions. In AWPPIG, pages 131-139, 2006.
17. J. Stylos, B. Graf, D. Busse, C. Ziegler, R. Ehret, and J. Karstens. A case study of API redesign for improved usability. In VL/HCC, pages 189-192, 2008.
18. J. Stylos and B. Myers. Mapping the space of API design decisions. In VL/HCC, pages 50-60, 2007.
19. J. Stylos and B. Myers. The implications of method placement on API learnability. In FSE, pages 105-112, 2008.
20. G. Wurster and O. Oorschot. Developer is the enemy. In NSPW, 2008.
21. M. Zibran. What makes APIs difficult to use? J. Comp. Sci. Netw. Sec., 8(4):255-261, 2008.