Showing papers on "Software as a service published in 2008"

System and method for programmatic management of distributed computing resources

Abstract: Systems and methods for providing a development and deployment platform for Software as a Service (SaaS) providers are disclosed. The platform may provide an application programming interface (API) through which customers may configure virtualized grids of language-level virtual machines (VMs), networks, and storage resources. A grid may be horizontally scalable and programmatically configurable by a customer and/or customer code. The platform may allow dynamic scaling of resources (up and down) to match changing demands, by allowing customers and/or customer code to programmatically alter their own system level structure at runtime, through the API. The grid may be accessed by both on-grid and off-grid processes, through internal and external connectivity resources provided by the platform. The platform may provide common utilities for end-user services, deployment operations, and development tasks (e.g., debugging), and may include frameworks and macro-components (e.g. web servers). The platform may host long-running Internet-based services and/or one-shot computational services.

Developing Software Online With Platform-as-a-Service Technology

Abstract: One of the hot topics in computer technology is software as a service, in which vendors host applications on the Internet and provide them via a browser to users, who perform and store their work online. Users thus don't have to worry about developing, hosting, updating, or maintaining applications or storing data. Several vendors have taken the SaaS concept a big step further and now offer platform as a service systems. PaaS systems are generally hosted, Web-based application-development platforms, providing end-to-end or, in some cases, partial environments for developing full programs online. They handle tasks from editing code to debugging, deployment, runtime, and management. In PaaS, the system's provider makes most of the choices that determine how the application infrastructure operates, such as the type of OS used, the APIs, the programming language, and the management capabilities. Users build their applications with the provider's on-demand tools and collaborative development environment.

Software as a Service: Configuration and Customization Perspectives

Abstract: Software as a service (SaaS) provides software application vendors a Web based delivery model to serve big amount of clients with multi-tenancy based infrastructure and application sharing architecture so as to get great benefit from the economy of scale. Though SaaS application is usually developed with highly standardized software functionalities to serve as many clients as possible, many clients still ask for function variants according to their unique business needs through easy configuration and customization. Due to the subscription based model, SaaS vendors need take a well designed strategy to enable self serve configuration and customization by their customers without changing the SaaS application source code for any individual customer. In this paper, we will explore the configuration and customization issues and challenges to SaaS vendors, clarify the difference between configuration and customization. A competency model and a methodology framework have been developed to help SaaS vendors to plan and evaluate their capabilities and strategies for service configuration and customization.

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

Abstract: Software-as-a-Service (SaaS) is emerging as a viable outsourcing option for clients interested in paying for the right to access a standardized set of business software functions through the network. SaaS model largely replaced the Application Service Providers (ASPs) model, by creating an architecture 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 the SaaS model adoption. We draw on economic, strategic management, and Information Systems theories to develop a theoretical framework. By integrating diverse literature streams, we are able to develop a more elaborate view of uncertainty arguing that some types uncertainty increase the propensity to adopt SaaS, while other types do not. Finally, we argue that the maturity of the client's internal enterprise IT architecture plays an important role in SaaS adoption decisions.

A Software as a Service with Multi-tenancy Support for an Electronic Contract Management Application

Abstract: In most commercial electronic contract management applications available today, different customized code base has to be developed, deployed and operated to support each tenant. Few advanced commercial electronic contract management applications use a single code base with configuration options to support multi-tenants. However, a separate instance of the code base still has to be deployed and operated for each tenant even in these applications. The business model of having to support a single application instance for each tenant makes an electronic contract management application and other critical business applications out of reach for most small and medium businesses (SMBs), in particular, the very small businesses (SVBs) because of its high development and maintenance cost. Recently, a new business model of a single application instance supporting multi-tenancy based on software as a service (SaaS) has emerged making expensive business applications more affordable for SMBs and SVBs for multi-tenancy [1]. In this paper, we present the first of a kind multi-tenancy SaaS electronic contract management application. We also describe several novel methods used in the metadata, security and shared services, as well as customization and tenant extensions modules to support multi-tenancy SaaS in this application. This multi-tenancy SaaS application has shown to benefit both the application service providers as well as their tenants. This new multi-tenancy SaaS model can reduce the application hosting cost and make the application more affordable to the tenants because of its capabilities in customization and scalability while continuing to support an increasing number of tenants. It furthers benefits tenants by saving their money and time with immediate access to the latest IT innovations and infrastructure improvements on a single application code base. Most end users of tenants have found their productivities increased, the contract transaction time accelerated, contractual errors reduced in using this multi-tenancy SaaS electronic contract management application as demonstrated in several ongoing IBM pilot programs serving more than ten tenants with over 3000 end users.

