End-user computing: Difference between revisions

Content deleted Content added
Cydebot (talk | contribs)
m Robot - Speedily moving category Human-computer interaction to Human–computer interaction per CFDS.
Remove confusing sentence. There's nothing in "duck test" which explains what "analysis coupling schemes" are.
Line 8:
:For the second approach, [[SQL]] administration would allow for end-user involvement at several levels including administration itself. Users would also define queries though the supporting mechanism may be constrained in order to reduce the likelihood of run-away conditions that would have negative influence on other users. We see this already in some [[business intelligence]] methods which build [[SQL]], including new databases, on the fly. Rules might help dampen effects that can occur with the open-ended environment. The process would expect, and accommodate, the possibility of long run times, inconclusive results and such. These types of unknowns are [[undecidable]] 'before the fact'; the need to do [[A posteriori|'after the fact']] evaluation of results is a prime factor of many higher-order computational situations but cannot (will not) be tolerated by an end user in the normal production mode.
 
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]], issues of [[Upper ontology (computer science)|ontology]], [[interactive visualization]] and analysis coupling schemes (see [[Duck test]]), and the like.
 
==EUC Ranges==