Software-As-A-Service: Implications For Business And Technology In Product Software Companies

Many software organizations are currently transitioning from an on-premises deployment model to the Software as a Service (SaaS) model. If a company restricts changes only in the business or technical perspective, the transition leads to higher costs, poor adoption of the SaaS model, and in the worst case, the company can lose its business. Much literature focuses on changes within one domain and is generally also limited to one perspective. This paper provides stakeholders (i.e. product managers, and business managers) an integrated perspective (business and technological) with a comprehensive framework that covers changes in four domains: business/product structure, revenue logic, customer relationships, and partnerships. The applicability of the proposed framework is assessed with a case study of a large software product vendor. The paper also contributes by providing a new avenue to study SaaS, with an integrated perspective for the organizational transition period. For the industry, this paper suggests a way to assess the impacts of organizational transition towards the SaaS model. With this overview in hand, software-producing organizations can use the comprehensive framework to successfully transition to become SaaS vendors

Software-As-A-Service Economics

Software-as-a-Service (SaaS) has been defined as software deployed as a hosted service and accessed over the Internet.  This paper covers the democratization and monetization of software services and uses cloud computing as the primary delivery vehicle.  Cloud computing represents a contextual shift in how computers are provisioned and accessed.  Opportunity and value exists in software-as-a-service for providers and clients, and the economic and technical essentials are reviewed in this paper

Software-as-a Service Model: Elaborating Client-Side Adoption Factors

Software-as-a-Service (SaaS) is emerging as a viable outsourcing option for clients interested in paying for the right to access through the network a standardized set of business software functions. SaaS model largely replaced the Application Service Providers (ASPs)-based model, by creating an architecture that that provides no mechanisms for customizing the software on the vendor side; all customization is done on the client side through standardized interfaces. The fact that vendors are not making any client-specific investments makes this outsourcing model quite intriguing. In this paper we investigate client’s side determinants of adopting the SaaS model. We draw on economic, strategic management, and IS theories to develop a theoretical framework. In it, we develop a more elaborate view of uncertainty as some types uncertainty increase the propensity to adopt SaaS, while other types do the opposite. Finally, we integrate the role of the internal enterprise IT architecture into our model

Customer relationship management software as a service-What is the providers' view of advantages of CRM software as a service?

"Software as a Service" (SaaS) concept emerged in the late twentieth century as a new software delivered model and is outstanding in terms of swift software delivery. Some analysts predict that the unique of some characteristics in SaaS motivate software providers to offer many types of software as a service. Customer Relationship Management (CRM) system has been delivered by providers as a service and they uses this attribute as the sole business objective ever since the time that the company was established and it has been their core business now. There should be some advantages from SaaS and those motivate software providers for offering CRM system as a service. The problem is whether CRM system as a service certainly has many advantages in fact; meanwhile, there are increasing arguments about the benefits of CRM system as a service. Furthermore, there was lack of previous scientific researches in advantages of CRM as a service and such a knowledge gap needs to be filled. Therefore, these incentives promote a research question, What is the providers' view of advantages of CRM software as a service? This study aims to gain better understanding about the advantages of CRM software as a service from providers' perspective. During this study, eight propositions were generated from a literature review. Later on, six interviews were carried out to gather empirical data used to test the eight propositions. At the end, the research has contributed the seven advantages of CRM system as a service. It is helpful for both clients and providers to comprehend the CRM system as a service advantages

Offering software as a service: Case study of system integrators

The software markets are moving from product-based business towards more service-oriented business. System Integrators (SIs) have also noted the service component\u27s increase in their customer cases and are placing more resources in their own service development. This study is focused on the SIs and the objective of this paper is to study how the integrators can use the Software as a Service (SaaS) business model in order to provide online services successfully to their customers and how they can take advantage of the associated benefits while overcoming the challenges. To providers, SaaS offers e.g. scale economies in distribution and administration costs, expansion of the potential customer base, and recurring revenue. From the customer viewpoint, SaaS services e.g. enable them to focus on their core competencies, provide easier access to technical expertise, and offer economical access to valuable software applications independent of time and location. We conducted a case study of six integrators and our findings confirm that the SIs are getting better in taking advantage of the SaaS model’s benefits, i.e. they are achieving scale and scope economies, have shortened their sales cycle, and expanded their potential customer base. The SIs are also solving or downplaying the associated challenges e.g. by placing more emphasis on scalability and customisation capabilities, and partner management

Software as a service: Undo

This paper proposes a highly automated mechanism to build an undo facility into a new or existing system easily. Our proposal is based on the observation that for a large set of operators it is not necessary to store in-memory object states or executed system commands to undo an action; the storage of input data is instead enough. This strategy simplifies greatly the design of the undo process and encapsulates most of the functionalities required in a framework structure similar to the many object-oriented programming frameworks