A strategic analysis for successful open source software utilization based on a structural equation model

Commercial software companies face many challenges when competing in today’s fast moving and competitive industry environment. Recently, the use of open source software (OSS) has been proposed as a possible way to address those challenges. OSS provides many benefits, including high-quality software and substantial profits. Nevertheless, OSS has not been effectively utilized in real business. The purpose of this paper is to find what affects the utilization of OSS. For this study, we propose a structural equation model (SEM) to analyze the relationships between the quality factors based on ISO/IEC 9126 and OSS utilization. In addition, we suggest an open source software utilization index (OSSUI) based on the proposed SEM. The results provide us with the controllable feedback information to improve user (programmer) satisfaction during OSS utilization.     

A critical look at open source

In recent years, open source software - more properly, free and open source software - has emerged as one popular solution to the so-called "software crisis". Advocates regard F/OSS as an agile, practice-led initiative that addresses three key issues namely cost, time scale and quality. F/OSS products are usually freely available for public download. The collaborative, parallel efforts of globally distributed developers allow many F/OSS products to be developed much more quickly than conventional software. Many F/OSS offerings are recognized for their high standards of reliability, efficiency, and robustness; products such as GNU/Linux, Apache, and Bind have become "category killers" stifling the incentive to develop any competing products.     

Comparing the relative importance of evaluation criteria in proprietary and open‐source enterprise application software selection – a conjoint study of ERP and Office systems

Until recently, organizations willing to acquire application systems have had no choice but to adopt proprietary software. With the advent of open‐source software (OSS), a new model for developing and distributing software has entered the stage. OSS has evolved from a generally horizontal infrastructure towards more highly visible applications in vertical domains, giving information systems (IS) managers more degrees of freedom in their selection of enterprise application software (EAS). Although a large body of research exists on the relative importance of evaluation criteria for proprietary EAS, the role of OSS in the EAS evaluation process has received little attention so far. To address this research gap, this study represents the first empirical investigation to compare the relative importance of evaluation criteria in proprietary and open‐source EAS selection. Through an online survey, we evaluated the responses of IS managers of 358 organizations to a conjoint study spawning 8592 trade‐off pair comparisons and 3580 purchase evaluations on proprietary and open‐source enterprise resource planning (ERP) and Office software packages. The results show that the relative importance of evaluation criteria significantly varies between proprietary and open‐source ERP systems. Implementation factors such as ease of implementation and support are much more crucial in the evaluation of open‐source than of proprietary ERP systems, which is generally due to IS managers' risk mitigation behaviour. Interestingly, there are no major differences in the ranking of evaluation criteria between proprietary and open‐source Office systems. We conclude our paper with a detailed discussion of our findings and their implications for researchers, companies, EAS vendors and open‐source communities.     

The Bazaar inside the Cathedral: Business Models for Internal Markets

Software product-line development lets organizations better optimize software development efficiency by building a shared set of assets for reuse in multiple products. This process introduces many challenges, not least of which is creating the initial set of reusable software assets. To accomplish this, organizations often establish a central software platform group. Such a group faces a serious problem: existing systems groups already have a large set of software components that they use to build their products. If companies are to successfully transition to product-line development, these systems groups must shift their investments from existing software components to the new reusable product-line assets. One way to encourage this is to create an internal open source software community that lets systems groups actively contribute their existing components to the platform. In OSS, a community works together to develop software. Because the software's users are part of the community, they can add the assets they need. Inner-source-software (ISS) development applies OSS within a limited environment that has a closed border (such as a company, a division, or a consortium). So, companies using the ISS approach essentially establish an OSS community within the confines of their organization.     

On the challenges of open-sourcing proprietary software projects

The open source software (OSS) movement has become widely recognized as an effective way to deliver software. Even big software companies, well-known for being restrictive when it comes to publishing their source code artifacts, have recently adopted open source initiatives and released for general use the source code of some of their most notable products. We conducted an exploratory study on merits of the widespread belief that open-sourcing a proprietary software project will attract external developers, like casual contributors, and therefore improve software quality (e.g., “given enough eyeballs, all bugs are shallow”). By examining the pre- and post-migration software history of eight active, popular, non-trivial proprietary projects that became open source, we characterize the phenomenon and identify some challenges. Contrary to what many believe, we found that only a few projects experienced a growth in newcomers, contributions, and popularity; furthermore, this growth does not last long. The results from the study can be useful for helping software companies to better understand the hidden challenges of open-sourcing their software projects to attract external developers.     

Empirical study of open source software selection for adoption,based on software quality characteristics

Currently, open source software (OSS) products have started to become popular in the market as an alternative to traditional proprietary or closed source software. Governments and organizations are beginning to adopt OSS on a large scale and several governmental initiatives have encouraged the use of OSS in the private sector. One major issue for the government and private sector is the selection of appropriate OSS. This paper uses new internal quality characteristics for selecting OSS that can be added to the dimensions of DeLone and McLean information systems’ model. Through this study, the quality characteristics are organized in a two level hierarchy, which list characteristics and sub-characteristics that are interconnected with three main dimensions: system quality, information quality and service quality. These characteristic dimensions are tailored to the criteria having been built from literature study and standard for software quality and guidelines. This paper presents case study results of applying the proposed quality characteristic on eight different open source software that are divided between open source network tools and learning management systems.     

