|
'''End User Computing''' (EUC) refersis a group of approaches to severalcomputing thingsthat aim at better integrating end users into the computing environment. ForOne one,such ittrend refersattempts to integrate the [[human interface]], [[ergonomics|ergonomically]] integrated into a [[user centered design]] system throughout its [[technology lifecycle|life cycle]]. In this sense, EUC's goal is to allow unskilled staff to use expensive and highly skilled knowledge in their jobs. This is done, by putting the knowledge and expertise into the computer and teaching the end user how to access it. ForAnother another,trend it refersis to softwareallow engineeringend andusers development(SMEs, controlled___domain byexperts) to control and even performedperform bysoftware theengineering end user (SME, ___domain expert,and development...)
In the former sense of EUC, it appears easier to teach factory workers, for example, how to read dials, push buttons, pull levers, and log results than to teach them the manufacturing process and mathematical models. The current computing trend is to [[simulate]] a console with similar dials, sliders, levers, and switches, which the end user is taught to use. To further reduce end user training, computer consoles all contain components which are shaped, labled, coloured, and function similarly. EUC developers assume that once the end user knows what and how a particular lever works, they will quickly identify it when it appears in a new console. This means that once staff learns one console, they will be able to operate all consoles. Admittedly each console will have new components, but training is limited to those, not the whole console. This approach requires more than just [[Pavlovian]] responses as the console content will have meaning that is of use and power to the particular computing ___domain.
In the latter sense of EUC, it has been argued that '''a''' (teaching programming and computing concepts to a ___domain expert (say, one of the sciences or engineering disciplines) and letting the expert develop rules (this type of action can be subsumed under the topic of business rules)) is easier than '''b''' (teaching the intricacies of a complex discipline to a computer worker (<!---need to clarify this further, but, for now, read IT/IS)-->). '''b''' is the normal approach of the IT-driven situation. '''a''' has been the reality since day one of computing in many disciplines. One may argument that resolving issues of '''a''' and '''b''' is not unlike the interplay between distributed and central processing (which is an age-old concern in computing). In thissense of EUC, there may be computer scientists supporting decisions about architecture, process, and GUI. However, in many cases, the end user owns the software components. One thrust related to this sense of EUC is a focus on providing better languages to the user. [[ICAD]] was an example in the [[Knowledge-Based_Engineering|KBE]] context. Of late, this discipline has moved to a co-joint architecture that features advanced interactive ___domain visualization coupled with a complicated API accessed via [[VBA]], [[C++]], and the like. This type of co-jointness is an example of a ___domain tool augmented with non-trivial extensibility.
In the former sense of EUC, computer developers assume that once the end user knows what and how a particular lever works, they will quickly identify it when it appears in a new console. This means that once staff learns one console, they will be able to operate all consoles. Admittedly each console will have new components, but training is limited to those, not the whole console. This approach requires more than just [[Pavlovian]] responses as the console content will have meaning that is of use and power to the particular computing ___domain. One aspect of EUC research addresses issues related to [[User_interface|man-machine]] interface.
In the latter sense of EUC, there may be computer scientists supporting decisions about architecture, process, and GUI. However, in many cases, the end user owns the software components. One thrust related to this sense of EUC is a focus on providing better languages to the user. [[ICAD]] was an example in the [[Knowledge-Based_Engineering|KBE]] context. Of late, this discipline has moved to a co-joint architecture that features advanced interactive ___domain visualization coupled with a complicated API accessed via [[VBA]], [[C++]], and the like. This type of co-jointness is an example of a ___domain tool augmented with non-trivial extensibility.
In computer jargon, consoles are called [[computer program|program]]s or [[application software|applications]] and they are presented through a [[Graphical User Interface]] which ensures the components have a consistent [[look and feel]]. The computer's [[operating system|operation]] is hidden behind this [[metaphor]] and presents itself in a way most people understand.
==Trend==
Other studies range from website [[accessibility]] to [[pervasive computing]], with the focus ranging from the human to the computer. The issue centres around how much the human can safely and reliably adjust to the computer's [[I/O device]]s on the one hand, and how unobtrusively the computer can detect the human's needs on the other.
TooFurthermore, issues related to computing ontologies (example: [[Language/Action_perspective]] has found some success in [[Customer_Relationship_Management|CRM]], etc.) continue to be of interest to EUC.
==Analysis==
The concepts related to the 'end user' cover a wide range (novice user to intellectual borg {seeborg—see Slogan 2}), hence '''End User Computing''' can have a range of forms and values. Most early computer systems were tightly controlled by an IT department; 'users' were just that. However, at any point in the evolution of computer systems through time, there was serious work in several domains that required user development. The dynamics of the power struggles between centralized and decentralized computing have been a fact; this was partially due to the emergence of the mid-sized computers ([[VAX]], etc.). Then, the advent of the personal workstation opened up the door, so to speak, since it allowed a more pervasive type of computation to emerge. The recent advent of 'web' services has extended the issues to a more broad scope.
In the sense of serious ___domain computing and given the intertwining of [[computation]] into all advanced disciplines, any tool (inclusive of any type of capability related to a ___domain/discipline) that is provided by a computer becomes part of the discipline (methodology, etc.).
As such, the issue arises about how open the tool is to scrutiny. Some disciplines require more understanding of the tool set than do others. That is, tools that are [[operational]] in scope require less understanding than those that are [[ontological]]. As an example of the latter type of influence on disciplines, consider the impact that the computer has had on the [[Scientific_method#Computational_approaches|scientific method]].
Some of the issues related to End User Computing concern architecture (iconic versus language interface, open versus closed, ...and others). These continue to be studied. Other issues relate to IP, configuration, maintenance, ... End User Computing allows more user input into system affairs that can range from personalization to full-fledged ownership of the system.
Examples of End User Computing are [[ICAD]], and [[SQL]], ... [[ICAD]] (in the [[Knowledge-Based_Engineering|KBE]] ___domain) stands as a prime example since it is associated with the pervasive use of [[Lisp_programming_language|Lisp]] by [[Engineers]] to accomplish remarkable effects through a long economic cycle.
=== Slogans ===
* Good End User Computing practices might help temper things such as the [[AI Winter]].
* The computational needs to wed with the phenomenal (are 'borgs' inevitable?).
<!--:Note: '''[[Borg]]''', in this sense, may be inspired by science fiction, however the reality of [[Wearable_computing|wearables]] and embedded [[Integrated_circuit|chips]] ought to be considered. Witness, too, the recent article in an [[IEEE]] periodical about the use of embedded circuitry (such as, to regulate release of medication) in [[Psychiatry]] practice. Related discussion will cover [[cognition]], [[perception]], and much more (to be listed).-->
* There is always more than meets the eye (or, [[Graphical_user_interface|GUI]], or any interface, is only part of the [[truth]]).
<!-- The reason for this section is unclear to me
==Addiction==
When people use computers to the extent it disrupts their relationships and lifestyle, they are addicted. Common addictions include [[Internet Relay Chat]] and [[mudding]].
::(Note: this is a little strong in that '''gaming''' can be a respected form of [[training]] and [[education]]; [[Augmented_reality|augmented reality]] is getting serious money behind it; ...)
-->
== See also ==
* [[Software engineering]]
* [[Usability engineering]]
* [[userUser (computing)]]
* [[endEnd-user (computer science)]]
* [[usabilityUsability]]
* [[userUser interface]]
* [[computerComputer systems]]
* [[Scientific method#Computational approaches|Scientific method]]
* [[Knowledge-Based_Engineering]]
* [[computerComputer addiction]]
* [[Mobile phones and driving safety]]
* [[digitalDigital persona]]
* [[luserLuser]]
==External links==
| 