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

What Is Web 2.0: Design Patterns and Business Models for the Next Generation of Software

Abstract: This paper was the first initiative to try to define Web2.0 and understand its implications for the next generation of software, looking at both design patterns and business modes. Web 2.0 is the network as platform, spanning all connected devices; Web 2.0 applications are those that make the most of the intrinsic advantages of that platform: delivering software as a continually-updated service that gets better the more people use it, consuming and remixing data from multiple sources, including individual users, while providing their own data and services in a form that allows remixing by others, creating network effects through an "architecture of participation," and going beyond the page metaphor of Web 1.0 to deliver rich user experiences.

What Is Web 2.0: Design Patterns and Business Models for the Next Generation of Software

Abstract: This paper was the first initiative to try to define Web2.0 and understand its implications for the next generation of software, looking at both design patterns and business modes. Web 2.0 is the network as platform, spanning all connected devices; Web 2.0 applications are those that make the most of the intrinsic advantages of that platform: delivering software as a continually-updated service that gets better the more people use it, consuming and remixing data from multiple sources, including individual users, while providing their own data and services in a form that allows remixing by others, creating network effects through an "architecture of participation," and going beyond the page metaphor of Web 1.0 to deliver rich user experiences.

Collaboration in Software Engineering: A Roadmap

Abstract: Software engineering projects are inherently cooperative, requiring many software engineers to coordinate their efforts to produce a large software system. Integral to this effort is developing shared understanding surrounding multiple artifacts, each artifact embodying its own model, over the entire development process. This focus on model- oriented collaboration embedded within a larger process is what distinguishes collaboration research in software engineering from broader collaboration research, which tends to address artifact-neutral coordination technologies and toolkits. This article first presents a list of goals for software engineering collaboration, then surveys existing collaboration support tools in software engineering. The survey covers both tools that focus on a single artifact or stage in the development process (requirements support tools, UML collaboration tools), and tools that support the representation and execution of an entire software process. Important collaboration standards are also described. Several possible future directions for collaboration in software engineering are presented, including tight integration between web and desktop development environments, broader participation by customers and end users in the entire development process, capturing argumentation surrounding design rationale, and use of massively multiplayer online (MMO) game technology as a collaboration medium. The article concludes by noting a problem in performing research on collaborative systems, that of assessing how well certain artifacts, models, and embedded processes work, and whether they are better than other approaches.

Comparison of Software Quality Under Perpetual Licensing and Software as a Service

Abstract: Software is available through a number of different licensing models such as the commonly used perpetual licensing model and a relatively new licensing model called software as a service (SaaS). There are several differences between SaaS and perpetual licensing. SaaS licensing offers software using a subscription model, whereas perpetual licensing involves a one-time payment for a perpetual use license and optional additional payments for future upgrades. Prior literature has not considered the impact of these licensing schemes on the publisher's incentive to invest in software quality. We model differences in how new software features are disseminated in SaaS and perpetual licensing. We show that these differences affect the publisher's incentive to invest in product development. We find that the SaaS licensing model leads to greater investment in product development under most conditions. This increased investment leads to higher software quality in equilibrium under SaaS as compared to perpetual licensing. The software publisher earns greater profits and social welfare is higher under SaaS under these conditions.

Software as a Service: Implications for Investment in Software Development

Abstract: Software as a service (SaaS) is a rapidly growing model of software licensing. In contrast to traditional software where users buy a perpetual-use license, SaaS users buy a subscription from the publisher. Whereas traditional software publishers typically release new product features as part of new versions of software once in a few years, publishers using SaaS have an incentive to release new features as soon as they are completed. We show that this property of the SaaS licensing model leads to greater investment in product development under most conditions. This increased investment leads to higher software quality in equilibrium under SaaS compared to perpetual licensing. The software publisher earns greater profits under SaaS while social welfare is also higher

The governance of open source initiatives: what does it mean to be community managed?

Abstract: The concept of ‘open source’ software initially referred to software projects managed by grassroots communities in public forums. Since 1998, the concept has been adapted and diffused to new settings that extend beyond software. While the open source community has maintained control over which software licenses can be considered ‘open source’, little attention has been paid to the elements that constitute community management. More private parties now contribute to OSS communities and more hybrid governance models have emerged. Before we can understand how hybrid models differ from a community managed model, a more precise definition is needed. This essay takes a step in this direction by identifying five core principles critical to community-managed governance.

Software as a Service: An Integration Perspective

