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.     

开放源代码软件开发的基本问题

尽管开放源代码软件运动发展得相当成功,但是普通大众总感到它不易使用。本文讨论当前开放源代码软件开发趋势中的5个基本问题,并提出可能有助于克服这些问题的解决方案。1.　用户界面设计出于某种原因,开放源代码项目在用户界面设计上有许多问题。我猜想用户界面的低质量并非是一种原因造成的。在开放源代码圈内存在一种认识,认为要在完成了真正的工作之后再去设计友好的用户界面,而不把用户界面设计当成真正的工作。然而,如果开放源代码希望真正繁荣起来,使普通大众使用其工具,他们必须承认,大多数用户可能从来不知道开放源代码人员曾为复…     

利用开源软件构建OLAP系统

在开源软件的基础上，实现应用系统的开发，已被证明是一种可靠和有效的方式。提出了一个基于开放源码软件构建联机分析处理系统的技术框架。在实际开发过程中，在遵循相关的许可证制度的前提下，通过对多个相关开源软件的源代码进行详细剖析，结合实际需求进行修改，最终成为一个完整的产品化系统，并成功地投入实际应用。     

Network ties and the success of open source software development

Prior network-based research on open source software (OSS) development has focused on the benefit of network ties and assumed all network ties play the same role. We adopt a fine-grained view of network relations to investigate the impact of network ties on the success of OSS development. Through examining the development of OSS projects hosted by SourceForge, we find that co-membership among project teams is an effective mechanism for building network ties, through which knowledge and expertise flows across projects in OSS community and, therefore, contributes to the success of OSS development. However, network ties among projects not only confer benefit, but also incur various cost, and due to the different growth patterns of cost and benefit, network ties have a diminishing return to project success. In addition, we find network ties of leader–follower type and follower–leader type are more beneficial to OSS success than other types of ties, and network ties connecting to projects of later development stages are more beneficial than those connecting to projects of earlier stages. Our study provides useful guidelines and suggestions as to how to leverage the knowledge and expertise of others for successful development of OSS projects.     

Self-organization of teams for free/libre open source software development

This paper provides empirical evidence about how free/libre open source software development teams self-organize their work, specifically, how tasks are assigned to project team members. Following a case study methodology, we examined developer interaction data from three active and successful FLOSS projects using qualitative research methods, specifically inductive content analysis, to identify the task-assignment mechanisms used by the participants. We found that ‘self-assignment’ was the most common mechanism across three FLOSS projects. This mechanism is consistent with expectations for distributed and largely volunteer teams. We conclude by discussing whether these emergent practices can be usefully transferred to mainstream practice and indicating directions for future research.     

Mission-critical development with open source software: lessons learned

Using open source software components in a mission-critical project not only can keep the project within budget but can also result in a more robust and flexible tool. When considering an open source component, prospective users should evaluate the project for several characteristics: maturity, longevity, and flexibility. For greatest benefit, the users should also build and maintain a strong working relationship with the component's developers. We compiled our experiences developing SAP into a developer's guide for those considering using open source in their mission-critical application. In addition to discussing how to evaluate open source components suitability for inclusion in a mission-critical application, the guide suggests strategies for working with open source development teams.     

Virtual organizational learning in open source software development projects

We studied virtual organizational learning in open source software (OSS) development projects. Specifically, our research focused on learning effects of OSS projects and the factors that affect the learning process. The number and percentage of resolved bugs and bug resolution time of 118 SourceForge.net OSS projects were used to measure the learning effects. Projects were characterized by project type, number and experience of developers, number of bugs, and bug resolution time. Our results provided evidence of virtual organizational learning in OSS development projects and support for several factors as determinants of performance. Team size was a significant predictor, with mid-sized project teams functioning best. Teams of three to seven developers exhibited the highest efficiency over time and teams of eight to 15 produced the lowest mean time for bug resolution. Increasing the percentage of bugs assigned to specific developers or boosting developer participation in other OSS projects also improved performance. Furthermore, project type introduced variability in project team performance.     

Managing license compliance in free and open source software development

License compliance in Free and Open Source Software development is a significant issue today and organizations using free and open source software are predominately focusing on this issue. The non-compliance to licenses in free and open source software development leads to the loss of reputation and the high costs of litigation for organizations. Towards an automated compliance management, we use the Open Digital Rights Language to implement the clauses of open source software licenses in a machine interpretable way and propose a novel algorithm that analyzes compatibility between free and open source software licenses. Also, we describe a framework that inductively manages compliance of license clauses in a free and open source software development. We simulate and evaluate the formalized license compliance management by analyzing a real-time open source software project GRASS.     

化学信息学与开源软件

化学信息学研究需要性能强大而又能随时修订的、开放性的软件工具。通过回顾自由软件到开源软件的发展历史,展示开源式程序开发的丰富成就,包括操作系统如Linux、社区如SourceForge和我国的共创软件联盟等,澄清与copyright针锋相对的copyleft式版权概念,介绍并比较多种软件许可证,对开源软件的发展机制进行简要分析,认为开源软件是满足化学信息学要求的最佳选择。     

