End-user computing: Difference between revisions

Revision as of 18:17, 1 June 2006

Revision as of 18:28, 1 June 2006

Line 4:

: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 situtationalsituational, 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 exteremesextremes 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. TheIn latterthis approachcase, allowsa forcomputing end-usergroup defintionwould of queries thoughkeep these maycanned beroutines constrainedup into orderdate to reducethrough the likelihoodnormal of run-away conditions that would have negative influence on other users. But, taken further, some business intelligencedevelopment/maintenance 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.

For this example, the latter approach would allow for end-user definition 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 setup for this type of work (with the associated long run times expected and allowed).

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.

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, engineeringinteractive chaosvisualization/analysis schemes, and the like.

==EUC Range==

Line 15 ⟶ 17:

Computing of this type can be labelled [[black box]] where trust will be an essential part.

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 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 thissensethis 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.

==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 useabilityusability, documentation, and distribution. Music, pictures, and documents are remixed and edited to satisifysatisfy 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 numerical processes that may require attention being given to serious computational characteristics, such as ill-conditioning, parallelisms. and similar issues of an ongoing nature.