Abstract: Software as a Service (SaaS) is gaining momentum in recent years with more and more successful adoptions. Though SaaS is delivered over Internet and charged on per-use basis, it is software application in essence. SaaS contains business data and logics which are usually required to integrate with other applications deployed by a SaaS subscriber. This makes Integration become one of the common requirements in most SaaS adoptions. In this paper, we analyze the key functional and non-functional SaaS integration requirements from an industry practitioner point of view; and summarize the SaaS integration patterns and existing offerings; then point out the gaps from both technology and tooling perspectives; finally we introduce a SaaS integration framework to address those gaps. Considering there is no much academic work on SaaS service modeling, we come up with a SaaS service description framework as an extension of Web Service description, so as to model SaaS unique features in a unified way. With the supported tooling and runtime platform, the framework can facilitate the SaaS integration lifecycle in a model-driven approach.

Pattern Oriented Software Architecture: Patterns for Resource Management

Abstract: This tutorial uses design patterns to present techniques for implementing effective and efficient resource management in a system. The tutorial is based on the third volume of the POSA (pattern-oriented software architecture) series. The tutorial presents a thorough introduction to resource management along with two case studies in which the patterns are applied to the domains of ad hoc networking and mobile radio networks. The presented patterns are independent of any implementation technique, such as .NET, Java or C++, even though the examples are given in Java and C++. The patterns are grouped by different areas of resource management and address the complete lifecycle of resources: acquisition, management, and release.

The Business Model of "Software-As-A-Service"

Abstract: The emergence of the software-as-a-service (SaaS) business model has attracted great attentions from both researchers and practitioners. SaaS vendors deliver on-demand information processing services to users, and thus offer computing utility rather than the standalone software itself. In this work, the author propose an analytical model to study the competition between the SaaS and the traditional COTS (commercial off-the-shelf) solutions for software applications. The author show that when software applications become open, modulated, and standardized, the SaaS business model will take a significant market share. In addition, under certain market conditions, offering users an easy exit option through the software contract will help to increase the SaaS vendors' competitive ability.

Social Software in Libraries: Building Collaboration, Communication, and Community Online

Abstract: Here is the first book to explore the growing phenomenon of social software and how these technologies can be applied in libraries. Social software lets libraries show a human face online, helping them communicate, educate, and interact with their communities. This nuts-and-bolts guide provides librarians with the information and skills necessary to implement the most popular and effective social software technologies: blogs, RSS, wikis, social networking software, screencasting, photo-sharing, podcasting, instant messaging, gaming, and more. Success stories and interviews highlight these tools ease-of-use and tremendous impact. Novice readers will find ample descriptions and advice on using each technology, while veteran users of social software will discover new applications and approaches. Supported by the author s Web page.

What Is Web 2.0: Design Patterns and Business Models for the Next Generation of Software

Abstract: This paper was the first initiative to try to define Web2.0 and understand its implications for the next generation of software, looking at both design patterns and business modes. Web 2.0 is the network as platform, spanning all connected devices; Web 2.0 applications are those that make the most of the intrinsic advantages of that platform: delivering software as a continually-updated service that gets better the more people use it, consuming and remixing data from multiple sources, including individual users, while providing their own data and services in a form that allows remixing by others, creating network effects through an "architecture of participation," and going beyond the page metaphor of Web 1.0 to deliver rich user experiences.

A Strategic Analysis of Competition Between Open Source and Proprietary Software

Abstract: This paper analyzes a software market consisting of a freely available open source software (OSS), the commercial version of this OSS (OSS-SS), and the competing commercial proprietary software (PS). We find that in software markets characterized by low direct network benefits, the PS vendor is better off in the presence of competition from OSS-SS. Furthermore, the OSS-SS vendor in these markets is better off by having lower usability than PS. Therefore, the PS vendor has little incentive to improve the usability of their software in these markets. On the other hand, in software markets characterized by high network benefits, a PS vendor is threatened by the presence of OSS-SS and can survive only if the PS is more usable than the competing OSS-SS.

Method and system for providing wireless vulnerability management for local area computer networks

Abstract: A Software-as-a-Service (SaaS) based method for providing wireless vulnerability management for local area computer networks The method includes providing a security server being hosted by a service provider entity to provide analysis of data associated with wireless vulnerability management for a plurality of local area computer networks of a plurality of customer entities, respectively The method includes creating a workspace for wireless vulnerability management for a customer entity on the security server and receiving configuration information associated with the workspace The method also includes supplying one or more sniffers to the customer entity The method includes receiving at the security server information associated with wireless activity monitored by the one or more sniffers at premises of the customer entity and processing the received information within the workspace for the customer entity using the security server The method includes metering usage of the workspace for wireless vulnerability management for the customer entity

A stakeholder-driven service life cycle model for SOA

