Content deleted Content added
Tag: Reverted |
Reverted 1 edit by Muthamizhkalai (talk): Unexplained deletions |
||
Line 13:
==EUC strategy==
EUC applications should not be evolved by accident, but there should be a defined EUC strategy.{{cn|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.{{cn|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
|last1= Vanarse|first1= Mandar|title= Business Value Assurance during the transformation journey.
|url= http://www.wipro.com/documents/business-value-assurance-during-the-transformation-journey.pdf
|website= Wipro|publisher= Wipro Limited|access-date= 26 July 2015
| quote = How should the business services be designed in terms of availability, security, scalability, interoperability, maintenance, performance, lower cost, extendibility and reliability (ASSIMPLER) from end consumer perspective?
}}
</ref>)
In businesses, an end-user concept gives workers more flexibility, as well as more opportunities for better productivity and creativity. However, EUC will work only when leveraged correctly. That’s why it requires a full-fledged strategy. Any strategy should include all the tools users might need to carry out their tasks and work more productively.
| |||