End-user development

End-user development (EUD) or end-user programming (EUP) refers to activities and tools that allow end-users – people who are not professional software developers – to program computers. People who are not professional developers can use EUD tools to create or modify software artifacts (descriptions of automated behavior) and complex data objects without significant knowledge of a programming language. According to statistics from the U.S. Bureau of Labor and Statistics, by 2012, there will be more than 55 million end-user developers in the United States, compared with fewer than 3 million professional programmers.[1] Various EUD approaches exist, and it is an active research topic within the field of computer science and human-computer interaction. Examples include spreadsheets, scripting languages (particularly in an office suite or art application), visual programming, trigger-action programming and programming by example.

The most popular EUD tool is the spreadsheet.[2][3] Due to their unrestricted nature, spreadsheets allow relatively un-sophisticated computer users to write programs that represent complex data models, while shielding them from the need to learn lower-level programming languages.[4] Because of their common use in business, spreadsheet skills are among the most beneficial skills for a graduate employee to have, and are therefore the most commonly sought after[5] In the United States of America alone, there are an estimated 13 million end-user developers programming with spreadsheets[6]

Early attempts in End-user development were centered on adding simple scripting programming languages to extend and adapt an existing application, such as an office suite.

More recent research tries to bring programming closer to the needs of end users. The Programming by example (PbE) approach reduces the need for the user to learn the abstractions of a classic programming language. The user instead introduces some examples of the desired results or operations that should be performed on the data, and the PbE system infers some abstractions corresponding to a program that produces this output, which the user can refine. New data may then be introduced to the automatically created program, and the user can correct any mistakes made by the program in order to improve its definition.

Lessons learned from EUD solutions can significantly influence the software life cycles for commercial software products, in-house intranet/extranet developments and enterprise application deployments.

Definition

Lieberman et al. propose the following definition:[7]

End-User Development can be defined as a set of methods, techniques, and tools that allow users of software systems, who are acting as non-professional software developers, at some point to create, modify or extend a software artifact.

Ko et al. propose the following definition:[8]

End-user programming is programming to achieve the result of a program primarily for personal, rather public use.

Artifacts defined by end users may be objects describing some automated behavior or control sequence, such as database requests or grammar rules,[9] which can be described with programming paradigms such as programming by demonstration, programming with examples, visual programming, or macro generation.[10] They can also be parameters that choose between alternative predefined behaviors of an application.[11] Other artifacts of end-user development may also refer to the creation of user-generated content such as annotations, which may be or not computationally interpretable (i.e. can be processed by associated automated functions).[12]

Examples

Examples of end-user development include the creation and modification of:

Cost-benefit modeling

According to Sutcliffe,[17] EUD essentially outsources development effort to the end user. Because there is always some effort to learn an EUD tool, the users' motivation depends on their confidence that it will empower their work, save time on the job or raise productivity. In this model, the benefits to users are initially based on marketing, demonstrations and word-of-mouth. Once the technology is put into use, experience of actual benefits becomes the key motivator.

This study defines costs as the sum of:

The first and second costs are incurred once during acquisition, whereas the third and fourth are incurred every time an application is developed. Benefits (which may be perceived or actual) are seen as:

Collaborations in end-user development

Many end-user development activities are collaborative in nature, including collaboration between professional developers and end-user developers and collaboration among end-user developers.

Mutual development[18] is a technique where professional developers and end-user developers work together in creating software solutions. In mutual development, the professional developers often “under design” the system and provide the tools to allow the “owners of problems[19]" to create the suitable solution at use time for their needs, objectives and situational contexts.[20] Then the communication between professional developers and end-user developers can often stimulate formalizing ad hoc modifications by the end users into software artifacts, transforming end-user developed solutions into commercial product features with impacts beyond local solutions.

In this collaboration, various approaches such as the Software Shaping Workshop[21] are proposed to bridge the communication gap between professional developers and end-user developers. These approaches often provide translucency according to the social translucence model,[22] enabling everyone in the collaboration to be aware of changes made by others and to be held accountable of their actions because of the awareness.

Besides programming collaboration platforms like GitHub, which are mostly utilized by expert developers due to their steep learning curve, collaborations among end-user developers often take place on wiki platforms where the software artifacts created are shared. End-user development is also often used for creating automation scripts or interactive tutorials for sharing “how-to” knowledge. Examples of such application include CoScripter[23] and HILC.[24] In such applications, user can create scripts for tasks using pseudo-natural language or via programming by demonstration. The users can choose to upload the script to a wiki style repository of scripts. On this wiki, users can browse available scripts and extend existing scripts to support additional parameters, to handle additional conditions or to operate on additional objects.

Online and offline communities of end-user developers have also been formed, where end-user developers can collaboratively solve EUD problems of shared interest or for mutual benefit. In such communities, local experts spread expertise and advice. Community members also provide social support for each other to support the collaborative construction of software.[25]

