Conference Paper

Collaborative Software Development in Ten Years: Diversity, Tools, and Remix Culture

To read the full-text of this research, you can request a copy directly from the authors.


Over the next ten years, collaboration in software engineering will change in a number of ways and research will need to shift its focus to enable and enhance such collaboration. Specifically, we claim that software in the small will become more popular and even large software will be built by fewer people due to better tools. For large projects, research will need to address the collaboration needs of project members other than just developers, including quality assurance engineers, build engineers, architects, and operations managers. Finally, code reuse and sharing will change as a result of a growing software remix culture, leading to more loosely coupled and indirect collaboration.

No full-text available

Request Full-text Paper PDF

To read the full-text of this research,
you can request a copy directly from the authors.

... Several metaCASE tools have been developed to support the use of models defined with DSML, but most of these tools do not support collaboration [3]. Nevertheless, whenever the complexity of a problem increases, the diversity of users in groups increases as well [4]. Hence, methods and tools to facilitate the cooperative work of these users are required. ...
Requirements engineering is a social process and while working together, stakeholders develop socio-technical relationships. Socio-technical aspects such as communication and awareness were discussed in literature, but little is known with respect to their role in requirements engineering activities. Therefore, requirements-driven collaboration, particularly on the relevance of socio-technical aspects, warrants further investigation. We aim to fill this gap by conducting a systematic literature review to further the knowledge on the two aspects: communication (information exchange among members) and awareness (knowledge of others). Our review was organised to cover planning (defining objectives and search strategy), execution (study search and selection) and interpretation of the findings (results and discussions). Findings revealed more studies on communication than on awareness. Two aspects of communication covered for requirements-driven collaboration in literature are: (i) preferred communication medium, and (ii) communication patterns of teams. However, for awareness the aspects affecting awareness and vice versa were studied for requirements-driven collaboration. Further investigation indicated the interdependence of awareness and communication and that distance did not happen to affect team’s awareness. We discuss implications for software practitioners in terms of enhancing their performance by considering the role of information brokers, identifying central and emergent members etc. Researchers can strengthen the body of knowledge by providing more empirical results on interdependence of socio-technical aspects.
Conference Paper
With the rapid advances in information technology (IT) in last few decades, software development has become a high-growth industry. While the software development process is an extremely complicated, iterative, unpredictable, knowledge-intensive, as well as an expensive process, a supportive collaborative information system (CIS) is indispensible for allowing complex interdependencies among globally distributed team members. The current work studies the role of CIS qualities and their impact on Individual, Organizational, and Project success using DeLone and McLean's (D&M) Information System (IS) Success Model as the basis for developing a theoretical framework. This study adopts a Partial Least Square (PLS) approach to analyze data collected from 154 questionnaires distributed to Indian software companies. The results indicate that CIS qualities, especially service quality strongly influence individual impacts and organizational impacts and hence software project success. This paper's contribution is the research into these three success areas in relation to CIS, and particularly, organizational success, as opposed to other current work being done on project success. The current study is the first to extend the IS success model into a collaborative context. In addition, because the study was done on the Indian software industry, it provides a glimpse into an industry that has rarely been studied. We hope that the current study can improve managerial understanding of a more productive and efficient IS for working within a distributed teamwork environment.
Conference Paper
The evolution of the Web has allowed the generation of several platforms for collaborative work. One of the main contributors to these advances is the Open Source initiative, in which projects are boosted to a new level of interaction and cooperation that improves their software quality and reliability. In order to understand how the group of contributors interacts with the software under development, we propose a novel methodology that adapts Lotka-Volterra-based biological models used for host-parasite interaction. In that sense, we used the concept mutualism from social parasites. Preliminary results based on experiments on the Github collaborative platform showed that Open Source phenomena can be modeled as a mutualistic system, in terms of the evolution of the population of developers and repositories.
Conference Paper
Open Source Software (OSS) has gained high amount of popularity during the last few years. It is becoming used by public and private institutions, even companies release portions of their code to obtain feedback from the community of voluntary developers. As OSS is based on the voluntary contributions of developers, the number of participants represents one of the key elements that impact the quality of the software. In order to understand how the the population of contributors evolve over time, we propose a methodology that adapts Lotka-Volterra-based biological models used for describing host-parasite interactions. Experiments based on data from the Github collaborative platform showed that the proposed approach performs effectively in terms of providing an estimation of the population of developers for each project over time.
Conference Paper
Full-text available
The build system of a software project is responsible for transforming source code and other development artifacts into executable programs and deliverables. Similar to source code, build system specifications require maintenance to cope with newly implemented features, changes to imported Application Program Interfaces (APIs), and source code restructuring. In this paper, we mine the version histories of one proprietary and nine open source projects of di erent sizes and domain to analyze the overhead that build maintenance imposes on developers. We split our analysis into two dimensions: (1) Build Coupling, i.e., how frequently source code changes require build changes, and (2) Build Ownership, i.e., the proportion of developers responsible for build maintenance. Our results indicate that, despite the di erence in scale, the build system churn rate is comparable to that of the source code, and build changes induce more relative churn on the build system than source code changes induce on the source code. Furthermore, build maintenance yields up to a 27% overhead on source code development and a 44% overhead on test development. Up to 79% of source code developers and 89% of test code developers are significantly impacted by build maintenance, yet investment in build experts can reduce the proportion of impacted developers to 22% of source code developers and 24% of test code developers.
Conference Paper
Full-text available
Software development is undergoing a major change away from a fully closed software process towards a process that incorporates open source software in products and services. Just how significant is that change? To answer this question we need to look at the overall growth of open source as well as its growth rate. In this paper, we quantitatively analyze the growth of more than 5000 active and popular open source software projects. We show that the total amount of source code as well as the total number of open source projects is growing at an exponential rate. Previous research showed linear and quadratic growth in lines of source code of individual open source projects. Our work shows that open source is expanding into new domains and applications at an exponential rate. Full Text at Springer, may require registration or fee
Introduction Part One: Cultures (Cultures of Our Past Culture of Our Future RO, Extended RW, Revived Cultures Compared) Part Two: Economies (Two Economies: Commercial and Sharing Hybrid Economies Economy Lessons) Part Three: Enabling the Future (Reforming Law Reforming Us Conclusion)