End-user computing: Difference between revisions

Revision as of 06:35, 9 September 2006

Revision as of 09:10, 21 September 2006

Line 1:

'''End User Computing''' (EUC) is a group of approaches to computing that aim at better integrating [[End-user_%28computer_science%29user (computer science)|end users]] into the computing environment or that attempt to realize the potential for high-end computing to perform in a trustworthy manner in problem solving of the highest order. The '''EUC Ranges''' section describes two types of approaches that are at different ends of a spectrum.

A simple example of these two extremes can use the [[SQL]] context. The first approach would have canned queries and reports that for the most part would be invoked with buttons and/or simple commands. In this approach, a computing group would keep these canned routines up to date through the normal development/maintenance methods. For the latter approach, [[SQL]] administration would allow for end-user involvement at several levels including administration itself. Users would also define queries though the supporting mechanism may be constrained in order to reduce the likelihood of run-away conditions that would have negative influence on other users. We see this already in some [[business intelligence]] methods which build [[SQL]], including new databases, on the fly. Rules might help dampen effects that can occur with the open-ended environment. The process would expect, and accommodate, the possibility of long run times, inconclusive results and such. These types of unknowns are [[undecidable]] [[Apriori|'before the fact']]; the need to do [[A_posterioriA posteriori|'after the fact']] evaluation of results is a prime factor of many higher-order computational situations but cannot (will not) be tolerated by an end user in the normal production mode.

Between these two extremes view of '''EUC''' there are many combinations. Some of the factors contributing to the need for further EUC research are [[knowledge]] processing, [[pervasive computing]], issues of [[Upper_ontology_%28computer_science%29Upper ontology (computer science)|ontology]], interactive [[visualization]] and analysis coupling schemes (see [[Duck_test|Duck test]]), and the like.

==EUC Ranges==

EUC might work by one type of approach that attempts to integrate the [[human interface]] [[ergonomics|ergonomically]] 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, by putting the [[knowledge]] and expertise into the computer and teaching the end user how to access it. At the same time, this approach is used when highly critical tasks are supported by computational systems ([[FAA|commercial flight]], [[nuclear plant]], and the like).

Another approach to EUC allows end users ([[Subject_Matter_ExpertSubject Matter Expert|SME]]s, ___domain experts) to control and even perform [[software engineering]] and development. In this case, it can be argued that this type of approach results mainly from deficiencies in computing that could be overcome with better tools and environments. But, high-end roles for the computer in non-trivial domains necessitate (at least, for now) a more full interchange (bandwidth for conversation) that is situational and subject to near exhaustive scrutiny (there are [[limits]] influencing how far we can go (bringing up, the necessity for a [[Duck_testDuck test|behavioral]] (also, see [[Black_box_%28systems%29Black box (systems)|black box]] below) framework)). Such cannot be filled by a pre-defined system in today's world. In a sense, the computer needs to have the same [[credentials]] as does a [[cohort]] ([[scientific method]] of [[peer review]]) in the discipline. Needless to say, this type of computing falls on the more 'open' side of the fence where scientific knowledge is not wrapped within the cloak of IP.

In the first type of approach of EUC described above, 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. That is, there may be training that reduces the time between sensor reading and action (such as the situation for a pilot of a commercial plane) however, the meaning behind the reading will include other sensor settings as well as whole context that may be fairly involved.

Computing of this type can be labelled [[Black_box_%28systems%29Black box (systems)|black box]] where trust will be an essential part, behavioral analysis is the name of the game (see [[Duck_test|Duck test]]), and there is a disparate (and very, very wide) gap between the ___domain and the computer-support [[Ontology_%28computer_science%29Ontology (computer science)|ontologies]].

In the other type of EUC described above, 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 further argue that resolving issues of '''a''' and '''b''' is not unlike the interplay between [[Distributed_computingDistributed computing|distributed]] and [[Centralized_systemCentralized system|centralized]] processing (which is an age-old concern in computing). In this 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_EngineeringBased 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.

==Trend==

The historical view regarding end users is being eroded by the internet and wireless communication, where the traditional end user is able to actively contribute and add value to the computer system. [[wiki]]s are one example where end users provide the content and free the webmaster to manage the site. Another example within the computer field is [[FLOSS]], where end users engage in all aspects of software development, from feature requests, through testing and reviews, to usability, documentation, and distribution. Music, pictures, and documents are remixed and edited to satisfy personal taste and demand. The consequence is that many countries and industries have been slow or unwilling to adjust to this emerging society, but some have seen the potential and are exploring economic possibilities.

Another trend is where users specify, and even develop, rules that may be fairly normal relationships ([[SQL]]) or be hard-core [[Applied_mathematicsApplied mathematics|numerical processes]] that may require attention being given to serious computational characteristics, such as ill-conditioning, [[Parallel_computingParallel computing|parallelisms]]. and similar issues of an ongoing nature.

==Research==

Line 26:

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.

Furthermore, issues related to computing ontologies (example: the [[Language/Action_perspectiveAction perspective]] has found success in [[Customer_Relationship_ManagementCustomer Relationship Management|CRM]], etc.) continue to be of interest to EUC.

==Analysis==

Line 33:

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_methodScientific method#Computational_approachesComputational 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_EngineeringBased Engineering|KBE]] ___domain) stands as a prime example since it is associated with the pervasive use of [[Lisp_programming_languageLisp programming language|Lisp]] by [[Engineers]] to accomplish remarkable effects through a long economic cycle.

=== Slogans ===

Line 44:

* 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_interfaceGraphical user interface|GUI]], or any [[User_interface_engineeringUser interface engineering|interface]], is only part of the [http://home.southwind.net/~jmswtlk/truth.html truth]).

<!-- The reason for this section is unclear to me

Line 61:

* [[Computer systems]]

* [[Scientific method#Computational approaches|Scientific method]]

* [[Knowledge-Based_EngineeringBased Engineering]]

* [[Computer addiction]]

* [[Mobile phones and driving safety]]