End-user computing: Difference between revisions

Revision as of 03:08, 29 May 2006

Revision as of 13:50, 1 June 2006

Line 1:

'''End User Computing''' (EUC) refers to several things. For one, it refers to the [[human interface]], [[ergonomics|ergonomically]] integrated into a [[user centered design]] system throughout its [[technology lifecycle|life cycle]]. 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. For another, it refers to software engineering and development controlled by and even performed by the end user (SME, ___domain expert, ...)

{{cleanupdate|April 13}}

'''End User Computing''' (EUC) refers to the [[human interface]], [[ergonomics|ergonomically]] integrated into a [[user centered design]] system throughout its [[technology lifecycle|life cycle]]. 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.

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

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 hacker). '''a''' is the normal approach of the IT-driven situation. '''b''' 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 central and distributed processing (which is an age-old concern in computing).

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 learn one console, they will be able to operate all consoles. Addmitedly each console will have new components, but training is limited to those, not the whole console.

ComputerIn 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 learn one console, they will be able to operate all consoles. AddmitedlyAdmittedly each console will have new components, but training is limited to those, not the whole console.

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.

Line 10 ⟶ 13:

==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 useability, documentation, and distribution. Music, pictures, and documents are remixed and edited to satisify 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.

==Research==

Line 15 ⟶ 20:

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.

Too, issues related to computing (example: [[Language/Action_perspective]] has found some success in [[CRM]], etc.) continue to be of interest to EUC.

==Analysis==

Line 28 ⟶ 35:

=== Slogans ===

* Computing concerns and good End User Computing can be antithetically related.

* 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?).