Organizational adoption of open source software

Organizations and individuals can use open source software (OSS) for free, they can study its internal workings, and they can even fix it or modify it to make it suit their particular needs. These attributes make OSS an enticing technological choice for a company. Unfortunately, because most enterprises view technology as a proprietary differentiating element of their operation, little is known about the extent of OSS adoption in industry and the key drivers behind adoption decisions. In this article we examine factors and behaviors associated with the adoption of OSS and provide empirical findings through data gathered from the US Fortune-1000 companies. The data come from each company's web browsing and serving activities, gathered by sifting through more than 278 million web server log records and analyzing the results of thousands of network probes. We show that the adoption of OSS in large US companies is significant and is increasing over time through a low-churn transition, advancing from applications to platforms. Its adoption is a pragmatic decision influenced by network effects. It is likelier in larger organizations and those with many less productive employees, and is associated with IT and knowledge-intensive work and operating efficiencies.     

Users’ perception of open source usability: an empirical study

The number of open source software (OSS) users has increased in recent years. No longer are they limited to technically adept software developers. Many believe that the OSS market share could increase tremendously provided OSS had systems that were easier to use. Although examples of good usable open source software exist, it is agreed that OSS can be made more usable. This study presents an empirical investigation into the impact of some key factors on OSS usability from the end users’ point of view. The research model studies and establishes the relationship between the key usability factors from the users’ perspective and OSS usability. A data set of 102 OSS users from 13 open source projects of various sizes was used to study the research model. The results of this study provide empirical evidence by indicating that the highlighted key factors play a significant role in improving OSS usability.     

Should You Adopt Open Source Software?

Many organizations use open source infrastructure software such as Linux, and open source software (OSS) is generally considered a viable technology. Both professional and academic literature devote much attention to the OSS phenomenon. However, decision makers considering the adoption of OSS face a plethora of books, research papers, and articles highlighting OSS's advantages and disadvantages. Different articles attach different levels of importance to these advantages or factors related to the adoption decision. Reasons for adopting OSS vary from the pragmatic. Organizations must consider the advantages and disadvantages of open source software before adopting it.     

Using open source software in product development: a primer

There are important legal aspects involved in using open source software in commercial products. Here are answers to common questions on how to handle these issues to mitigate risk. The use of open source software in industrial products is growing rapidly because its many advantages are well known. However although we in industry understand liability and intellectual-property-right risks fairly well, the implication of OSS-related legal and managerial issues are new to many of us. Legal aspects can vary greatly from one piece of OSS to another depending on the license scheme used. We discuss the major legal aspects and risks in using OSS and how to mitigate them in product development. We've ordered the information in a top-down approach, starting with a definition of OSS, its benefits, and then some risks and experiences with managing it in software engineering practice.     

Beyond free software: An exploration of the business value of strategic open source

The phenomenon of open source software (OSS) has been well studied from the software development perspective, but it has received much less attention from the perspective of business value. Nevertheless, OSS, when viewed as a value creation process rather than ‘free’ software, provides businesses with value through access to knowledge and innovation capacity resident in online communities. This conceptualisation, which we label ‘strategic open source’ requires firms to rethink their strategy and processes as there is a shift in focus from ownership to openness and collaboration with external parties. Nonetheless, the emergence of OSS poses a puzzle for conceptions of organisational theory. Therefore, a theorising process is needed in order to develop a deeper understanding of how value is created and captured with OSS. Using a field study of eleven European firms, this paper explores the creation and capture of business value from strategic open source. The findings reveal that while decision makers look to open innovation initiatives like OSS for value creation and capture, there is still a desire to remain self reliant, resulting in collaborative design (of external innovations) rather than collaborative decision making with value network partners in relation to how such innovations would help create and capture value within firms.     

A framework for creating hybrid-open source software communities

Abstract The open source software (OSS) model is a fundamentally new and revolutionary way to develop software. The success of the OSS model is also setting the stage for a structural change in the software industry; it is beginning to transform software industry from manufacturing to a service industry. Despite the success of the OSS model, for‐profit organizations are having difficulty building a business model around the open source paradigm. Whereas there are some isolated empirical studies, little rigorous research has been done on how traditional organizations can implement and benefit from OSS practices. This research explores how organizations can foster an environment similar to OSS to manage their software development efforts to reap its numerous advantages. Drawing on organizational theory, we develop a framework that guides the creation and management of a hybrid‐OSS community within an organization. We discuss the implications of this framework and suggest areas for future research.     

Open source software licenses: Strong-copyleft, non-copyleft, or somewhere in between?

Studies on open source software (OSS) have shown that the license under which an OSS is released has an impact on the success or failure of the software. In this paper, we model the relationship between an OSS developer's utility, the effort that goes into developing an OSS, his attitude towards the freedom to choose an OSS license, and the choice of OSS license. We find that the larger the effort to develop OSS, the more is the likelihood that the OSS license would be free from restrictions. Interestingly, the result holds even when all OSS developers prefer restrictive licenses or less-restrictive license. The results suggest that least-restrictive or non-copyleft license will dominate other types of OSS license when a large effort is required to develop derivative software. On the other hand, most-restrictive or strong-copyleft licenses will be the dominant license when minimal effort is required to develop the original OSS and the derivative software.     