A Study and Performance Evaluation of the Multi-Tenant Data Tier Design Patterns for Service Oriented Computing

Abstract: Multi-tenancy is one of key characteristics of the service oriented computing especially for Software as a Service (SaaS) to leverage economy of scale to drive down total cost of ownership for both service consumer and provider. This paper aims to study the technologies to build a cost-effective, secure and scalable multi-tenant infrastructure, especially in data tier. We first explore all the key implementation patterns of data tier multi-tenancy on aspects of isolation, security, customization & scalability etc. Furthermore, we mainly evaluate the performance of these design patterns on aspects of isolation and security via a series of experiments and simulations. This paper also identifies the potential performance bottlenecks, summarizes corresponding optimization approaches and best implementation practices for different multi-tenant business usage models.

What's in a Name? Distinguishing between SaaS and SOA

Abstract: Considerable confusion arises in distinguishing between software as a service (SaaS) and service-oriented architecture (SOA). Zachman's framework can help to try to make sense of the alphabet soup of Web services and utilities that form the basis for both SOA and SaaS. The difference between SaaS and SOA is that the former is a software-delivery model whereas the latter is a software-construction model. A better way to illuminate the differences between these two concepts is to use the well-known Zachman architectural model. In this article, we briefly examine the concepts of SaaS and SOA, followed by a brief history of software architectural models. We use the Zachman model to differentiate the two architectural approaches to building software. Because the Zachman model is so intuitive, the approach we take to describe the differences between SaaS and SOA works well even with non-IT professionals.

Green IT: Reduce Your Information System's Environmental Impact While Adding to the Bottom Line

Abstract: Reduce the environmental and budgetary impact of your IT infrastructure This groundbreaking work offers a complete roadmap for integrating environmentally sound techniques and technologies into your Information Systems architecture. Green IT explains how to adopt a business-driven green initiative and provides a detailed implementation plan. You will find strategies for reducing power needs, procuring energy from alternative sources, utilizing virtualization technologies, and managing sustainable development. Case studies highlighting successful green IT projects at major organizations are included. Keep your IT department and your organization in the green--both environmentally and financially--with help from this comprehensive guide. Work within current global initiatives and standards for e-waste Minimize power usage and use alternative cooling methods in your datacenter Transition your office into a paperless environment Equip your organization with green hardware, including EPEAT-, RoHS-, and ENERGY STAR-certified machines Implement efficient datacenter design in terms of energy consumption, cooling, server configuration, consolidation, cabling, redundancy, and more Virtualize servers and storage using the latest technologies from VMware, Microsoft, Compellent, Incipient, and others Measure existing datacenter efficiency using current metrics, and track progress with Business Intelligence tools Establish a green supply chain Explore the Software as a Service (SaaS) model Manage ongoing compliance and sustainable growth Table of contents Part I: Trends and Reasons to Go Green Chapter 1. Overview and Issues Chapter 2. Current Initiatives and Standards Part II: Consumption Issues Chapter 3. Minimizing power usage Chapter 4. Cooling Part III: What You Can Do Chapter 5. Changing the Way We Work Chapter 6. Going Paperless Chapter 7. Recycling Chapter 8. Hardware Considerations Part IV: Case Studies Chapter 9. Technology Businesses Chapter 10. Other Organizations Part V: The Greening Process Chapter 11. Datacenter Design and Redesign Chapter 12. Virtualization Chapter 13. Greening Your Information Systems Chapter 14. Staying Green

Defining Composite Configurable SaaS Application Packages Using SCA, Variability Descriptors and Multi-tenancy Patterns

Abstract: Currently, several vendors and projects are building proprietary SaaS platforms where more and more applications are hosted in a Software as a Service business model. However, these proprietary platforms prevent that applications offered by different SaaS application vendors can be easily reused on the platforms offered by the different SaaS hosting providers. In this paper we describe a package format for composite configurable SaaS application packages for applications developed following a service oriented architecture. We show how the service component architecture (SCA) can be extended with variability descriptors and SaaS multi-tenancy patterns to package and deploy multi- tenant aware configurable composite SaaS applications.

Generation of BPEL Customization Processes for SaaS Applications from Variability Descriptors

