End-user computing: Difference between revisions

Revision as of 20:26, 26 July 2015

Revision as of 04:27, 27 July 2015

Line 1:

'''End-user computing''' (EUC) refers to systems in which non-programmers can create working [[Application software|application]]s.<ref>{{citecitation|url=http://portal.acm.org/citation.cfm?id=1120304|title=End-user computing}}</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_solvingProblem solving|problem-solving]] in a trustworthy manner.<ref>McBride, Neil, "[http://www.cse.dmu.ac.uk/~nkm/EUC1.html 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] University of Texas, USA, ISSN: 1537–9310</ref>

End-user computing can range in complexity from users simply clicking a series of buttons, to writing scripts in a controlled [[scripting language]], to being able to modify and execute code directly.

Line 8:

Factors contributing to the need for further EUC research include [[knowledge]] processing, [[pervasive computing]], issues of [[Upper 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,{{huh?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. Any Application Architecture Strategy / IT Strategy should consider the white spaces in automation (Enterprise Functionality not automated by ERP / Enterprise Grade Applications). These are the potential areas where EUC can play a major role. Then ASSIMPLER parameters should be applied to these white spaces. ASSIMPLER stands for Availability, Scalability, Security, Interoperability, Maintainability, Performance, Low Cost of Ownership, Extendability and Reliability to develop the EUC Strategy.<ref>{{cite web|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|accessdate=26 July 2015}}</ref>.

== See also ==

Line 26:

* [[Defensive computing]]

* [[Decentralized computing]]

==References==

{{Reflist}}

==External links==