Abstract: Service-orientation is a relatively new paradigm aiming at developing software systems that are adaptive and dynamic. Service-oriented systems are developed by composing services that are shared across organizations. Because new roles and new development tasks are introduced in service-oriented development as opposed to traditional software engineering, a new approach to service life cycle management is required. In this paper, based on the observations of the state of the art in the field, we propose a stakeholder-driven service life cycle model for service oriented architecture (SOA). Horizontally, the model shows the activities that associated with the stakeholders in SOA. While vertically, the model shows the interactions and cooperation between the stakeholders. This model facilitates the researchers to gain further insight into service-oriented development and governance.

Software distribution via peer-to-peer networks

Abstract: Providing a software distribution service via ad hoc peer-to-peer networks involves configuring a first device (106) to offer a peer-to-peer software distribution service (130) that facilitates access to a plurality of programs (314, 334, 344, 360). The peer-to-peer software distribution service (130) is advertised via the first device (106) using a service discovery protocol of an ad hoc peer-to-peer network (104). At least one query (134, 320) for a description of the peer-to-peer software distribution service • (130) from a target device (106) of the ad hoc peer-to-peer network is received at the first device (106) in response to advertising the peer-to-peer software distribution service (130). Downloading (136, 140) of a program to the target device (106) is facilitated via the peer-to-peer software distribution service (130). The program is selected from the plurality of programs (314, 334, 344, 360) and capable of operating on a processor of the target device (106).

Method and apparatus for providing authentication and encryption services by a software as a service platform

Abstract: An extensible servicing hosting platform is provided that supports the design, build and concurrent deployment of multiple web accessible services on a services hosting platform. The services hosting platform comprises a services hosting framework capable of hosting multiple service applications, each of which may be shared by multiple tenants that each customize their use of a particular application service by extending the application service to exploit run time platform services within a service execution pipeline. The services hosting framework may easily be leveraged by applications to decrease the time associated with developing, deploying and maintaining high quality services in a cost effective manner.

Device-based software authorizations for software asset management

Abstract: Software device groups allow owners and administrators to be defined for various intelligent devices, instead of tracking by primary user. A software license compliance management system obtains discovery information for these devices to determine software installed or active on these devices. The management system also obtains the number of licenses for each software package and determines whether the software is in compliance, or if the number of instances exceeds the number of licenses. This determination is flexible and can handle various license types, such as per user, per device, and per processor. For any exception, the group owner is informed and then can re-allocate licenses, purchase additional licenses, or request the uninstalling of a software instance(s). Device groups also can include sub-groups with sub-group owners responsible for handling any exception in that sub-group.

On-demand software service system and method

Abstract: An on-demand software and service access system has a remote processing system or remote service provider accessible via the Internet or other network, and a local system which runs on a user's local device. The remote system has a plurality of different software applications, operating systems, and central data storage means for selective access by authorized users from their local computer via a network or the Internet, as well as a profile manager for providing user registration, user login, and loading of user selected settings and services onto the local system. Usage of the selected software applications is provided on a subscription basis for applications required by users on a daily basis, as well as on a one-time purchase basis, for one time use, for use only for a specific time period, or permanently.

Systems and methods for integrating services

Abstract: Methods and apparatus, including computer program products, are provided for executing a service using a set of software plug-ins. The method may include generating, at a first computer, a service request to execute the service. The method may also include processing, at a second computer, the generated service request using the set of software plug-ins associated with the service to create a modified service request by executing each of the software plug-ins in a sequence. further, the method may include executing, at a third .computer, the service using the modified service request and processing, by a second set of software plug-ins based on the sequence, a result from the executing step.

Towards a Methodology for Service Construction

Abstract: All large vendors of standard business software have announced to move to service oriented architecture. They claim benefits for their customers with regard to agility and openness. In contrast to the design of software services which has been a focus of research in the computer science community in recent years, the design of enterprise services has not been addressed as much by the information systems research community. This paper outlines a research program on the design of enterprise services. The necessity of different service understandings on different layers of enterprise architecture is shown, conceptual foundations for the design of enterprise services are presented, and first results of developing a method for enterprise service design are proposed

An ITIL-based IT Service Management Model for Chinese Universities

Abstract: Considering the exigency of establishing an IT service management model that accords with the characteristics of universities, this paper has developed the organization model, the process model and the technology model of campus IT service management based on the ITIL theory and the realities of Chinese universities.

Analysis of a new information systems outsourcing practice: software-as-a-service business model

Abstract: Software-as-a-Service (SaaS) is an emerging business model that delivers software applications to users through web-based technology. Adopting SaaS applications allow companies to dramatically save their Information Technology (IT) costs. This paper discusses the concepts and applications of services, SaaS, outsourcing and their economic implications. SaaS can be adopted as an excellent outsourcing model since it exhibits the technological and economic benefits of IT services.