Abstract: Software as a service (SaaS) is a new delivery model for software. Software in a SaaS model is no longer run exclusively for one customer at a customer's premise but run at a service provider and accessed via the Internet. A provider of software as a service exploits economies of scale by hosting and providing the same application for several different customers. However, each individual customer has different requirements for the same basic application. In order to allow each customer to customize the process layer and related artifacts of a SaaS application to their specific needs the application needs to provide a set of variability points that can be modified by customers. In this paper we describe the notion of a variability descriptor that defines variability points for the process layer and related artifacts of process-based, service-oriented SaaS applications. Furthermore we describe how these variability descriptors can be transformed into a WS-BPEL process model that can then be used to guide a customer through the customization of the SaaS application.

Towards Service Engineering: Service Orientation and Business-IT Alignment

Abstract: The rapid movement towards service orientation, on both the business and technology fronts, offers unprecedented opportunities for business-IT alignment. As we will argue, to achieve true agility in its service provisioning to meet rapidly changing requirements, an organization needs a multi-dimensional business-IT alignment strategy - alignment via architecture, via governance and via communication - integrated with a service oriented architecture (SOA) paradigm to develop their service-based system. To help engineer such a service-based system with this integrated approach, we have developed a 3-layer, multi-disciplinary BITAM-SOA service engineering schematic. The schematic also serves as a process model for service design and management. This schematic is rooted in the resource-based view theory perspective: business value can be created by IT-enhanced capabilities that can dynamically integrate resources. The strategic, managerial and practical implications of this schematic on service oriented implementations are exemplified and discussed.

Information technology workforce skills: The software and IT services provider perspective

Abstract: It is now commonplace for an organization to turn to external firms for the provision of IT services and software. As technology advances and the business environment continues to evolve, a key challenge facing IT software and service providers is identifying critical skill sets, both today and in the future. The challenge is compounded as a result of the continuing growth of outsourcing and the increasing demand for technology solutions. This paper explores that challenge through a survey of IT software and service providers. We extend and complement previous studies of non-IT firms by comparing skills sought by non-IT organizations with those of IT services and software providers. Results indicate that, surprisingly, software and services providers place more emphasis on business domain and project management skills than on technical skills. This has implications for the hiring and retention practices of managers, and for academic curriculum and course offerings.

Resource Calculations with Constraints, and Placement of Tenants and Instances for Multi-tenant SaaS Applications

Abstract: Cost of customization, deployment and operation of a software application supporting multiple tenants can be lowered through multi-tenancy in a new application business model called Software as a Service (SaaS) However, there are a number of technical challenges that need to be tackled before these benefits can be realized These challenges include calculations of resource requirements for multi-tenants with applied constraints in a shared application instance, the optimal placement of tenants and instances with maximum cost savings but without violating any requirements of service level agreements for all tenants in a set of servers Moreover, previously reported capacity planning and resource allocation methods and tools are not tenant aware This paper will address and provide novel solutions to these challenges We also describe the first of a kind, a multi-tenant placement tool for application deployment in a distributed computing environment

Management of composite software services

Abstract: A computer implemented method, data processing system, computer usable program code, and active repository are provided for management of a software service. A request is received to deploy the software service in a computer network. A dependency analysis is performed for the requested software service to determine component software services and physical resources necessary to deploy and manage new software service as a composite in responsive to the software service being the new software service. An active object is created to manage the new software service using an active template based on the analysis. The new software service is deployed in the computer network using the active object. The new software service is managed using the active object.

Towards Provisioning the Cloud: On the Usage of Multi-Granularity Flows and Services to Realize a Unified Provisioning Infrastructure for SaaS Applications

Abstract: The automatic provisioning of applications is an important task for the success of software as a service (SaaS) providers. Different provisioning engines from different vendors and open source projects with different interfaces have been emerging lately. Additionally, infrastructure providers that provide infrastructure on demand now provide computing resources that can be integrated in a SaaS providerpsilas computing environment. In order to allow SaaS application providers to specify generic installation and maintenance flows independent from the underlying provisioning engines we propose an architecture for a generic provisioning infrastructure based on Web services and workflow technology.

Tenant life cycle management for a software as a service platform

