Forking and coordination in multi-platform development

Duc, Anh Nguyen; Mockus, Audris; Hackbarth, Randy; Palframan, John

doi:10.1145/2652524.2652546

Cited by 16 publications

(7 citation statements)

References 26 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Researchers have recognized awareness as an essential success factor of collaborative software development. For example, the investigation of Duc et al (2014) on multi-platform development practices showed that diverged code bases frequently lead to redundant development. Our approach can be used to develop an understanding of changes at the level of features in distributed development.…”

Section: Related Workmentioning

confidence: 99%

Feature-oriented clone and pull operations for distributed development and evolution

et al. 2022

View full text Add to dashboard Cite

Software companies frequently customize and extend product lines in multiple projects concurrently to quickly deliver solutions to customers. Engineers use a distributed and feature-oriented development process, commonly supported by version control systems to track implementation-level changes. For instance, feature branches are widely used to add new or modify existing features. However, when merging back features to the product line, the information about feature-to-code mappings is usually lost. Furthermore, the granularity of merging is limited to branches, making it hard to extract and merge selected individual features from one product to another. This paper thus presents feature-oriented clone and pull operations for distributed development, which are implemented in the FORCE2 platform. Our evaluation uses variants of the ArgoUML product line to investigate the correctness and performance of our approach. The results show that the feature-oriented operations work with high precision and recall for different cases of feature interactions, also when feature implementations are scattered across many locations in the source code. The performance measurements demonstrate that the operations can be integrated in the typical workflows of engineers.

show abstract

Section: Related Workmentioning

confidence: 99%

Feature-oriented clone and pull operations for distributed development and evolution

et al. 2022

View full text Add to dashboard Cite

show abstract

“…Evaluation metrics are used extensively in empirical study about data mining, software quality predictions and software metrics. We adopted the set of evaluation metrics in our previous work [37,38]. These metrics are also successfully adopted in studies about security before [13,20] It is possible to have both TP and FP in a test file.…”

Section: Evaluation Metricsmentioning

confidence: 99%

On the Combination of Static Analysis for Software Security Assessment – A Case Study of an Open-Source e-Government Project

Nguyen-Duc¹,

Do²,

Luong-Hong³

et al. 2021

Adv. sci. technol. eng. syst. j.

View full text Add to dashboard Cite

Static Application Security Testing (SAST) is a popular quality assurance technique in software engineering. However, integrating SAST tools into industry-level product development and security assessment poses various technical and managerial challenges. In this work, we reported a longitudinal case study of adopting SAST as a part of a humandriven security assessment for an open-source e-government project. We described how SASTs are selected, evaluated, and combined into a novel approach for software security assessment. The approach was preliminarily evaluated using semi-structured interviews. Our result shows that (1) while some SAST tools out-perform others, it is possible to achieve better performance by combining more than one SAST tools and (2) SAST tools should be used towards a practical performance and in the combination with triangulated approaches for human-driven vulnerability assessment in real-world projects.

show abstract

“…The Android software chosen for this study is a fork of the Spark codebase. A more in-depth description of the development process is provided in [17].…”

Section: Software Descriptionmentioning

confidence: 99%

Deriving a usage-independent software quality metric

Dey¹,

Mockus²

2020

Empir Software Eng

Self Cite

View full text Add to dashboard Cite

Context: The extent of post-release use of software affects the number of faults, thus biasing quality metrics and adversely affecting associated decisions. The proprietary nature of usage data limited deeper exploration of this subject in the past. Objective: To determine how software faults and software use are related and how, based on that, an accurate quality measure can be designed. Method: Via Google Analytics we measure new users, usage intensity, usage frequency, exceptions, and release date and duration for complex proprietary mobile applications for Android and iOS. We utilize Bayesian Network and Random Forest models to explain the interrelationships and to derive the usage independent release quality measure. To increase external validity, we also investigate the interrelationship among various code complexity measures, usage (downloads), and number of issues for 520 NPM packages. We derived a usage-independent quality measure from these analyses, and applied it on 4430 popular NPM packages to construct timelines for comparing the perceived quality (number of issues) and our derived measure of quality during the lifetime of these packages. Results: We found the number of new users to be the primary factor determining the number of exceptions, and found no direct link between the intensity and frequency of software usage and software faults. Crashes increased with the power of 1.02-1.04 of new user for the Android app and power of 1.6 for the iOS app. Release quality expressed as crashes per user was independent of other usage-related predictors, thus serving as a usage independent measure of software quality. Usage also affected quality in NPM, where downloads were strongly associated with numbers of issues, even after taking the other code complexity measures into consideration. Unlike in mobile case where exceptions per user decrease over time, for 45.8% of the NPM packages the number of issues per download increase. Conclusions: We expect our result and our proposed quality measure will help gauge release quality of a software more accurately and inspire further research in this area.

show abstract

Forking and coordination in multi-platform development

Cited by 16 publications

References 26 publications

Feature-oriented clone and pull operations for distributed development and evolution

Feature-oriented clone and pull operations for distributed development and evolution

On the Combination of Static Analysis for Software Security Assessment – A Case Study of an Open-Source e-Government Project

Deriving a usage-independent software quality metric

Contact Info

Product

Resources

About