Service componentization and composition architecture

Abstract: An architecture for componentizing portions of a collaborative or software as a service (SaaS) environment is provided such that users and/or developers leveraging such environments need not initialize and load the entire environment. Rather services are discovered and selectable so applications can be implemented to utilize a portion of the environment where another portion is not required for the access desired. Similarly, thinner versions of a collaborative or SaaS environments can be implemented to provide easy and efficient access to a portion of the service such that processing power and other burdens are removed from the collaboration or SaaS server and respective clients.

Non-intrusive asset monitoring framework for runtime configuration of deployable software assets

Abstract: The present invention discloses a solution for metering, monitoring, and monetizing software assets. The solution can include a step of registering a software asset with a monitoring service. A unique identifying key for the software asset can be generated during registration. The software asset can then be instrumented for the monitoring service. The instrumentation can reference the software asset by the unique key. Specifics of the set of metrics that are to be monitored by the monitoring service for the software asset can be runtime, development time, and/or deployment time configurable. The instrumented software asset can convey transaction data to the monitoring server when used by clients. Analyzed results produced by the monitoring service pertaining to the software assets based upon the transaction data can be provided to authorize users of vendors associated with the software asset.

DrProject: a software project management portal to meet educational needs

Abstract: DrProject is a web-based software project management portal that integrates revision control, issue tracking, mailing lists, a wiki, and other features Unlike other such systems, DrProject is specifically tailored to the needs of undergraduate teaching and team programming assignments We describe the pedagogical motivations for DrProject and our experiences with it to date

Healthcare core measure tracking software and database

Abstract: Software and a system created by the software with its application are applied in the healthcare setting for various patients corresponding to guideline-recommended treatments. The system provides real-time guidance to care providers regarding guideline-recommended care, educational resources, and their performance, as well as hospital benchmarking. The software allows real-time data entry at the bedside, -during patient care processes, from admission to discharge. The software captures necessary patient data related to guideline compliance initiatives of government authorities, private payors or other organizations, plus report safety events. The software can be used on a variety of hardware devices, and may gather data from various hospital information systems.

Method for Providing a Web-based Payroll and Payroll Related Software as a Service

Abstract: A method for providing payroll processing software as a service to payroll providers such as payroll vendors and end users. The software developer contracts with the payroll provider to provision, administer and support the payroll processing software thereby allowing the payroll provider to concentrate on its core business of payroll processing.

Virtualization-based techniques for enabling multi-tenant management tools

Abstract: As service providers strive to improve the quality and efficiency of their IT (information technology) management services, the need to adopt a standard set of tools and processes becomes increasingly important. Deploying multitenant capable tools is a key part of this standardization, since a single instance can be used to manage multiple customer environments, and multi-tenant tools have the potential to significantly reduce service-delivery costs. However, most tools are not designed for multi-tenancy, and providing this support requires extensive re-design and re-implementation. In this paper, we explore the use of virtualization technology to enable multi-tenancy for systems and network management tools with minimal, if any, changes to the tool software. We demonstrate our design techniques by creating a multi-tenant version of a widely-used open source network management system. We perform a number of detailed profiling experiments to measure the resource requirements in the virtual environments, and also compare the scalability of two multi-tenant realizations using different virtualization approaches. We show that our design can support roughly 20 customers with a single tool instance, and leads to a scalability increase of 60-90% over a traditional design in which each customer is assigned to a single virtual machine.

Providing support for multiple interface access to software services

Abstract: Techniques are described for providing enhanced access to software services or other software programs that provide interfaces for use by clients. The enhanced access may, for example, be provided for a software service having multiple distinct versions with distinct corresponding interfaces, such as if some clients continue to initiate access to older versions of the software service using corresponding older interfaces, while other clients initiate access to a current software service version using a corresponding current interface version. The enhanced access techniques may further include automatically adapting requests that correspond to older interface versions of a software service so that the adapted requests correspond to the current interface version for the software service, and responses may similarly be adapted from a format for a current version of a software service to a format for a prior interface version used by the request that resulted in the response.

The Impact of Service-Oriented Application Development on Software Development Methodology

Abstract: Web services technology has become a key technology for system integration and the implementation of service-oriented architectures. However, many organizations are still facing challenges implementing Web services-based applications on a larger scale. The lack of an accepted and reliable framework for the implementation of Web services has been identified, among other issues, as one important challenge. The underlying assumption is that Web services-based implementations entail substantial changes in how applications are developed. The study presented in this paper examines the impact of Web services on the software development process. The current results of this research provide insights into the characteristics of software development based on Web services. The outcomes of this research are intended to contribute to a framework for guiding software methodology choices and adjustments in the context of Web services