2008
DOI: 10.1109/vlhcc.2008.4639083
|View full text |Cite
|
Sign up to set email alerts
|

A case study of API redesign for improved usability

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
25
0
4

Year Published

2009
2009
2017
2017

Publication Types

Select...
4
3
1

Relationship

2
6

Authors

Journals

citations
Cited by 35 publications
(29 citation statements)
references
References 4 publications
0
25
0
4
Order By: Relevance
“…For instance, one article details a number of functionality and usability problems with the .NET socket Select() function in C# [11], and uses this to motivate more focus on the usability of APIs in general. In another study, API users reported difficulty with SAP's BRFplus API -a business rules engine, and a redesign of the API dramatically improved users' success and timeto-completion [21]. A study of the early version of SAP's APIs for enterprise service-oriented architecture (eSOA) identified problems with documentation, and there were additional issues with the API itself, including names that were too long (see Figure 2), unclear dependencies, 1 We are making a list of usability issues with APIs -please send your stories to the first author.…”
Section: Examples Of Problemsmentioning
confidence: 99%
See 1 more Smart Citation
“…For instance, one article details a number of functionality and usability problems with the .NET socket Select() function in C# [11], and uses this to motivate more focus on the usability of APIs in general. In another study, API users reported difficulty with SAP's BRFplus API -a business rules engine, and a redesign of the API dramatically improved users' success and timeto-completion [21]. A study of the early version of SAP's APIs for enterprise service-oriented architecture (eSOA) identified problems with documentation, and there were additional issues with the API itself, including names that were too long (see Figure 2), unclear dependencies, 1 We are making a list of usability issues with APIs -please send your stories to the first author.…”
Section: Examples Of Problemsmentioning
confidence: 99%
“…This makes it clear what they are looking for or trying to achieve, and in general why they are making certain choices. A researcher might be interested in a more formal A-vs.-B test, comparing, for example, an old vs. new version of an API (as was done in [6,21,25]), but usually the insights about usability barriers that come out of an informal think-aloud evaluation are sufficient.…”
Section: Evaluating the Api Designmentioning
confidence: 99%
“…Students in these classes are far beyond learning to use programming primitives such as loops and conditions; instead, they must figure out how to combine APIs to create new software. This is a challenge; researchers have identified many ways in which misunderstandings about APIs can interfere with programming [2], [12] and reduce productivity by as much as a factor of six [13]- [15].…”
Section: Pedagogical Challenges Of Helping People Learn To Use Apismentioning
confidence: 99%
“…Members of our group have helped with the redesign of a business process rules engine called SAP BRFplus [11], and proposed improvements to SAP's eSOA (enterprise Service Oriented Architectures) web services [6,10].…”
Section: Introductionmentioning
confidence: 99%