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 programming to extend and adapt an existing package, such as an office suite.
There are two basic reasons why EUD has become popular[citation needed]. One is because organizations are facing delays on projects and using EUD can effectively cut the time of completion on a project. The second reason is that software tools are more powerful and easier to use.
Other examples of end-user development include the creation and modification of:
- 3D models created with end-user oriented tools and approaches such as Sketchup
- Animation scripts used by graphic artists to describe characters, environments and how characters move to produce an intended animation
- Configuration files that blur the line between programs and data (e.g., 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 package — in some cases, end-users participate as full-fledged developers
- Game modifications to introduce users' own characters, environments, etc. — many recent games are distributed with modification in mind
- Interaction scripts used in CRM call centres
- Process models used in workflow applications
- Prototypes and ___domain-specific programs written by businesspeople, engineers, and scientists to demonstrate or test specific theories
- Scientific models used in computer simulation
- Scripts and macros added to extend or automate office productivity suites and graphics applications.
- Simulations created using application definition software
- Spreadsheet models, e.g., used for budgeting or risk analysis
- Web pages - plain HTML or HTML and scripting
- Wikis - a collaborative end-user development process
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.
Cost-benefit modeling of end-user development
According to Sutcliffe[1], 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 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.
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 incurred every time an application is developed. Benefits (which may be perceived or actual) are seen as:
- Functionality delivered by the technology
- Flexibility to respond to new requirements
- Usability of applications produced
- Overall quality of the applications produced
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. Warren Harrison, a professor of computer science at Portland State University, wrote:[2]
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.
In response to this, end-user software engineering has been defined as a higher level of EUD, whereby end-users become motivated to consider security and verifiability when developing their solutions.[3]
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."[4] 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 tools that support rigorous business and security rules at the expense of performance and scalability. Though this is a valid separation of concerns, it can lead to a situation where requirements analysis and prototyping are substantially completed and documented by end-users before business analysts have considered 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
- End-user computing
- Software engineering
- AgentSheets - an end-user development tool to create interactive simulations and educational games
External links
References
- ^ Sutcliffe, Alistair (2005). "Evaluating the costs and benefits of end-user development" (pdf). ACM SIGSOFT Software Engineering Notes. 30 (4). ACM: 1–4. doi:10.1145/1082983.1083241. ISSN 0163-5948. Retrieved 2008-05-29.
{{cite journal}}: Unknown parameter|month=ignored (help) - ^ Harrison, Warren (July/August 2004). "The Dangers of End-User Programming" (pdf). IEEE Software. 21 (4). doi:10.1109/MS.2004.13. Retrieved 2009-03-02.
{{cite journal}}: Check date values in:|date=(help) - ^ "End-User Software Engineering: Empirical Findings". Retrieved 2008-05-28.
- ^ Pliskin, Nava (1987). "End-user prototyping: sophisticated users supporting system development". ACM SIGMIS Database. 4: 7–17. doi:10.1145/1017816.1017817. ISSN 0095-0033. Retrieved 2008-05-29.
{{cite journal}}: Unknown parameter|coauthors=ignored (|author=suggested) (help) Cite error: The<ref>tag has too many names (see the help page).
 | This computer science article is a stub. You can help Wikipedia by expanding it. |