Revision as of 00:41, 19 May 2016 edit Jandalhandler (talk \| contribs) Extended confirmed users 8,605 edits →EUC strategy ← Previous edit		Revision as of 01:02, 19 May 2016 edit undo AnomieBOT (talk \| contribs) Bots 6,856,162 edits m Dating maintenance tags: {{Cn}} {{By whom?}} {{Which?}} Next edit →
Line 12: ==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.

End-user computing: Difference between revisions