End-user computing: Difference between revisions

Revision as of 04:00, 10 April 2016

Revision as of 00:41, 19 May 2016

Line 12:

==EUC strategy==

EUC applications should not be evolved by accident, but there should be a defined EUC strategy.{{cn}} Any [[Application Architecture]] Strategy / IT Strategy should consider the white spaces in automation (Enterpriseenterprise Functionalityfunctionality not automated by [[Enterprise resource planning | ERP]] / [[Enterprise Grade Applications]]). These are the potential areas where EUC can play a major role.{{cn}} Then ASSIMPLER parameters{{which?}} should be applied{{by whom?}} to these white spaces to develop the EUC strategy. (ASSIMPLER stands for Availabilityavailability, Scalabilityscalability, Securitysecurity, Interoperabilityinteroperability, Maintainabilitymaintainability, Performanceperformance, Lowlow Cost[[cost of Ownershipownership]], Extendabilityextendibility and Reliability to develop the EUC Strategyreliability.<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|accessdate= 26 July 2015}}</ref>

| 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>)

== See also ==