Content deleted Content added
Citation bot (talk | contribs) Add: title. Changed bare reference to CS1/2. | Use this bot. Report bugs. | Suggested by BrownHairedGirl | Linked from User:BrownHairedGirl/Articles_with_bare_links | #UCB_webform_linked 2835/2843 |
mNo edit summary |
||
Line 7:
==Factors==
Factors contributing to the need for further EUC research include [[knowledge]] processing, [[pervasive computing]], issues of [[
Some of the issues related to end-user computing concern [[software architecture]] ([[Graphical user interface|iconic]] versus language interfaces, open versus closed,{{clarify|date=July 2013}} and others). Other issues relate to [[intellectual property]], configuration and maintenance. End-user computing allows more user-input into system affairs that can range from [[personalization]] to full-fledged ownership of a system.
==EUC strategy==
EUC applications should not be evolved by accident, but there should be a defined EUC strategy.{{citation needed|date=May 2016}} Any [[Application Architecture]] Strategy / IT Strategy should consider the white spaces in automation (enterprise functionality not automated by [[Enterprise resource planning|ERP]] / [[Enterprise Grade Applications]]). These are the potential areas where EUC can play a major role.{{citation needed|date=May 2016}} Then ASSIMPLER parameters{{which|date=May 2016}} should be applied{{by whom|date=May 2016}} to these white spaces to develop the EUC strategy. (ASSIMPLER stands for availability, scalability, security, interoperability, maintainability, performance, low [[cost of ownership]], extendibility and reliability.<ref>
Compare: {{cite web
| |||