The confi guration management and version control tools available today are rigid and effort intensive in handling complex and dynamics of modern software. There is a lack of analytics required to handle uncontrolled frequent changes to critical decision-supportive information. There is no control on different kinds of artifacts and monitoring different environments for different kind of deployments like partial
deployment, patch releases, and full and complete deployment, and creating respective rollback scenarios is very diffi cult to achieve using the currently available tools.
As cloud applications are distributed in nature, the changes in software also will be distributed. The new confi guration management system should ensure the changes happening across environments and should provide a consolidated view of application stack. This facilitates delivery managers to monitor and control confi gu- ration changes across various layers and environments of application software that includes Web and application servers, databases, different third-party components, sharewares, operating systems, and hardware.
4.20
Conclusion
With this chapter, we have tried to visualize the different changes at each life cycle stage due to cloud development and bucket them into different cloud usage patterns . Just as the cloud solutions can have generalized standards and guidelines (which organizations like BIAN are trying to address), the impact of cloud solutions on software development methodology can also be standardized.
Another point to highlight is the fact that cloud impact on SDLC is often neglected as on surface; it seems as if there are not many differences. However, as explained in this chapter, from privacy laws of different countries that can impact requirements to consideration of cost of deployment on testing and implementation processes, the impacts need to be fully analyzed and thought through.
References
1. Musings from David Chou: Architect, Microsoft, Cloud computing as a new development para- digm, 20 July 2010. http://blogs.msdn.com/b/dachou/archive/2010/07/20/cloud- computing- as-a-new-development-paradigm.aspx (2010)
2. XOrient: Cloud computing services in a typical cloud ecosystem. http://www.xoriant.com/ Cloud-Computing-Services-SaaS-PaaS-IaaS-models.html (2012)
3. Barr, J.: Amazon, six cloud usage patterns, 1 August 2011. http://cloudspring.com/cloud- usage-patterns/ (2011)
4. Nichols, C.: Top 4 cloud costing models, Wed, 28 March 2012. http://www.unitiv.com/it- solutions-blog/bid/84527/Top-4-Cloud-Costing-Models (2012)
5. Massingill, B.L., Mattson, T.G., Sanders, B.A.: Re-engineering for parallelism: an entry point into PLPP (Pattern Language for Parallel Programming) for legacy applications. http://parlab. eecs.berkeley.edu/wiki/_media/patterns/plpp.pdf (2006)
6. Varia, J.: Architecture for the cloud: best practices. Amazon Web Services http://media. amazonwebservices.com/AWS_Cloud_Best_Practices.pdf (2011)
7. Reese, G.: The AWS outage: the cloud’s shining moment, 23 April 2011. http://broadcast. oreilly.com/2011/04/the-aws-outage-the-clouds-shining-moment.html (2011)
8. Naganathan, V.: Infosys, how is testing cloud based applications different from testing on premise applications in QA clouds, 8 November 2011. http://www.infosysblogs.com/testing- services/2011/11/how_is_testing_cloud_based_app.html (2011)
9. Ramdas, J (Senior Technology Architect, Infosys LTD)., Srinivas, J (Principal Architect, Infosys LTD).: Extend Java EE containers with cloud characteristics, 12 May 2011. www.ibm. com/developerworks/cloud/library/cl-jeecontainercloud/ (2011)
10. Godinez, M., Hechler, E., Koenig, K., Lockwood, S., Oberhofer, M., Schroeck, M.: The art of enterprise architecture. http://www.amazon.com/Art-Enterprise-Information-Architecture- Systems-Based/dp/0137035713 (2010)
11. Arista, C.: Cloud networking: design patterns for “Cloud-Centric” application environments. http://www.techrepublic.com/whitepapers/cloud-networking-design-patterns-for-cloud-cen- tric-application-environments/2393983 (2009)
12. Kothandaraman, H.: Testing Applications n Cloud. LEF Grant Briefi ng. http://assets1.csc. com/lef/downloads/LEFBriefi ng_TestingApplicationsCloud_021011.pdf (2011)
13. Flynn, M.J.: Computer Architecture: Pipelined and Parallel Processor Design. http://public. callutheran.edu/~reinhart/CSC521MSCS/Week5/FlynnTaxonomies.pdf (1996)
14. Roodenrijs, E.: Testing on the cloud, A sogeti point of view on the potential of software testing using cloud computing. http://www.sogeti.com/upload/COM/Curious%20about%20us/ Documents/PoV%20-%20A%20Sogeti%20Test%20Cloud_v1%200.pdf (2010)
15. Williams, B.J., Carver, J.C.: Characterizing software architecture changes: an initial study. In: ESEM 2007, pp. 410–419 http://www.google.co.in/url?sa=t&rct=j&q=characterizing%20 s o f t w a r e % 2 0 a r c h i t e c t u r e % 2 0 c h a n g e s % 3 A % 2 0 a n % 2 0 i n i t i a l % 2 0 s t u d y & s - ource=web&cd=1&cad=rja&ved=0CC4QFjAA&url=http%3A%2F%2Fciteseerx.ist.psu.edu %2Fviewdoc%2Fdownload%3Fdoi%3D10.1.1.123.6396%26rep%3Drep1%26type%3Dpdf &ei=n3pJUbfSMY6zrAet64GYDQ&usg=AFQjCNHlS847JhguLPP23LfMh9Nonz1Fbw&bv m=bv.44011176,d.bmk (2007)
101 Z. Mahmood and S. Saeed (eds.), Software Engineering Frameworks for the Cloud
Computing Paradigm, Computer Communications and Networks, DOI 10.1007/978-1-4471-5031-2_5, © Springer-Verlag London 2013
Abstract Information technology (IT) today has evolved into a rapidly changing and dynamic science. Timelines have shrunk drastically for technology from being termed cutting edge to becoming obsolete. In such a fast-changing and dynamic world needing customised solutions, cloud computing offers a viable alternative. Cloud can overcome the redundancy factor and evolve over time to suit user needs. It is characterised by a wide array of deployment models and services that are very promising. While the concept of cloud computing has been around for some time now, industry adoption has been rather slow. Due to the sheer possibilities on offer, one remains optimistic of wider acceptance of this technology in future. This chap- ter takes us through the steps needed to validate the choice of public cloud via risk - based feasibility analysis. The chosen option can be built into needed IT systems based on cloud variants of the classic life cycle model. This chapter discusses the phases and activities of this development. The Wrapper model discussed here will enable better understanding of system control determinants for services opted on the cloud. A case study is discussed to help provide a better insight and understand- ing of the life cycle model.
Keywords Software life cycle • Cloud provision • Wrapper model
5.1
Introduction
Rapid adoption of the World Wide Web has brought a paradigm shift in business computing. This transformation can be attributed to the robust client-server archi- tecture of the Web and its request-response operation model. The days of using