End-user computing: Difference between revisions

Revision as of 16:17, 1 June 2006

Revision as of 18:17, 1 June 2006

Line 1:

{{cleanupdate|April 13}}

'''End User Computing''' (EUC) is a group of approaches to computing that aim at better integrating [[End-user_%28computer_science%29|end users]] into the computing environment. Oneor suchat trend attempts to integrateimproving the [[humanpotential interface]]for [[ergonomics|ergonomically]]high-end into a [[user centered design]] system throughout its [[technology lifecycle|life cycle]]. In this sense, EUC's goal iscomputing to allowperform unskilledin staffa to use expensive and highly skilledtrustworthy knowledgemanner in theirproblem jobs,solving by puttingof the knowledgehighest and expertise into the computer and teaching the end user how to access itorder. Another trend is to allow end users (SMEs, ___domain experts) to control and even perform software engineering and development.

:One type of approach 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 (commercial flight, nuclear plant, and the like).

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.

:Another type of approach allows end users (SMEs, ___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 necessitates (at least, for now) a more full interchange (bandwidth for conversation) that is situtational, subject to exhaustive scrutiny, and that cannot be filled by a pre-defined systems in today's world.

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.

A simple example of these two exteremes can use [[SQL]]. The first approach would have canned queries and reports that for the most part would be invoked with buttons and/or simple commands. The latter approach allows for end-user defintion of queries though these may be constrained in order to reduce the likelihood of run-away conditions that would have negative influence on other users. But, taken further, some business intelligence methods build [[SQL]] on the fly. There may be rules that dampen effects, however it is not hard to conceive of an open-ended environment being set up for this type of work.

Also, 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, engineering chaos, and the like.

==EUC Range==

In the formerfirst sensetype 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]] where trust will be an essential part.

In the latterother sensetype 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 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.

==Trend==