End-user computing: Difference between revisions

Revision as of 05:57, 31 December 2011

Revision as of 13:35, 2 February 2012

Line 19:

Computing of this type can be labelled [[Black box (systems)|black box]] where trust will be an essential part, behavioral analysis is the name of the game (see [[Duck test]]), and there is a disparate (and very, very wide) gap between the ___domain and the computer-support [[Ontology (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 computing|distributed]] and [[Centralized 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 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 [[Visual Basic for Applications|VBA]], [[C++]], and the like. This type of co-jointness is an example of a ___domain tool augmented with non-trivial extensibility.

==Trend==