Criticism

Commentators have been concerned that end users do not understand how to test and secure their applications. Warren Harrison, a professor of computer science at Portland State University, wrote:[26]

It’s simply unfathomable that we could expect security... from the vast majority of software applications out there when they’re written with little, if any, knowledge of generally accepted good practices such as specifying before coding, systematic testing, and so on.... How many X for Complete Idiots (where "X" is your favorite programming language) books are out there? I was initially amused by this trend, but recently I’ve become uneasy thinking about where these dabblers are applying their newfound knowledge.

This viewpoint assumes that all end users are equally naive when it comes to understanding software, although Pliskin and Shoval argue this is not the case, that sophisticated end users are capable of end-user development.[27] However, compared with expert programmers, end-user programmers rarely have the time or interest in systematic and disciplined software engineering activities,[28] which makes ensuring the quality of the software artifact produced by end-user development particularly challenging.  

In response to this, the study of end-user software engineering has emerged. It is concerned with issues beyond end-user development, whereby end users become motivated to consider issues such as reusability, security and verifiability when developing their solutions.[29]

An alternative scenario is that end users or their consultants employ declarative tools that support rigorous business and security rules at the expense of performance and scalability; tools created using EUD will typically have worse efficiency than those created with professional programming environments. Though separating functionality from efficiency is a valid separation of concerns, it can lead to a situation where end users will complete and document the requirements analysis and prototyping of the tool, without the involvement of business analysts. Thus, users will define the functions required before these experts have a chance to consider the limitations of a specific application or software framework. Senior management support for such end-user initiatives depends on their attitude to existing or potential vendor lock-in.

See also

