scholarly journals A Change Recommendation Approach Using Change Patterns of a Corresponding Test File

Symmetry ◽  
2018 ◽  
Vol 10 (11) ◽  
pp. 534
Author(s):  
Jungil Kim ◽  
Eunjoo Lee
Keyword(s):  
Open Source ◽  
Software Project ◽  
Meaningful Change ◽  
Software Projects ◽  
Source File ◽  
Naming Convention ◽  
History Of ◽  
Test File ◽  
Source Test

Change recommendation improves the development speed and quality of software projects. Through change recommendation, software project developers can find the relevant source files that they must change for their modification tasks. In an existing change-recommendation approach based on the change history of source files, the reliability of the recommended change patterns for a source file is determined according to the change history of the source file. If a source file has insufficient change history to identify its change patterns or has frequently been changed with unrelated source files, the existing change-recommendation approach cannot identify meaningful change patterns for the source file. In this paper, we propose a novel change-recommendation approach to resolve the limitation of the existing change-recommendation method. The basic idea of the proposed approach is to consider the change history of a test file corresponding to a given source file. First, the proposed approach identifies the test file corresponding to a given source file by using a source–test traceability linking method based on the popular naming convention rule. Then, the change patterns of the source and test files are identified according to their change histories. Finally, a set of change recommendations is constructed using the identified change patterns. In an experiment involving six open-source projects, the accuracy of the proposed approach is evaluated. The results show that the accuracy of the proposed approach can be significantly improved from 21% to 62% compared with the existing approach.

The Impact of Project Initiators on Open Source Software Project Success

2021 ◽  
pp. 221-238
Author(s):  
Ling Wang ◽  
Jinxiao Wang
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Project Success ◽  
Software Project ◽  
Software Projects ◽  
Collective Behaviors ◽  
Collective Wisdom ◽  
Open Source Software Project ◽  
Development Costs ◽  
Collaborative Innovation

This paper focuses on studying the role of open source software project initiator in affecting the OSS project success from the perspective of individual and collective behaviors. The authors collected the data from an emerging OSS hosting platform Gitee in China. This research indicates that the success mode for open source software projects in China relies a lot on the project initiators. Project initiators not only contribute codes to aid the project directly, but also use their social capital to facilitate the project success. But no full play has been given to social network's effect on mass production and collaborative innovation. The authors suggest collaborative innovation which could lead to coherence of global collective wisdom, reduced development costs, and expanded source of innovation should be the further direction for the OSS project in emerging platforms.

scholarly journals What Is Needed for the Sustainable Success of OSS Projects: Efficiency Analysis of Commit Production Process via Git

2018 ◽  
Vol 10 (9) ◽  
pp. 3001
Author(s):  
Jaeyoon Song ◽  
Changhee Kim
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Coordination Mechanism ◽  
Software Project ◽  
Tobit Regression ◽  
Software Projects ◽  
Open Source Software Project ◽  
Regulatory Processes ◽  
Massive Number ◽  
Tobit Regression Analysis

The purpose of this study is to investigate the relative efficiency of open source software projects, and to analyze what is needed for their sustainable success. The success of open source software is known to be attributable to a massive number of contributors engaging in the development process. However, an efficient open source software project is not guaranteed simply by active participation by many; a coordination mechanism is needed to seamlessly manage the multi-party collaboration. On this basis, this study aimed to examine the internal regulatory processes based on Git and GitHub, which serve as such a mechanism, and redefine the efficiency of open source software projects to fully reflect them. For this purpose, a two-stage data envelopment analysis was used to measure the project efficiency reflecting the internal processes. Moreover, this study considered the Kruskal–Wallis test and Tobit regression analysis to examine the effects of the participation by many on an open source software project based on the newly defined efficiency. Results show that a simple increase in contributors can be poisonous in terms of the efficiency of open source software projects.

scholarly journals Identification-Method Research for Open-Source Software Ecosystems

Symmetry ◽  
2019 ◽  
Vol 11 (2) ◽  
pp. 182 ◽  
Author(s):  
Zhifang Liao ◽  
Ningwei Wang ◽  
Shengzong Liu ◽  
Yan Zhang ◽  
Hui Liu ◽  
...  
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Clustering Algorithm ◽  
Research Area ◽  
Software Project ◽  
Software Projects ◽  
Virtual Collaboration ◽  
Software Ecosystem ◽  
Software Ecosystems ◽  
Core Project

