TY - JOUR
T1 - The state of the art in end-user software engineering
AU - Ko, Andrew J.
AU - Abraham, Robin
AU - Beckwith, Laura
AU - Blackwell, Alan
AU - Burnett, Margaret
AU - Erwig, Martin
AU - Scaffidi, Chris
AU - Lawrance, Joseph
AU - Lieberman, Henry
AU - Myers, Brad
AU - Rosson, Mary Beth
AU - Rothermel, Gregg
AU - Shaw, Mary
AU - Wiedenbeck, Susan
PY - 2011/4
Y1 - 2011/4
N2 - Most programs today are written not by professional software developers, but by people with expertise in other domains working towards goals for which they need computational support. For example, a teacher might write a grading spreadsheet to save time grading, or an interaction designer might use an interface builder to test some user interface design ideas. Although these end-user programmers may not have the same goals as professional developers, they do face many of the same software engineering challenges, including understanding their requirements, as well as making decisions about design, reuse, integration, testing, and debugging. This article summarizes and classifies research on these activities, defining the area of End-User Software Engineering (EUSE) and related terminology. The article then discusses empirical research about end-user software engineering activities and the technologies designed to support them. The article also addresses several crosscutting issues in the design of EUSE tools, including the roles of risk, reward, and domain complexity, and self-efficacy in the design of EUSE tools and the potential of educating users about software engineering principles.
AB - Most programs today are written not by professional software developers, but by people with expertise in other domains working towards goals for which they need computational support. For example, a teacher might write a grading spreadsheet to save time grading, or an interaction designer might use an interface builder to test some user interface design ideas. Although these end-user programmers may not have the same goals as professional developers, they do face many of the same software engineering challenges, including understanding their requirements, as well as making decisions about design, reuse, integration, testing, and debugging. This article summarizes and classifies research on these activities, defining the area of End-User Software Engineering (EUSE) and related terminology. The article then discusses empirical research about end-user software engineering activities and the technologies designed to support them. The article also addresses several crosscutting issues in the design of EUSE tools, including the roles of risk, reward, and domain complexity, and self-efficacy in the design of EUSE tools and the potential of educating users about software engineering principles.
UR - http://www.scopus.com/inward/record.url?scp=79955668292&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=79955668292&partnerID=8YFLogxK
U2 - 10.1145/1922649.1922658
DO - 10.1145/1922649.1922658
M3 - Article
AN - SCOPUS:79955668292
SN - 0360-0300
VL - 43
JO - ACM Computing Surveys
JF - ACM Computing Surveys
IS - 3
M1 - 21
ER -