Content deleted Content added
Elmo Lincoln (talk | contribs) |
Reformatted. |
||
Line 1:
'''End-user development''' (EUD) is a research topic within the field of [[computer science]] and [[human-computer interaction]], describing activities or techniques that allow people who are not professional developers to create or modify a software artifact. A typical example of EUD is [[Computer programming|programming]] to extend and adapt an existing package,
There are two basic reasons why EUD has become popular Other examples of * [[3D modeling|3D models]] created with end-user oriented tools and approaches such as [[Sketchup]]
* [[Computer animation|Animation]] scripts used by graphic artists to describe characters, environments and how characters move to produce an intended animation
* [[Configuration file|Configuration files]] that blur the line between programs and data (e.g., [[E-mail filtering|email filters]] are sequenced lists of criteria and actions to take)
* Contributions to [[open source]] projects where users of a software package contribute their own code for inclusion in the main [[Software package (installation)|package]]
* [[Mod (computer gaming)|Game modifications]] to introduce users' own characters, environments, etc.
* Interaction scripts used in [[Call centre|CRM call centres]]
* Process models used in [[
* [[Software prototyping|Prototypes]] and ___domain-specific programs written by businesspeople, engineers, and scientists to demonstrate or test specific theories
* Scientific models used in [[
* Scripts and macros added to extend or automate [[Office suite|office productivity suites]] and [[Graphics software|graphics applications]].
* Simulations created using [[Software_prototyping#Application_definition_software|application definition software]]
* [[Spreadsheets|Spreadsheet]] models, e.g., used for budgeting or risk analysis
* [[Web page]]s - plain HTML or HTML and scripting
* [[Wiki]]s - a collaborative
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 [[
==Cost-
According to Sutcliffe<ref>{{cite journal
According to one analysis, EUD essentially out-sources development effort to the end user. Because there is always some effort to learn an EUD tool motivation depends on users' confidence that it will empower their work, save time on the job and/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.<ref>{{cite journal▼
| last = Sutcliffe
| first = Alistair
Line 33 ⟶ 38:
| format = pdf
| accessdate = 2008-05-29
▲
This study defines costs as the sum of:
* Technical cost: the price of the technology and the effort to install it
* Learning cost: the time taken to understand the technology
* Development cost: the effort to develop applications using the technology
* Test and debugging cost: the time taken to verify the system
The first and second costs are incurred once during acquisition, whereas the third and fourth are
* Functionality delivered by the technology
* Flexibility to respond to new requirements
* Usability of applications produced
* Overall quality of the applications produced
A major drawback with the implementation of end-user development is that it removes the end-users away from their daily task, decreases productivity and efficiency. 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:<ref>{{cite journal|url=http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=01309636 |title= The Dangers of End-User Programming |last=Harrison |first=Warren |journal=IEEE Software | volume=21 | issue=4 | date=July/August 2004 | format=pdf | doi=10.1109/MS.2004.13 | accessdate=2009-03-02 }}</ref>
▲==Other Aspects of End-user development==
▲A major drawback with the implementation of End User Development is that it removes the end-users away from their daily task, decreases productivity and efficiency. Commentators have been concerned that end users do not understand how to test and secure their applications - "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
In response to this, '''
All the above approaches assume that the user is developing software using tools already approved by a central IT function, where "the user is naive, with little understanding of data processing.... but users should no longer be considered universally ignorant of information systems. Moreover, sophisticated information center veterans, as well as microcomputer users, can and do contribute to system development. They are capable of preliminary experimentation with system requirements, in particular those related to user interface."<ref name ACM_1987>{{cite journal |url=http://portal.acm.org/citation.cfm?id=1017817 |first=Nava |last=Pliskin |coauthors=Shoval, Peretz |title=End-user prototyping: sophisticated users supporting system development |work=ACM SIGMIS Database |volume=4 |pages=7-17|year=1987|issn=0095-0033|doi=10.1145/1017816.1017817|accessdate=2008-05-29}}</ref> In this case the assumption is that the tools have a high learning curve and require exceptional expertise to be deployed in a secure, reliable and scalable manner.
An alternative scenario is that end users (and/or their consultants) employ [[Declarative programming|declarative]] tools that support rigorous business and security rules at the expense of performance and scalability. Though this is a valid [[
== See also ==
| |||