In recent years, open-source software (OSS) development has grown, with many developers around the world working on different OSS projects. A variety of open-source software ecosystems have emerged, for instance, GitHub, StackOverflow, and SourceForge. One of the most typical social-programming and code-hosting sites, GitHub, has amassed numerous open-source-software projects and developers in the same virtual collaboration platform. Since GitHub itself is a large open-source community, it hosts a collection of software projects that are developed together and coevolve. The great challenge here is how to identify the relationship between these projects, i.e., project relevance. Software-ecosystem identification is the basis of other studies in the ecosystem. Therefore, how to extract useful information in GitHub and identify software ecosystems is particularly important, and it is also a research area in symmetry. In this paper, a Topic-based Project Knowledge Metrics Framework (TPKMF) is proposed. By collecting the multisource dataset of an open-source ecosystem, project-relevance analysis of the open-source software is carried out on the basis of software-ecosystem identification. Then, we used our Spectral Clustering algorithm based on Core Project (CP-SC) to identify software-ecosystem projects and further identify software ecosystems. We verified that most software ecosystems usually contain a core software project, and most other projects are associated with it. Furthermore, we analyzed the characteristics of the ecosystem, and we also found that interactive information has greater impact on project relevance. Finally, we summarize the Topic-based Project Knowledge Metrics Framework.

Software Quality in Open Source Software Ecosystems

2011 ◽  
pp. 1496-1501
Author(s):  
Pankaj Kamthan
Keyword(s):  
Software Engineering ◽  
Open Source ◽  
Open Source Software ◽  
Research Literature ◽  
Future Research ◽  
Software Project ◽  
Window System ◽  
Mailing Lists ◽  
Engineering Practices

The steady rise of open source software (OSS) (Raymond, 1999) over the last few decades has made a noticeable impact on many sectors of society where software has a role to play. As reflected from the frequency of media articles, traffic on mailing lists, and growing research literature, OSS has garnered much support in the software community. Indeed, from the early days of GNU software, to X Window System, to Linux and its utilities, and more recently the Apache Software Project, OSS has changed the way software is developed and used. As the deployment of OSS increases, the issue of its quality with respect to its stakeholders arises. We contend that the open source community collectively bears responsibility of producing “high-quality” OSS. Lack of quality raises various risks for organizations adopting OSS (Golden, 2004). This article discusses the manifestation of quality in open source software development (OSSD) from a traditional software engineering standpoint. The organization is as follows. We first outline the background and related work necessary for the discussion that follows, and state our position. This is followed by a detailed treatment of key software engineering practices that directly or indirectly impact the quality of OSS. Next, challenges and directions for future research are outlined and, finally, concluding remarks are given.

scholarly journals A study of quality prediction for large-scale open source software projects

2021 ◽  
Vol 10 (1) ◽  
pp. 34
Author(s):  
Shinji Akatsu ◽  
Ayako Masuda ◽  
Tsuyoshi Shida ◽  
Kazuhiko Tsuda
Keyword(s):  
Decision Making ◽  
Open Source ◽  
Open Source Software ◽  
Large Scale ◽  
Quality Analysis ◽  
Quality Prediction ◽  
Software Projects ◽  
Resolution Rate ◽  
The Status

Open source software (OSS) has seen remarkable progress in recent years. Moreover, OSS usage in corporate information systems has been increasing steadily; consequently, the overall impact of OSS on the society is increasing as well. While product quality of enterprise software is assured by the provider, the deliverables of an OSS are developed by the OSS developer community; therefore, their quality is not guaranteed. Thus, the objective of this study is to build an artificial-intelligence-based quality prediction model that corporate businesses could use for decision-making to determine whether a desired OSS should be adopted. We define the quality of an OSS as “the resolution rate of issues processed by OSS developers as well as the promptness and continuity of doing so.” We selected 44 large-scale OSS projects from GitHub for our quality analysis. First, we investigated the monthly changes in the status of issue creation and resolution for each project. It was found that there are three different patterns in the increase of issue creation, and three patterns in the relationship between the increase in issue creation and that of resolution. It was confirmed that there are multiple cases of each pattern that affect the final resolution rate. Next, we investigated the correlation between the final resolution rate and that for a relevant number of months after issue creation. We deduced that the correlation coefficient even between the resolution rate in the first month and the final rate exceeded 0.5. Based on these analysis results, we conclude that the issue resolution rate in the first month once an issue is created is applicable as knowledge for knowledge-based AI systems that can be used to assist in decision-making regarding OSS adoption in business projects.

Fixing the Bugs in Software Projects from Software Repositories for Improvisation of Quality