References

  1. ↑ Scaffidi, C.; Shaw, M.; Myers, B. (2005-09-01). "Estimating the numbers of end users and end user programmers". 2005 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC'05): 207–214. doi:10.1109/VLHCC.2005.34.
  2. ↑ Margaret M. Burnett and Christopher Scaffidi. "End-User Development". Interaction-Design.org. at "Encyclopedia of Human-Computer Interaction".
  3. ↑ Hornsby, Peter (2009-08-03). "Empowering Users to Create Their Own Software". UXmatters. Retrieved 2014-01-31.
  4. ↑ Abraham, R.; Burnett, M; Erwig, M (2009). "Spreadsheet programming". Wiley Encyclopedia of Computer Science and Engineering. pp. 1–10.
  5. ↑ Kruck, S. & Sheetz, S., 2001. Spreadsheet accuracy theory. Journal of Information Systems Education.
  6. ↑ Scaffidi, C., Shaw, M. & Myers, B., 2005. Estimating the Numbers of End Users and End User Programmers. 2005 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC’05), pp.207–214.
  7. ↑ Lieberman, H., Paternò, F., Klann, M., and Wulf, V. (2006). End-User Development: An Emerging Paradigm. In: End-User Development, Lieberman, H., Paternò, F., and Wulf, V. (eds.), Springer Netherlands, 2006, ser. Human-Computer Interaction Series, vol. 9, Chapter 1, pp. 1-7, doi:10.1007/1-4020-5386-X_1
  8. ↑ Ko, Andrew J.; Abraham, Robin; Beckwith, Laura; Blackwell, Alan; Burnett, Margaret; Erwig, Martin; Scaffidi, Chris; Lawrance, Joseph; Lieberman, Henry (2011-04-01). "The State of the Art in End-user Software Engineering". ACM Comput. Surv. 43 (3): 21:1–21:44. ISSN 0360-0300. doi:10.1145/1922649.1922658.
  9. ↑ H. Lieberman, B. A. Nardi, and D. Wright. Grammex: Defining grammars by example. In ACM conference on Human Factors in Computing Systems (Summary, Demonstrations) (CHI ’98), Los Angeles, California, USA, pages 11–12. ACM Press, Apr. 1998.
  10. ↑ Maria Francesca Costabile, Daniela Fogli, Piero Mussio, Antonio Piccinno. End-user development: the software shaping workshop approach. In Lieberman, H., Paternò, F., Wulf, V. (Eds) (2004) End User Development - Empowering People to Flexibly Employ Advanced Information and Communication Technology, © 2004 Kluwer Academic Publishers, Dordrecht, The Netherlands.
  11. ↑ Costabile, M.F., Fogli, D., Letondal, C., Mussio, P., Piccinno, A., Domain -Expert Users and their Needs of Software Development", UAHCI Conference, Crete, June 22–27, 2003, 232-236.
  12. ↑ Gerhard Fischer End-User Development and Meta-Design: Foundations for Cultures of Participation. End-User Development Lecture Notes in Computer Science, 2009, Volume 5435/2009, 3-14,
  13. ↑ Scaffidi, Christopher; Brandt, Joel; Burnett, Margaret; Dove, Andrew; Myers, Brad (2012). "SIG: end-user programming". CHI '12 Extended Abstracts on Human Factors in Computing Systems: 1193–1996. doi:10.1145/2212776.2212421.
  14. ↑ Sarkar, Advait; Blackwell, Alan; Jamnik, Mateja; Spott, Martin. "Teach and Try: A simple interaction technique for exploratory data modelling by end users". 2014 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC 2014): 53–56. doi:10.1109/VLHCC.2014.6883022.
  15. ↑ Haynes, John L. (Fall 1985). "Circuit Design with Lotus 1-2-3". BYTE. pp. 143–156. Retrieved 19 March 2016.
  16. ↑ Roy Chowdhury, Soudip; Rodriguez, Carlos; Daniel, Florian; Casati, Fabio (2010). "Wisdom-aware computing: on the interactive recommendation of composition knowledge".
  17. ↑ Sutcliffe, Alistair (July 2005). "Evaluating the costs and benefits of end-user development" (PDF). ACM SIGSOFT Software Engineering Notes. ACM. 30 (4): 1–4. doi:10.1145/1082983.1083241. Retrieved 2008-05-29.
  18. ↑ Andersen, Renate; Mørch, Anders I. (2009-03-02). "Mutual Development: A Case Study in Customer-Initiated Software Product Development". End-User Development. Springer, Berlin, Heidelberg: 31–49. doi:10.1007/978-3-642-00427-8_3.
  19. ↑ Fischer, Gerhard (1994-01-01). User-Centred Requirements for Software Engineering Environments. Springer, Berlin, Heidelberg. pp. 297–306. doi:10.1007/978-3-662-03035-6_23.
  20. ↑ Fischer, Gerhard; Giaccardi, Elisa (2006-01-01). Lieberman, Henry; Paternò, Fabio; Wulf, Volker, eds. End User Development. Human-Computer Interaction Series. Springer Netherlands. pp. 427–457. ISBN 9781402042201. doi:10.1007/1-4020-5386-x_19.
  21. ↑ Lieberman, Henry; Paternò, Fabio; Klann, Markus; Wulf, Volker (2006-01-01). Lieberman, Henry; Paternò, Fabio; Wulf, Volker, eds. End User Development. Human-Computer Interaction Series. Springer Netherlands. pp. 1–8. ISBN 9781402042201. doi:10.1007/1-4020-5386-x_1.
  22. ↑ Erickson, Thomas; Kellogg, Wendy A. (2000-03-01). "Social Translucence: An Approach to Designing Systems That Support Social Processes". ACM Trans. Comput.-Hum. Interact. 7 (1): 59–83. ISSN 1073-0516. doi:10.1145/344949.345004.
  23. ↑ Leshed, Gilly; Haber, Eben M.; Matthews, Tara; Lau, Tessa (2008-01-01). "CoScripter: Automating & Sharing How-to Knowledge in the Enterprise". Proceedings of the SIGCHI Conference on Human Factors in Computing Systems. CHI '08. New York, NY, USA: ACM: 1719–1728. ISBN 9781605580111. doi:10.1145/1357054.1357323.
  24. ↑ Intharah, Thanapong; Turmukhambetov, Daniyar; Brostow, Gabriel J. (2017-01-01). "Help, It Looks Confusing: GUI Task Automation Through Demonstration and Follow-up Questions". Proceedings of the 22Nd International Conference on Intelligent User Interfaces. IUI '17. New York, NY, USA: ACM: 233–243. ISBN 9781450343480. doi:10.1145/3025171.3025176.
  25. ↑ Fischer, G.; Giaccardi, E.; Ye, Y.; Sutcliffe, A. G.; Mehandjiev, N. (2004-09-01). "Meta-design: A Manifesto for End-user Development". Commun. ACM. 47 (9): 33–37. ISSN 0001-0782. doi:10.1145/1015864.1015884.
  26. ↑ Harrison, Warren (July–August 2004). "The Dangers of End-User Programming" (PDF). IEEE Software. 21 (4): 5. doi:10.1109/MS.2004.13. Retrieved 2009-03-02.
  27. ↑ Pliskin, Nava; Shoval, Peretz (1987). "End-user prototyping: sophisticated users supporting system development". ACM SIGMIS Database. 4 (4): 7–17. doi:10.1145/1017816.1017817. Retrieved 2008-05-29.
  28. ↑ Brandt, Joel; Guo, Philip J.; Lewenstein, Joel; Klemmer, Scott R. (2008-01-01). "Opportunistic Programming: How Rapid Ideation and Prototyping Occur in Practice". Proceedings of the 4th International Workshop on End-user Software Engineering. WEUSE '08. New York, NY, USA: ACM: 1–5. ISBN 9781605580340. doi:10.1145/1370847.1370848.
  29. ↑ "End-User Software Engineering: Empirical Findings". End Users Shaping Effective Software Consortium. Retrieved 2008-05-28.

Further reading

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.