End-user computing: Difference between revisions

Revision as of 07:35, 27 October 2021

Latest revision as of 09:48, 23 April 2025

(6 intermediate revisions by 6 users not shown)

Line 1:

{{Short description|Systems in which users can make apps}}

{{howto|date=July 2021}}

'''End-user computing''' ('''EUC''') refers to systems in which non-programmers[[programmer]]s can create working [[Application software|application]]s.<ref name="EUC">{{cite conference | url=http://dl.acm.org/citation.cfm?id=1120304 | title=End-user computing | publisher=[[Association for Computing Machinery]] | access-date=30 December 2015 | author=Goodall, Howie | book-title=CHI EA '97 CHI '97 Extended Abstracts on Human Factors in Computing Systems | date = March 1997 | conference=ACM CHI 97 Human Factors in Computing Systems Conference | ___location=Los Angeles, Los Angeles County, California, United States of America | pages=132 | isbn=0-89791-926-2}}</ref> EUC is a group of approaches to computing that aim to better integrate [[user (computing)|end users]] into the computing environment. These approaches attempt to realize the potential for high-end computing to perform problem-solving in a trustworthy manner.<ref>McBride, Neil, "[https://www.dora.dmu.ac.uk/handle/2086/213 Towards User-Oriented control of End-User Computing in Large Organizations]"</ref><ref>Mahmood, Adam, [http://www.idea-group.com/bookseries/details.asp?id=3 Advances in End User Computing Series] {{Webarchive|url=https://web.archive.org/web/20070129022235/http://www.idea-group.com/bookseries/details.asp?id=3 |date=2007-01-29 }} University of Texas, USA, {{ISSN|1537-9310}}</ref>

End-user computing can range in complexity from users simply clicking a series of buttons, to citizen developers<ref>[{{Cite web|url=https://www.gartner.com/en/information-technology/glossary/citizen-developer]|title=Definition of Citizen Developer - Gartner Information Technology Glossary}}</ref> writing scripts in a controlled [[scripting language]], to being able to modify and execute code directly.

Examples of end-user computing are systems built using [[fourth-generation programming language]]s, such as [[MAPPER]] or [[SQL]], or one of the [[fifth-generation programming language]]s, such as [[ICAD (software)|ICAD]].

==Factors==

Factors contributing to the need for further EUC research include [[knowledge]] processing, [[pervasive computing]], issues of [[Upperupper ontology (computer science)|ontology]], [[interactive visualization]], and the like.

Some of the issues related to end-user computing concern [[software architecture]] ([[Graphical user interface|iconic]] versus language interfaces, open versus closed,{{clarify|date=July 2013}} and others). Other issues relate to [[intellectual property]], configuration and maintenance. End-user computing allows more user-input into system affairs that can range from [[personalization]] to full-fledged ownership of a system.

==EUC strategy==

EUC applications should not be evolved by accident, but there should be a defined EUC strategy.{{cncitation needed|date=May 2016}} Any [[Application Architecture]] Strategy / IT Strategy should consider the white spaces in automation (enterprise functionality not automated by [[Enterprise resource planning | ERP]] / [[Enterprise Grade Applications]]). These are the potential areas where EUC can play a major role.{{cncitation needed|date=May 2016}} Then ASSIMPLER parameters{{which?|date=May 2016}} should be applied{{by whom?|date=May 2016}} to these white spaces to develop the EUC strategy. (ASSIMPLER stands for availability, scalability, security, interoperability, maintainability, performance, low [[cost of ownership]], extendibility and reliability.<ref>

Compare: {{cite web

EUC applications should not be evolved by accident, but there should be a defined EUC strategy.{{cn|date=May 2016}} Any [[Application Architecture]] Strategy / IT Strategy should consider the white spaces in automation (enterprise functionality not automated by [[Enterprise resource planning | ERP]] / [[Enterprise Grade Applications]]). These are the potential areas where EUC can play a major role.{{cn|date=May 2016}} Then ASSIMPLER parameters{{which?|date=May 2016}} should be applied{{by whom?|date=May 2016}} to these white spaces to develop the EUC strategy. (ASSIMPLER stands for availability, scalability, security, interoperability, maintainability, performance, low [[cost of ownership]], extendibility and reliability.

|last1= Vanarse|first1= Mandar|title= Business Value Assurance during the transformation journey.

|url= http://www.wipro.com/documents/business-value-assurance-during-the-transformation-journey.pdf

|website= Wipro|publisher= Wipro Limited|access-date= 26 July 2015

| quote = How should the business services be designed in terms of availability, security, scalability, interoperability, maintenance, performance, lower cost, extendibility and reliability (ASSIMPLER) from end consumer perspective?

}}

</ref>)

In businesses, an end-user concept gives workers more flexibility, as well as more opportunities for better productivity and creativity. However, EUC will work only when leveraged correctly. That’s why it requires a full-fledged strategy. Any strategy should include all the tools users might need to carry out their tasks and work more productively.

Line 38 ⟶ 45:

* lack of maintenance processes;

* lack of security;

* lack of audit trail.;

* overreliance on manual controls.

==EUC risk management software==

Many companies elect to leverage software to manage their EUC risks. Software can provide many benefits to organizations, including:

* automation of risk management activities;

* reduction in manual effort required for manual controls;

* version controls for EUC applications;

* change controls for EUC applications.

Examples of EUC risk software include:

* apparity<ref>{{cite web |title=End-user computing risk management solution of the year: Apparity |url=https://www.insuranceerm.com/content/awards/insuranceerm-annual-awards-2023-uk-and-europe/winners/end-user-computing-risk-management-solution-of-the-year-apparity.html |website=InsuranceERM |access-date=2 May 2023}}</ref>

==See also==