End-user computing: Difference between revisions

Revision as of 02:40, 8 September 2010

Revision as of 02:43, 8 September 2010

Line 39:

As such, the issue arises about how open the tool is to scrutiny. Some disciplines require more understanding of the tool set than do others. That is, tools that are [[operational]] in scope require less understanding than those that are [[ontological]]. As an example of the latter type of influence on disciplines, consider the impact that the computer has had on the [[Scientific method#Computational approaches|scientific method]].

Some of the issues related to End User Computing concern architecture (iconic versus language interface, open versus closed, and others). These continue to be studied. Other issues relate to IP, configuration, maintenance, ... End User Computing allows more user input into system affairs that can range from personalization to full-fledged ownership of the system. One example is to use cloud applications to manage a [http://isapp.fsksm.utm.my/ project] front and back-end.

Examples of End User Computing are systems built using the [[Fourth-generation programming language|4GLs]], such as [[MAPPER (Software)|MAPPER]] or [[SQL]], or one of the [[Fifth-generation programming language|5GLs]], such as [[ICAD]]. [[ICAD]] (in the [[Knowledge-Based Engineering|KBE]] ___domain) stands as a prime example since it is associated with the pervasive use of [[Lisp programming language|Lisp]] (one of the [[Third-generation programming language|3GLs]]) by [[Engineers]] to accomplish remarkable effects through a long economic cycle.