Future Perspectives in End-User Development

Klann, Markus; Paternò, Fabio; Wulf, Volker

doi:10.1007/1-4020-5386-x_21

Cited by 13 publications

(10 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In their perspectives on the future of end-user development, Klann et al pointed to the need both for intelligent customizations and quality control in end-user development [14]. In addition to Klann et al's arguments, there are at least three reasons why end-user assessment of today's customized assistants has become of key importance.…”

Section: When Using a Customized Intelligent Assistant How Can An Enmentioning

confidence: 99%

Where Are My Intelligent Assistant’s Mistakes? A Systematic Testing Approach

Kulesza

Burnett

Stumpf

et al. 2011

End-User Development

View full text Add to dashboard Cite

Abstract. Intelligent assistants are handling increasingly critical tasks, but until now, end users have had no way to systematically assess where their assistants make mistakes. For some intelligent assistants, this is a serious problem: if the assistant is doing work that is important, such as assisting with qualitative research or monitoring an elderly parent's safety, the user may pay a high cost for unnoticed mistakes. This paper addresses this problem with WYSIWYT/ML, a human/computer partnership that enables end users to systematically test intelligent assistants. Our empirical evaluation shows that WYSIWYT/ML helped end users find assistants' mistakes significantly more effectively than ad hoc testing. Not only did it allow users to assess an assistant's work on an average of 117 email messages in only 10 minutes, it also scaled to a much larger data set, assessing an assistant's work on 623 out of 1,448 messages using only the users' original 10 minutes' testing effort.

show abstract

Section: When Using a Customized Intelligent Assistant How Can An Enmentioning

confidence: 99%

Where Are My Intelligent Assistant’s Mistakes? A Systematic Testing Approach

Kulesza

Burnett

Stumpf

et al. 2011

End-User Development

View full text Add to dashboard Cite

show abstract

“…The trade-offs exist between expressiveness, freedom, and being general purpose on the one hand, and usability, learnability, control, and being domain specific on the other [Klann et al 2006]. The challenge is to abstract away from JavaScript by identifying recurrent abstractions in augmentation scripts.…”

Section: Web Augmentation: Caring For Producersmentioning

confidence: 99%

A language for end-user web augmentation

2013

View full text Add to dashboard Cite

Web augmentation is to the Web what augmented reality is to the physical world: layering relevant content/layout/navigation over the existing Web to customize the user experience. This is achieved through JavaScript (JS) using browser weavers (e.g., Greasemonkey). To date, over 43 million of downloads of Greasemonkey scripts ground the vitality of this movement. However, Web augmentation is hindered by being programming intensive and prone to malware. This prevents end-users from participating as both producers and consumers of scripts: producers need to know JS, consumers need to trust JS. This article aims at promoting end-user participation in both roles. The vision is for end-users to prosume (the act of simultaneously caring for producing and consuming) scripts as easily as they currently prosume their pictures or videos. Encouraging production requires more "natural" and abstract constructs. Promoting consumption calls for augmentation scripts to be easier to understand, share, and trust upon. To this end, we explore the use of Domain-Specific Languages (DSLs) by introducing Sticklet. Sticklet is an internal DSL on JS, where JS generality is reduced for the sake of learnability and reliability. Specifically, Web augmentation is conceived as fixing in existing web sites (i.e., the wall) HTML fragments extracted from either other sites or Web services (i.e., the stickers). Sticklet targets hobby programmers as producers, and computer literates as consumers. From a producer perspective, benefits are threefold. As a restricted grammar on top of JS, Sticklet expressions are domain oriented and more declarative than their JS counterparts, hence speeding up development. As syntactically correct JS expressions, Sticklet scripts can be installed as traditional scripts and hence, programmers can continue using existing JS tools. As declarative expressions, they are easier to maintain, and amenable for optimization. From a consumer perspective, domain specificity brings understandability (due to declarativeness), reliability (due to built-in security), and "consumability" (i.e., installation/enactment/sharing of Sticklet expressions are tuned to the shortage of time and skills of the target audience). Preliminary evaluations indicate that 77% of the subjects were able to develop new Sticklet scripts in less than thirty minutes while 84% were able to consume these scripts in less than ten minutes. Sticklet is available to download as a Mozilla add-on. ACM Reference Format:Díaz, O., Arellano, C., and Azanza, M. 2013. A language for end-user web augmentation: caring for producers and consumers alike.

show abstract

“…Interaction, Cognitive Science, Requirements Engineering, Software Engineering, Computer-Supported Cooperative Work (CSCW), Artificial Intelligence, Information Systems, and the Psychology of Programming. 10 Lieberman et al 4 defines EUD as ''a set of methods, techniques, and tools that allow users of software systems, who are acting as non-professional software developers, to at some point create, modify and extend a software artifact.'' Consequently, end-user developers are not professional programmers, but users who may have little or no formal training or experience in programming.…”

Section: Introductionmentioning

confidence: 99%

End-User Development of Visualizations

Pantazos

Lauesen

2016

View full text Add to dashboard Cite

In this article the authors investigated a visualization tool (uVis) for end-user developers, in order to see how end users actually use it. The tool was an early version and the investigation helped the authors to improve it. The investigation showed that users appreciated the simple formula language, the coordinated panels, and the drag-and-drop mechanism. However, the most important thing for them was the immediate response when they changed something, for instance part of a formula. The entire visualization was updated immediately without having to switch from development view to production view. With uVis, developers construct a visualization from simple visual components such as boxes, curvePoints, and textboxes. All component properties such as Top and BackColor can be complex formulas similar to spreadsheet formulas. The operands in the formula can address relational data in a database, other visual objects, and dialog data provided by the user. A special Rows property can bind to a database query and make the component replicate itself for each row in the query. In this way, traditional as well as novel visualizations can be constructed. The most serious usability problems were data binding and not noticing errors (errors were shown in an error list, but not in the formula that had the error). There were many other usability problems. Removing them would speed up learning and make the tool more successful.

show abstract

Future Perspectives in End-User Development

Cited by 13 publications

References 17 publications

Where Are My Intelligent Assistant’s Mistakes? A Systematic Testing Approach

Where Are My Intelligent Assistant’s Mistakes? A Systematic Testing Approach

A language for end-user web augmentation

End-User Development of Visualizations

Contact Info

Product

Resources

About