Abstract: Managing user access to application-specific capabilities of a system includes maintaining data correlating application-specific capabilities for each of the applications of the system, where the application-specific capabilities of different applications are independent of each other. Managing user access also includes maintaining data correlating user identifiers with user roles, maintaining data correlating user roles with application-specific capabilities, and managing the data using a security module that accesses the data correlating application-specific capabilities, data correlating user identifiers, and the data correlating user roles. The system may have a plurality of tenants and wherein each of the tenants subscribes to one or more of the applications. Each of the users may correspond to a particular one of the tenants. Each tenant may subscribe to a particular set of applications/features.

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

Abstract: 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.

AlfredO: an architecture for flexible interaction with electronic devices

Abstract: Mobile phones are rapidly becoming the universal access point for computing, communication, and digital infrastructures. In this paper we explore the software architectures necessary to make the mobile phone a truly universal access point to any electronic infrastructure. We propose AlfredO, a lightweight middleware architecture that allows developers to construct applications in a modular way, organizing the applications into detachable tiers that can be distributed at will to dynamically configure multi-tier architectures between mobile phones and service providers. Through AlfredO, a phone can lease on-the-fly the client side of an application and immediately become a fully tailored client. Our experimental results indicate that AlfredO has very little overhead, it is scalable, and yields very low latency. To demonstrate the feasibility and potential of the platform, in the paper we also describe AlfredOShop, a prototype application for spontaneously controlling information screens from a mobile phone.

The software fabric for the internet of things

Abstract: One of the most important challenges that need to be solved before the "Internet of Things" becomes a reality is the lack of a scalable model to develop and deploy applications atop such a heterogeneous collection of ubiquitous devices. In practice, families of hardware devices or of software platforms have intrinsic characteristics that make it very cumbersome to write applications where arbitrary devices and platforms interact. In this paper we explore constructing the software fabric for the "Internet of Things" as an extension of the ideas already in use for modular software development. In particular, we suggest to generalize the OSGi model to turn the "Internet of Things" into a collection of loosely coupled software modules interacting through service interfaces. Since OSGi is Java-based, in the paper we describe how to use OSGi concepts in other contexts and how to turn non-Java capable devices and platforms into OSGi-like services. In doing this, the resulting software fabric looks and feels like well known development environments and hides the problems related to distribution and heterogeneity behind the better understood concept of modular software design.

System and Methods to Create a Multi-Tenancy Software as a Service Application

Abstract: A method for providing multi-tenant services includes receiving a request from a user, establishing tenancy information for the user, wherein the tenancy information is selected which corresponds to a tenant of the user from among multiple tenants, customizing the request according to the tenancy information established for the user, forwarding the request to an application that is not multi-tenant aware, receiving results of the request from the application, customizing the results according to the tenancy information established for the user and corresponding to the tenant of the user, and returning customized results to the user.

In-page installer

Abstract: A method of notifying a user about the existence of relevant software and facilitating the installation of such software using a browser. A user's interactions with the browser are monitored to determine a context for a given browsing session, and it is determined whether software relevant to the context is available. If such software is available, it is recommended to the user, and if the user wishes to install the software, the installation can be performed via the browser. The software can be recommended to the user through a variety of means, including incorporating the recommendation in a static web page, incorporating the recommendation in a dynamic web page, and delivering the recommendation as part of advertising content. The recommendation may include a link to installation scripts or the like which facilitate the installation of the software by the browser.

Application Development over Software-as-a-Service Platforms

Abstract: New web development and deployment platforms are arising; some examples of these are Apex of Salesforce.com, Google Application Engine SDK, Facebook API, and so on. These software delivery platforms (SDP) are meant to serve as the basis for the delivery of an important percentage of the software offer. In the other hand, application development over these new platforms is not a defined process. Building applications over an SDP change the way software is designed, developed and delivered. Common methods of software development should be analyzed and redefined in order to fulfill the requirements of these new ways of constructing and delivering software. This paper presents the analysis of the impact of these requirements and proposes guidelines to be applied for application development in software-as-a-service (SaaS) environments.

Situated Software: Concepts, Motivation, Technology, and the Future

Abstract: Situated software, a type of opportunistic software, is created by a small subset of users to fulfill a specific purpose. For example, business users have been creating situated software through mashups, which combine data from multiple sources on internal systems or the Internet. Situated software can change the way users access, perceive, and consume information, and can allow users to finally focus on what to do with information, rather than where to find it or how to get to it. However, situated software also has limitations. This article identifies situated software's role, provides examples of its use, traces the Internet's role in its rapid evolution, outlines areas where it is appropriate, describes its limitations, and presents enablers for adopting situated software in an enterprise.