Volunteers’ involvement in online community based software development

We sought to gain understanding of voluntary developers’ involvement in open source software (OSS) projects. Data were collected from voluntary developers working on open source projects. Our findings indicated that a voluntary developer's involvement was very important to his or her performance and that involvement was dependent on individual motivations (personal software needs, reputation and skills gaining expectation, enjoyment in open source coding) and project community factors (leadership effectiveness, interpersonal relationship, community ideology). Our work contributes theoretically and empirically to the body of OSS research and has practical implications for OSS project management.     

An open source usability maturity model (OS-UMM)

User satisfaction has always been a major factor in the success of software, regardless of whether it is closed proprietary or open source software (OSS). In open source projects, usability aspects cannot be improved unless there are ways to test and measure them. Hence, the increasing popularity of open source projects among novice and non-technical users necessitates a usability evaluation methodology. Consequently, this paper presents a usability maturity model specifically aimed at usability-related issues for open source projects. In particular, the model examines the degree of coordination between open source projects and their usability aspects. The measuring instrument of the model contains factors that have been selected from four of our empirical studies, which examine the perspectives of OSS users, developers, contributors and the industry. In addition to presenting the usability maturity model, this paper discusses assessment questionnaires, a rating methodology and two case studies.     

User acceptance model of open source software

The development and implementation of open source software (OSS) is one of the most current topics within the academic, business and political environments. Traditionally, research in OSS has focused on identifying individual personal motives for participating in the development of an OSS project, analyzing specific OSS solutions, or the OSS movement, itself. Nevertheless, user acceptance towards this type of technology has received very little attention. For this reason, the main purpose of the current study is to identify the variables and factors that have a direct effect on individual attitude towards OSS adoption. Therefore, we have developed a technological acceptance model on behalf of the users towards a solution based on OSS. For this development, we have considered the technology acceptance model. Findings show that OSS is a viable solution for information management for organizations.     

Understanding OSS development in communities: the perspectives of ideology and knowledge sharing

This study aims to understand why open source software (OSS) developers contribute and how their dispersed efforts are controlled to lead to viable outputs. Drawing on theories related to ideology and information sharing, a model is proposed and tested empirically. We found that OSS values are positively associated with collaborative elaboration and communication competence, which in turn affect the performance of OSS task in terms of task completion. Our results also delineate the relationship among OSS norms, collaborative elaboration and source credibility, and task completion. This research contributes to advancing theoretical understanding of OSS performance as well as providing OSS practitioners with guidelines on how OSS communities use OSS ideology to achieve better performance.     

Exploring value networks: theorising the creation and capture of value with open source software

The emergence of open source software (OSS) as a form of peer production and innovation challenges theories of organisation and strategy due to its non-reliance on traditional governance mechanisms to organise production. OSS requires firms to rethink the processes that facilitate value creation and capture. The objective of this paper is to theorise how firms create and capture value from OSS. We derive a model from extant research and refine it through the study of three inter-organisational networks. The findings reveal how a firm's ability to access a value network of complementors is crucial for effective value creation and capture. Two types of networks are evident: a high-density network of familiar partners and a low-density network of multiple, often unfamiliar, partners. Leveraging these networks depends on the level of commitment, volume of knowledge exchange and the alignment of objectives among participant firms. Effective governance is revealed as critical for creating and capturing value within both types of network; and depends on both formal and informal mechanisms.     

Achieving Quality in Open-Source Software

The open source software community has published a substantial body of research on OSS quality. Focusing on this peer-reviewed body of work lets us draw conclusions from empirical data rather than rely on the large volume of evangelical opinion that has historically dominated this field. This body of published research has become much more critical and objective in its efforts to understand OSS development, and a consensus has emerged on the key components of high-quality OSS delivery. This article reviews this body of research and draws out lessons learned, investigating how the approaches used to deliver high-quality OSS differ from, and can be incorporated into, closed-source software development     

Antecedents of open source software defects: A data mining approach to model formulation, validation and testing

This paper develops tests and validates a model for the antecedents of open source software (OSS) defects, using Data and Text Mining. The public archives of OSS projects are used to access historical data on over 5,000 active and mature OSS projects. Using domain knowledge and exploratory analysis, a wide range of variables is identified from the process, product, resource, and end-user characteristics of a project to ensure that the model is robust and considers all aspects of the system. Multiple Data Mining techniques are used to refine the model and data is enriched by the use of Text Mining for knowledge discovery from qualitative information. The study demonstrates the suitability of Data Mining and Text Mining for model building. Results indicate that project type, end-user activity, process quality, team size and project popularity have a significant impact on the defect density of operational OSS projects. Since many organizations, both for profit and not for profit, are beginning to use Open Source Software as an economic alternative to commercial software, these results can be used in the process of deciding what software can be reasonably maintained by an organization.