A systematic review of research on open source software in commercial software product development

Context

The popularity of the open source software development in the last decade, has brought about an increased interest from the industry on how to use open source components, participate in the open source community, build business models around this type of software development, and learn more about open source development methodologies. There is a need to understand the results of research in this area.

Objective

Since there is a need to understand conducted research, the aim of this study is to summarize the findings of research that has ben carried out on usage of open source components and development methodologies by the industry, as well as companies’ participation in the open source community.

Method

Systematic review through searches in library databases and manual identification of articles from the open source conference. The search was first carried out in May 2009 and then once again in May 2010.

Results

In 2009, 237 articles were first found, from which 19 were selected based on content and quality, and in 2010, 76 new articles were found from which four were selected. Twenty three articles were identified in total.

Conclusions

The articles could be divided into four categories: open source as part of component based software engineering, business models with open source in commercial organization, company participation in open source development communities, and usage of open source processes within a company.     

Leadership characteristics and developers’ motivation in open source software development

Open Source Software (OSS) is generally developed by interested professionals who have decided to participate in the process. The presence of effective leaders who both steer the development and motivate the developers is crucial to ensure a successful product. Using path-goal theory and built on leadership and motivation theories, we proposed and tested a model that can be used to assess the relationship between an OSS project leader's leadership style and a developer's motivation to contribute to the software development. We specifically decomposed the leadership and motivation construct to understand the hidden mechanisms by which leadership impacts motivation. A set of survey data collected from 118 OSS developers on Sourceforge.net was used to test our hypotheses. Our results indicate that leaders’ transformational leadership is positively related to developers’ intrinsic motivation and that leaders’ active management style is positively related to the developers’ extrinsic motivation.     

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.     

Reliability analysis and optimal version-updating for open source software

Context

Although reliability is a major concern of most open source projects, research on this problem has attracted attention only recently. In addition, the optimal version-dating for open source software considering its special properties is not yet discussed.

Objective

In this paper, the reliability analysis and optimal version-updating for open source software are studied.

Method

A modified non-homogeneous Poisson process model is developed for open source software reliability modeling and analysis. Based on this model, optimal version-updating for open source software is investigated as well. In the decision process, the rapid release strategy and the level of reliability are the two most important factors. However, they are essentially contradicting with each other. In order to consider these two conflicting factors simultaneously, a new decision model based on multi-attribute utility theory is proposed.

Results

Our models are tested on the real world data sets from two famous open source projects: Apache and GNOME. It is found that traditional software reliability models provide overestimations of the reliability of open source software. In addition, the proposed decision model can help management to make a rational decision on the optimal version-updating for open source software.

Conclusion

Empirical results reveal that the proposed model for open source software reliability can describe the failure process more accurately. Furthermore, it can be seen that the proposed decision model can assist management to appropriately determine the optimal version-update time for open source software.     

Simulating software development processes

One of the main factors affecting any product development schedule is rework. In the consumer product market, the risk of rework is often measured against the need to get to market quickly. This frequently happens in the software market as well; products are released with known bugs and then upgraded after user testing. Therefore, software development organizations may choose to limit the iterations of defect correction to meet schedules or control costs. The decision to release software after a certain point is a business decision, and there is little written about business decisions in any software-related literature, including the SEI's Capability Maturity Model. A quick review of software project management literature suggests that rework is implicit in software estimating techniques, but is not explicit. The amount of rework and the manner in which it is treated are very important factors in determining software schedules and cost     

Hybrid morphological methodology for software development cost estimation

In this paper we propose a hybrid methodology to design morphological-rank-linear (MRL) perceptrons in the problem of software development cost estimation (SDCE). In this methodology, we use a modified genetic algorithm (MGA) to optimize the parameters of the MRL perceptron, as well as to select an optimal input feature subset of the used databases, aiming at a higher accuracy level for SDCE problems. Besides, for each individual of MGA, a gradient steepest descent method is used to further improve the MRL perceptron parameters supplied by MGA. Finally, we conduct an experimental analysis with the proposed methodology using six well-known benchmark databases of software projects, where two relevant performance metrics and a fitness function are used to assess the performance of the proposed methodology, which is compared to classical machine learning models presented in the literature.     

敏捷方法在软件项目开发中的实践

目前很多企业内中小型软件项目面临开发时间紧迫、人手不足、需求不断变化的困难,传统重量级的软件开发方法无法应对这样的挑战.敏捷方法是基于实践的软件开发方法学,为解决这类轻量级项目管理和开发所碰到的问题提供了新的思路.通过分析敏捷方法的主要目标、观点和原则,并结合一个实际的管理信息系统项目开发,从项目计划、项目文档、重构的改进和项目维护的4个方面探讨了敏捷方法的实践应用.实践证明,采用敏捷方法的观点和原则进行必要的改进,能取得项目开发的成功.     

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.     

Using open source for a profitable startup

The viability of open source projects such as Linux and GNU is frequently questioned. This month, the author shows how the use of such software can help a small, underfunded company establish itself in the commercial software arena. It's apparent that from his perspective the viability question has been answered with a resounding yes