Assessing the Readiness to Move into the Cloud

  • Leire Orue-Echevarria
  • Juncal Alonso
  • Marisa Escalante
  • Stefan Schuster
Part of the Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering book series (LNICST, volume 112)


The race to keep software compatible and optimal with respect to the latest trends is hard. 90% of software cost can be due to maintenance, and 75% on developing new features to stay competitive and relevant. The industry progresses through periods of incremental development interspersed with true paradigm shifts. Legacy software must keep up the pace.

At present we are experiencing one of these paradigm shifts, as remarked by the EC [1] “The speed of change in Internet technologies continues to be impressive. Software is becoming more and more pervasive: it runs on the devices that we use every day ... [opening] a new world of possible applications”. Today, technological and business model innovation generates large demand for the transition of legacy software towards modernization. However, software modernization is not a trivial issue and if improperly done, it dangers the business continuity and sustainability.

This means that for any company meditating about the transition to the new paradigm of cloud computing, there is a need to have at its disposal an innovative and combined technical and business analysis on the maturity and prospect of the legacy application. The major target of this process is to identify in advance the perspectives of the migration and pre-evaluate the performance and business benefits with relation to the cost of the process. For the first time, the business value will be directly attached to the technical performance.

This paper presents this aforementioned approach, being currently developed and tested, in order to assess the maturity of an application and the convenience of migrating to the new cloud computing paradigm or not, based on quantitative indicators while always ensuring the company’s business continuity. Following this approach, questions such as cost and effort of the migration, impact of new business models in the company or return of the investment will be provided in advance of tackling the actual modernization.


Cloud Computing Business Model Business Model Innovation Legacy Application Business Analysis 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
  2. 2.
  3. 3.
    Simon, F., Seng, O., Mohaut, T.: Code-Quality-Management. Dpunkt.Verlag, Heidelberg (2006)Google Scholar
  4. 4.
    Orue-Echevarria, L., Alonso, J., Gottschick, J., Restel, H.: FROM SOFTWARE-AS-A-GOOD TO SAAS: CHALLENGES AND NEEDS. Developing a tool supported methodology for the migration of non-SaaS applications to SaaS. In: ICSOFT 2011 (2011)Google Scholar
  5. 5.
  6. 6.
    Wu, B., Lawless, D., Bisbal, J., Grimson, J., Wade, V., O’Sullivan, D., et al.: Legacy systems migration - a method and its tool-kit framework. Paper presented at the Joint 1997 Asia Pacific Software Engineering Conference and International Computer Science Conference (1997)Google Scholar
  7. 7.
    Khusidman, V., Ulrich, W.: Architecture-Driven Modernization: Transforming the Enterprise. OMG (2007)Google Scholar
  8. 8.
    Warren, I., Ransom, J.: Renaissance: A Method to Support Software System Evolution Paper presented at the 26th Annual International Computer Software and Applications Conference (2002)Google Scholar
  9. 9.
  10. 10.
  11. 11.
  12. 12.
  13. 13.
  14. 14.
  15. 15.
    Moyer, C.: Building Applications in the Cloud. Ed. Addison Wesley (2011)Google Scholar
  16. 16.
    Reese, G.: Cloud Application Architectures. Ed. O’Reilly Media (2009)Google Scholar
  17. 17.
    Sosinsky, B.: Cloud Computing Bible. Ed.Wiley (2011)Google Scholar
  18. 18.
    Chate, S.: Convert your web application to a multi-tenant SaaS solution. IBM developerWorks (2010)Google Scholar
  19. 19.
    Chidamber, S.R., Kemerer, C.F.: Towards a Metrics Suite for Object Oriented Design. In: Proceedings of OOPSLA 1991, pp. 197–211 (1991)Google Scholar
  20. 20.
    Chidamber, S.R., Kemerer, C.F.: A Metrics Suite for Object Oriented Design. IEEE Transactions on Software Engineering 20(6), 476–493 (1994)CrossRefGoogle Scholar
  21. 21.
    Li, W., Henry, S.: Object-oriented metrics that predict maintainability. Journal of Systems and Software 23(2), 111–122 (1993)CrossRefGoogle Scholar
  22. 22.
    Lee, Y.S., Liang, B.S., Wu, S.F., Wang, F.J.: Measuring the Coupling and Cohesion of an Object-Oriented Program Based on Information Flow. In: Proceedings of International Conference on Software Quality, Maribor, Slovenia (1995)Google Scholar

Copyright information

© ICST Institute for Computer Science, Social Informatics and Telecommunications Engineering 2013

Authors and Affiliations

  • Leire Orue-Echevarria
    • 1
  • Juncal Alonso
    • 1
  • Marisa Escalante
    • 1
  • Stefan Schuster
    • 1
  1. 1.TECNALIA. ICT / European Software Institute Divison, Parque Tecnológico Ed. #202ZamudioSpain

Personalised recommendations