Content deleted Content added
m typos and some little content changes |
m --> move bulk of Lead In to EUC Range |
||
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 or at improving 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.
: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). ▼
: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 situational, subject to exhaustive scrutiny, and that cannot be filled by a pre-defined systems 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. ▼
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 case, a computing group would keep these canned routines up to date through the normal development/maintenance methods.
Line 12 ⟶ 8:
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, interactive visualization/analysis schemes, and the like.
==EUC
▲
▲
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.
| |||