Content deleted Content added
mNo edit summary |
|||
Line 3:
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 approach, a computing group would keep these canned routines up to date through the normal development/maintenance methods. For the latter 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]] [[Apriori|'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_%28computer_science%29|ontology]], interactive [[visualization]] and
==EUC Ranges==
| |||