2020 ◽  
Vol 13 (2) ◽  
pp. 184-192 ◽  
Author(s):  
Ekbal Rashid ◽  
Mohd D. Ansari
Keyword(s):  
Software Project ◽  
Software Projects ◽  
Software Repositories ◽  
Bug Fixing ◽  
Closing Rate

Background: The study of bugs that are reported and close may indicate the growth and working of a software project. It may also indicate the quality of the project. Methods: As software projects grow, the number of bugs reported generally increases each year. To maintain quality, the developers have to resolve and close these increasing numbers of bugs. Results: The present paper discusses the relations between bugs being reported and bugs being closed. It also discusses some parameters related to the study of bugs. In this paper, new parameters have been introduced that help in the improvement of quality and this is the novelty of paper. Conclusion: The research mainly covers the problem of finding the relation of collaborative growth with the quality of software. The paper also covers improvements in parameters like the rate of bug fixing. It also discusses the significance of these parameters. We have suggested a new parameter called the bug closing rate. And this can be calculated in two ways.

scholarly journals Impact of Historical Software Metric Changes in Predicting Future Maintainability Trends in Open-Source Software Development

2020 ◽  
Vol 10 (13) ◽  
pp. 4624
Author(s):  
Mitja Gradišnik ◽  
Tina Beranič ◽  
Sašo Karakatič
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Software Maintenance ◽  
Software Metrics ◽  
Prediction Models ◽  
Measurement Data ◽  
Software Project ◽  
Software Projects ◽  
Software Metric ◽  
Software Maintainability

Software maintenance is one of the key stages in the software lifecycle and it includes a variety of activities that consume the significant portion of the costs of a software project. Previous research suggest that future software maintainability can be predicted, based on various source code aspects, but most of the research focuses on the prediction based on the present state of the code and ignores its history. While taking the history into account in software maintainability prediction seems intuitive, the research empirically testing this has not been done, and is the main goal of this paper. This paper empirically evaluates the contribution of historical measurements of the Chidamber & Kemerer (C&K) software metrics to software maintainability prediction models. The main contribution of the paper is the building of the prediction models with classification and regression trees and random forest learners in iterations by adding historical measurement data extracted from previous releases gradually. The maintainability prediction models were built based on software metric measurements obtained from real-world open-source software projects. The analysis of the results show that an additional amount of historical metric measurements contributes to the maintainability prediction. Additionally, the study evaluates the contribution of individual C&K software metrics on the performance of maintainability prediction models.

scholarly journals A Negotiation Framework for Managing the Requirements Changes

2013 ◽  
Vol 13 (Special-Issue) ◽  
pp. 75-87
Author(s):  
Yirui Zhang ◽  
Ying Jin ◽  
Jianxiu Bai ◽  
Jing Zhang
Keyword(s):  
Software Engineering ◽  
Experimental Results ◽  
Software Project ◽  
Software Projects ◽  
Consistent System ◽  
Requirements Change ◽  
Key Factor ◽  
System Requirements ◽  
Requirement Changes

Abstract The consistent system requirements set is the basis of successful software projects. The requirements change is very usual in a software project, and it may cause inconsistency of the requirements set, and become the key factor that affects the quality of the requirements and the software. Aiming at the problem of requirements inconsistencies caused by the requirements change, this paper proposes a compromise-based negotiation framework to manage the requirements changes, illustrates the efficiency of the proposed method by a software engineering case, gives a contrast experiment with the current mainstream method, and finally gives a comparison with the related work and a conclusion. The experimental results show that the framework proposed in this paper is more flexible and accurate than the results of the current popular framework, so it is more suitable for the requirement changes management.

The Impact of Project Initiators on Open Source Software Project Success

2020 ◽  
Vol 12 (1) ◽  
pp. 28-43
Author(s):  
Ling Wang ◽  
Jinxiao Wang
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Project Success ◽  
Software Project ◽  
Software Projects ◽  
Collective Behaviors ◽  
Collective Wisdom ◽  
Open Source Software Project ◽  
Collaborative Innovation ◽  
The Impact

This paper focuses on studying the role of open source software project initiator in affecting the OSS project success from the perspective of individual and collective behaviors. The authors collected the data from an emerging OSS hosting platform Gitee in China. This research indicates that the success mode for open source software projects in China relies a lot on the project initiators. Project initiators not only contribute codes to aid the project directly, but also use their social capital to facilitate the project success. But no full play has been given to social network's effect on mass production and collaborative innovation. The authors suggest collaborative innovation which could lead to coherence of global collective wisdom, reduced development costs, and expanded source of innovation should be the further direction for the OSS project in emerging platforms.

Sign in / Sign up

Export Citation Format

Share Document