Content deleted Content added
No edit summary |
No edit summary |
||
Line 1:
{{cleanupdate|April 13}}
'''End User Computing''' can mean several things. However, given the intertwining of [[computation]] into all advanced disciplines, any tool (inclusive of any type of capability related to a ___domain/discipline) that is provided by a computer becomes part of the discipline (methodology, etc.).
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]].
Some of the issues related to End User Computing concern architecture (iconic versus language interface, open versus closed, ...). These continue to be studied.
Other issues relate to IP, configuration, maintenance, ...
End User Computing has a range of forms and values. Most early computer systems were tightly controlled by an IT department. Users were just that. The advent of the personal workstation opened up the door, so to speak.
End User Computing allows more user input into system affairs that can range from personalization to full-fledged ownership of the system.
Examples of End User Computing are [[ICAD]] (Example of the pervasive use of [[Lisp_programming_language|Lisp]] by [[Engineers]]), [[SQL]], ...
==
*'''Slogan 1''': good '''End User Computing''' practices might help temper things such as the [[AI Winter]].
*'''Slogan 2''': the computational needs to wed with the phenomenal (are 'borgs' inevitable?).
== See also ==
* [[Software engineering]]
==External links==
|