Revision as of 20:12, 26 July 2015 edit Kannan Deivasigamani (talk \| contribs) 8 edits →References Tag: section blanking ← Previous edit		Revision as of 20:26, 26 July 2015 edit undo Kannan Deivasigamani (talk \| contribs) 8 edits No edit summary Next edit →
Line 12: ==EUC strategy== EUC applications should not be evolved by accident, but there should be a defined EUC strategy. Any Application Architecture Strategy / IT Strategy should consider the white spaces in automation (Enterprise Functionality not automated by ERP / Enterprise Grade Applications). These are the potential areas where EUC can play a major role. Then ASSIMPLER parameters should be applied to these white spaces. ASSIMPLER stands for Availability, Scalability, Security, Interoperability, Maintainability, Performance, Low Cost of Ownership, Extendability and Reliability to develop the EUC Strategy.<ref>{{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\|accessdate=26 July 2015~~}}{{fact\|date=December 2014~~}}</ref>. == See also ==

End-user computing: Difference between revisions