The future of software engineering IN and FOR the cloud

Abstract

Experts are predicting the cloud software market to grow at a high rate in the coming years. Merrill Lynch and Gartner predict the cloud computing market to be worth between $160 and $150 billion in 2013. Many computing services have now migrated to the cloud and many applications are becoming cloud-based and function as standalone or in orchestration with other cloud-based services. With the advent of the cloud and the reliance on Big Data, cloud-based systems are driving our digital economy and increasingly becoming pervasive in many daily applications. Cloud has become the backbone for many e-businesses; engineering, scientific and experimental processes; real-time control and monitoring data intensive systems such as disaster management, weather and climate predictions, which heavily depends on the Big Data thing. The dependability of these systems and their continuous evolution are essential pre-requisite for the success and prosperous growth of our digital economy. The "cloud wave" has urged the need for advancing the fundamentals of cloud software engineering, supporting the emergence and the advancement of this emergent digital economy.Practitioners are very likely to beg, borrow and steal from software engineering in-the-small to benefit the case of software engineering for the large-scale and ultra-large-scale, as it is the case of the cloud. Though the fundamentals of engineering software in both paradigms exhibit resemblance, software engineering for the cloud require novel approaches, which address the interplay between technical, economics-driven considerations and shifts software engineering towards utility-based engineering for software-, infrastructure-, data storage-and/or platform-as services. Given the unpredictable, dynamic, elasticity and on-demand nature of the cloud, it would be unrealistic to assume that traditional software engineering can "cleanly" satisfy the cloud behavioural requirements. Much of cloud software engineering, for examples, involves problems related to designing for emergent behaviour and engineering for scale and its economies in unpredictable, volatile and highly uncertain world. The paradigm has introduced new challenges and problems shaping the scientific and engineering queries and likely to shape the research landscape of software engineering for at least the next decade: cloud requirements engineering; architecting for the cloud; cloud security software engineering; service-level Agreement(SLA) compliance; maintenance, testing and evolution for the cloud; virtualisation; autonomic and self-* management for scale; cloud as a market place and economics-driven software engineering for the cloud; multitenancy and federation; dependability and performance engineering for the cloud; allocation assignment and dynamic balancing and optimisation for resources to achieve pragmatic trade-offs between many competing technical , short-term and strategic business objectives.The goal of this special issue is to strengthen the cross-fertilization of advances from software engin...

Measuring the maturity of Indian small and medium enterprises for unofficial readiness for capability maturity model integration‐based software process improvement

“…6 They are crucial for the prioritization of the steps involved within SPI. 49,50 Additionally, they are important for the identification of the different improvements that can be implemented and increase benefits to the organization within short-term periods. 51 Also, the model aims at a process's constant improvement.…”

DeepVS: an efficient and generic approach for source code modelling usage

“…The Deep Cloud platform is used as a centralized deep learning model attendant to determine the likelihood scores for the next source code suggestion task. Here, we choose cloud platform [2] because of its centralized nature and scalability. Our Deep Cloud is a platform as a service-based cloud.…”

Experimental Evaluation of the Cloud-Native Application Design

“…Delivering software applications from the cloud requires a new way of thinking about software architectures and software engineering processes [1]. Typical cloud service environments with raw infrastructure and featureful platform services (IaaS and PaaS, respectively) offer multiple benefits over other software hosting and delivery paradigms.…”

“…This paper therefore does not attempt to argue for CNA, for which we refer to our previous publication [5]. It is also not a step-by-step guide to CNA, for which we refer to our detailed posts on this topic 1 . Instead, it briefly repeats the CNA characteristics and then focuses on a thorough evaluation.…”