The Myth of Open Web Services: The Rise of the Service Parks

Abstract: Issues of trust, reliability, and data heterogeneity make it unlikely that we'll have access to a set of free and heterogenous Web services and tools to combine them on the Internet anytime soon. The authors contend, instead, that "service parks" will rise and succeed in the near future as execution environments that support simplified data integration and service reliability. As service park owners establish and leverage branding of their efforts, they will likely build trust within the Web service user community. The most successful service parks will allow users and service providers other than the park owners to to be easily provide and modify services.

Sustainable design decision support system

Abstract: A software application providing system and methods for using Web Services to connect an Analysis calculator, a Recommendations engine, Social Networking, and Knowledge Management technologies in a platform for operationalizing sustainability into Product Life Cycle Management (e.g., conception, design, manufacture, service, end-of-life disposition) and Enterprise Resource Planning (ERP) (including enterprise-wide activities of manufacturing, supply change management, financials, human resources, customer relationship management, and external stakeholder engagement). A Web Service Framework integrates Life Cycle Assessment (LCA) software technology with product design, manufacturing, and distribution process design tools. A logic layer can perform sustainability estimates within a Knowledge Management System. A Web Service Framework is utilized for constructing or entering LCA models, methodologies and source data. A social software-based participation environment is integrated with sustainable product design and LCA tools and processes.

Enabling application agility: software as a service, cloud computing and dynamic languages

Abstract: The good news is that application developers are on the verge of being liberated from the tyranny of middleware. Next Generation IT will leverage a new computing platform which makes the development and deliver of applications significantly easier than it is today. This new platform consists of Cloud Computing, Software As A Service and Dynamic Languages. Cloud Computing [1] offers mainframe or better infrastructure through a small set of services delivered globally over the Internet.

Adoption, Improvement, and Disruption: Predicting the Impact of Open Source Applications in Enterprise Software Markets

Abstract: This article develops a model of open source disruption in enterprise software markets. It addresses the question: Is free and open source software (FOSS) likely to disrupt markets for commercial enterprise software? The conventional wisdom is that open source provision works best for low-level system-oriented technologies, while large, complex enterprise business applications are best served by commercial software vendors. The authors challenge the conventional wisdom by developing a two-stage model of open source disruption in enterprise software markets that emphasizes a virtuous cycle of adoption and lead-user improvement of the software. The two stages are an initial incubation stage (the I-Stage) and a subsequent snowball stage (the S-Stage). Case studies of several FOSS projects demonstrate the model’s ex post predictive value. The authors then apply the model to SugarCRM, an emerging open source CRM application, to make ex ante predictions regarding its potential to disrupt commercial CRM incumbents.

Integrated soa deployment and management system and method for software services

Abstract: A method and appertaining system provide that an integrated Service Oriented Architecture (SOA) repository stores functional and non-functional requirements and associated data and results of associated with software services across the software lifecycle, thereby permitting access at a common point or in a common way by a user to all relevant information about the software service at least during the development, testing, and run-time stages of the software service. Thus, all design documents, testing requirements and results, and run-time policies and contracts can be provided in a common location to facilitate development in the service oriented architecture.

SPIN: Service Performance Isolation Infrastructure in Multi-tenancy Environment

Abstract: The flourish of SaaS brings about a pressing requirement for Multi-tenancy to avoid dedicated installation for each tenant and benefit from reduced service delivery costs. Multi-tenancy's intention is to satisfy requests from different tenants concurrently by a single service instance over shared hosting resources. However, extensive resource sharing easily causes inter-tenant performance interference. Therefore, Performance isolation is crucial for Multi-tenancy environment to prevent the potentially bad behaviors of one tenant from adversely affecting the performance of others in an unpredictable manner and prevent the unbalanced situation where some tenants achieve very high performance at the cost of others. Current technologies fail to achieve the goals of both performance isolation and resource share. This paper proposes a Service Performance Isolation Infrastructure (SPIN) which allows extensive resource sharing on hosting systems. Once some aggressive tenants interfere with others' performance, SPIN gives anomaly report, identifies the aggressive tenants, and enables a self-adaptive moderation to remove their negative impacts on others. We have implemented SPIN prototype and demonstrate its isolation efficiency on the Trade6 benchmark which is revised to support Multi-tenancy. SPIN fits industry practice for a performance overhead less than 5%.