End-user development: Difference between revisions

Revision as of 16:01, 16 November 2020

Revision as of 17:21, 23 December 2020

Line 9:

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. [[Low-code development platforms]] are also an approach to EUD.

One evolution in this area has considered the use of mobile devices to support end-user development activities. In this case previous approaches for desktop applications cannot be simply reproposed, given the specific characteristics of mobile devices. Desktop EUD environments lack the advantages of enabling end users to create applications opportunistically while on the move.<ref>[http://www.hindawi.com/journals/isrn/2013/532659/ Paternò F., 2013, ISRN Software Engineering, End User Development: Survey of an Emerging Field for Empowering People]</ref>

More recently, interest in how to exploit EUD to support development of Internet of Things applications has increased. In this area trigger-action programming seems a promising approach.<ref>[https://dl.acm.org/ft_gateway.cfm?id=3057861&ftid=1868975&dwn=1&CFID=15395619&CFTOKEN=88b71644acac92dd-68065E67-C078-832A-D6A5CF54EBDFA5C9/ Ghiani, G., Manca, M., Paternò, F., Santoro, C.: Personalization of Context-dependent Applications through Trigger-Action Rules. ACM Transactions on Computer-Human Interaction, Vol.24, Issue 2, Article N.14, April 2017.]</ref>

Lessons learned from EUD solutions can significantly influence the [[Software release life cycle|software life cycles]] for [[Software product management|commercial software products]], in-house [[intranet]]/[[extranet]] developments and [[Enterprise resource planning|enterprise application]] deployments.

==Application specific low code development platforms==

Roughly 40 vendors now offer solutions targeted at end users designed to reduce programming efforts. These solutions do not require traditional programming and may be based around relatively narrow functionality, e.g. contract management, customer relationships management, issue and bug tracking. Often referred to as low code development platforms, web based interactions guide a user to develop an application in as little as 40-8040–80 hours.<ref>[[Low-code development platforms]]</ref>{{Circular reference|date=December 2017}}

==Definition==

Line 31:

==Examples==

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

* [[Computer animation|Animation]] scripts used by graphic artists to describe characters, environments and how characters move to produce an intended animation

Line 55 ⟶ 54:

==Cost-benefit modeling==

According to [[Alistair Sutcliffe|Sutcliffe]],<ref>{{cite journal

| last = [[Alistair Sutcliffe|Sutcliffe, Alistair]]

| author-link = Alistair Sutcliffe

|date=July 2005

| title = Evaluating the costs and benefits of end-user development