In this paper, we define and validate a new multidimensional measure of Open Source Software (OSS) project survivability, called Project Viability. Project viability has three dimensions: vigor, resilience, and organization. We define each of these dimensions and formulate an index called the Viability Index (VI) to combine all three dimensions. Archival data of projects hosted at SourceForge.net are used for the empirical validation of the measure. An Analysis Sample (n=136) is used to assign weights to each dimension of project viability and to determine a suitable cut-off point for VI. Cross-validation of the measure is performed on a hold-out Validation Sample (n=96). We demonstrate that project viability is a robust and valid measure of OSS project survivability that can be used to predict the failure or survival of an OSS project accurately. It is a tangible measure that can be used by organizations to compare various OSS projects and to make informed decisions regarding investment in the OSS domain.

Abstract Installation of maintenance patches in operational software systems is a source of significant expenditure and resource consumption. Managers often have to find a balance between publicly announced vulnerabilities and/or possible destabilization of existing applications, while making decisions regarding patch roll out to all systems. We propose a classification scheme for maintenance patches and examine the effects of patch category on the internal characteristics of a software system. Text mining the patch releases of 77 successive versions of the Linux operating system, we extend previous categorization schemes to maintenance patches. This granularity level offers a view of the aggregate nature of the tasks performed in each version. An unsupervised learning technique, cluster analysis associated with Text mining, reveals that there are three identifiable categories in Linux patch files. Based on the maintenance keywords in each category, we label them as:corrective,perfectiveandadaptivepatches. Further analysis of the effects of patch category on the structural complexity and the time to next release indicates that perfective patches are associated with a reduction in the complexity and frequency of patch release. Categorization at the patch level is useful for managers, since changes made to operational software systems are through patches. Determining the nature of a patch can assist managers in planning version roll out and testing criterion. Copyright © 2010 John Wiley & Sons, Ltd.