Software as a service

About: Software as a service is a research topic. Over the lifetime, 8514 publications have been published within this topic receiving 136177 citations. The topic is also known as: Service as a Software Substitute & SaaSS.

Why software process innovations are not adopted

Abstract: 0 7 4 0 7 4 5 9 / 0 1 / $ 1 0 . 0 0 © 2 0 0 1 I E E E W hat do these modern, buzzword software methods have in common: eXtreme Programming, Crystal, lean programming, scrum, feature-driven development, adaptive software development, “good enough” software, personal software process/team software process, Rational Unified Process, rapid development, code complete, ...? They all offer something in exchange for a change in work habits, and sometimes in exchange for a “culture” change, too. An important reason organizations do not adopt such methods—that is, do not use them in daily software development—is that what the methods offer is not as important (read “cost-effective”) as staying with the status quo. This has nothing to do with inertia or resistance to change. Put more strongly, what these methods offer is irrelevant. Put more diplomatically, what they offer is not strategic for the enterprise. All the buzzword methods offer to reduce cost or effort, duration or time to market, or defects, and most offer to reduce all of these. How can we object? Don’t we all agree that those reductions are desirable, even necessary, especially considering our profession’s sorry state? My perspective comes from two disparate directions: I have read nearly everything on adopting process innovations, and I have seen adoption succeed and fail in many software development organizations. What explains the difference between success and failure? The standard answers are about upper-management commitment and sponsorship, the ability or persuasiveness of change agents, the divisibility of the innovation, how disruptive the innovation is, and whether the change is planned and managed. All those are important, but I have seen something that is more powerful and more dominant: alignment with strategy. When the method is aligned with the organization’s strategy, the adoption is much more often successful.

Design and auditing of Cloud computing security

Abstract: Cloud computing is the long dreamed vision of computing as a utility, where data owners can remotely store their data in the cloud to enjoy on-demand high-quality applications and services from a shared pool of configurable computing resources. While data outsourcing relieves the owners of the burden of local data storage and maintenance, it also eliminates their physical control of storage dependability and security, which traditionally has been expected by both enterprises and individuals with high service-level requirements. This paper, gives a brief introduction to Cloud computing privacy issue being addressed is then introduced, by describing some of the unique factors to be considered when data enters the Cloud. Finally, a data protection scheme with public auditing scheme is outlined that will address a number of these factors, by providing a mechanism to allow for data to be encrypted in the Cloud without loss of accessibility or functionality for authorized parties. This scheme is not necessarily a replacement for traditional privacy and security measures for data, but rather an enhancement which allows users (again, at either the individual or enterprise level) a greater degree of confidence in the adoption of innovative, cost-saving Cloud computing technologies.

A Model of Competition Between Perpetual Software and Software as a Service

Abstract: Software as a service (SaaS) has grown to be a significant segment of many software product markets. SaaS vendors, which charge customers based on use and continuously improve the quality of their products, have put competitive pressure on traditional perpetual software vendors, which charge a licensing fee and periodically upgrade the quality of their software. We develop an analytical model to study the competitive pricing strategies of an incumbent perpetual software vendor in the presence of a SaaS competitor. We find that, depending on both the SaaS quality improvement rate and the network effect, the perpetual software vendor adopts one of three different strategies: (1) an entry deterrence strategy, (2) a market segmentation strategy, or (3) a sequential dominance strategy. Surprisingly, we find that vendor competition does not always result in higher consumer surplus, and it might lead to a socially inefficient outcome under certain conditions. We further show insights into how the incumbent perpetual software vendor can defend its market position by providing incremental quality improvement through patching and/or by releasing consecutive versions with major quality upgrades. Finally, we extend our model to include the vendor’s quality improvement cost and users’ switching cost. These additional analyses help to identify the effect of different quality and cost factors on the market competitive equilibrium.

Toward Advanced Mobile Cloud Computing for the Internet of Things: Current Issues and Future Direction

Abstract: Cloud computing is the coming new era of information processing and has proved its benefits in high scalability and functional diversity. However, almost all cloud-computing architectures including SaaS, PaaS, and IaaS are vulnerable to serious security issues. Similarly, Mobile Cloud Computing (MCC) is vital to overcoming mobile limited storage and computing capabilities. MCC authentication and authorization issues must be provided on two levels: login password control and the environment from where the cloud is accessed. MCC has overcome the barrier of limited storage by providing remote storage but requires a strict security system that is responsible for retrievability, integrity, and seamless storage access. Elasticity and connectivity are also of major concern in MCC because delays and jitters cause degradation in the user experience. Cloud-computing architecture creates more challenges in maintaining security because of the liberty of users to choose any MCC architecture. Thus in this paper we discuss current cloud computing issues and future directions.

‘Robot-Cloud’: A framework to assist heterogeneous low cost robots

Abstract: This paper gives a framework to offer assistance to low cost ROS (Robot Operating System) supported heterogeneous robots in a large environment through cloud. To build such a system ‘Robot-Cloud’ is prepared which extends the functionality of a robot. A ‘Robot-Cloud’ is designed and implemented with components like cloud controller, ROS master node, storage unit, Map-reduce computing cluster and robotic services. In this system every robot is facilitated with ROS capability that helps to provide abstraction over hardware, heterogeneity and communication over TCP/IP. All the robots communicate with a master node present at the cloud controller to avail communication with other robots and to request services from the cloud. Our system supports all three basic service models i.e. Saas, PaaS and IaaS by incorporating typical SOA (Service Oriented Architecture) functionality. This approach can also be utilized to achieve a common goal for the networked robots. Finally, some simulation results are given to support the claimed framework.